Tag
Field reference and a complete example manifest for the Tag Kind.
Tag
A labeled color and description an organization can attach to monitors. metadata.name is the natural key, unique per organization.
Fields
Generated from up0 schema explain Tag --version v1 --output json against a live deployment.
| Field | Type | Required | Default | Meaning |
|---|---|---|---|---|
color | string | no | #6B7280 | A hex color code, used wherever the tag renders as a chip. |
description | string | no | (none) | Free text, up to 500 characters. |
Monitor.spec.tags (see the Monitor page) references a Tag by its metadata.name, so declare the tags a monitor needs before, or alongside, the monitor that uses them.
Example
Applied directly through the API for this page:
# up0/tags/production.yaml
apiVersion: up0.io/v1
kind: Tag
metadata:
name: production
spec:
color: "#3B82F6"
description: Production environmentReal output, applied as 1651-example while writing this page:
{"id":"c4512d73-7d6b-474a-b521-b7fae5c2b757","org_id":"1f1317e4-2675-4f15-a298-d09346c9cad8","name":"1651-example","color":"#3B82F6","description":"docs walk for #1651 configuration-as-code","created_at":"2026-09-16T13:29:14.242290Z","updated_at":"2026-09-16T13:29:14.242290Z"}No uniqueness constraint yet
Every other Kind's backing table enforces a (org_id, name) uniqueness constraint, which is what makes a repeated apply idempotent rather than a duplicate. tags still has only a plain, non-unique index, so re-applying a Tag manifest twice is not yet guaranteed to converge on one row the way every other Kind's does.