> ## Documentation Index
> Fetch the complete documentation index at: https://metoro.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Alert and Dashboard Tags

> Organize, find, and manage alerts and dashboards with reusable tags

Tags are organization-wide metadata that help you group related alerts and dashboards without changing their folders or access permissions. For example, you can use `payments`, `production`, or `team platform` on resources that belong to the same service, environment, or owner.

<Note>
  Tags help organize resources, but they do not grant or restrict access. Folder-based [resource permissions](/docs/user-management/rbac) continue to determine which alerts and dashboards a user can read or change.
</Note>

## Add or edit tags

### Alerts

When creating or editing an alert, add tags in the **Details** step. The complete tag set is also shown on the alert details page.

### Dashboards

Open the dashboard, choose **Edit**, and open **Dashboard settings** to add or remove tags. Dashboard clones retain the tags from the original dashboard.

Kubernetes-managed and ConfigMap-managed resources display their tags as read-only because their external manifest is the source of truth. Update the `tags` field in Kubernetes and sync the resource to change them.

## Find resources by tag

The Alerts and Dashboards pages include a **Tags** filter in both list and tree views. Select one or more tags to show resources that contain **any** selected tag. For example, selecting `payments` and `checkout` returns resources tagged with either value.

You can also click a tag chip on a resource row to filter directly to that tag. Dense rows show the first two tags and a `+N` indicator; open the resource to see the complete set.

Selected tags are stored in the URL as repeated `tag` parameters and coexist with search and folder parameters:

```text theme={null}
/alerts?folder=/alerts/default/&tag=payments&tag=production
/dashboards?tag=checkout&tag=payments
```

## Tag format

Metoro normalizes tag identity before saving or filtering:

* Leading and trailing whitespace is removed.
* Repeated whitespace is collapsed to one space.
* Letters are lowercased.
* Duplicate normalized values are removed.
* Only letters, numbers, spaces, hyphens (`-`), and underscores (`_`) are allowed.
* A resource can have at most 20 tags.
* Each tag must contain 1–64 characters after normalization.

For example, `  Team   Platform  ` is stored as `team platform`.

## API behavior

Alert and dashboard metadata accept an optional `tags` array in the [API reference](/docs/api-reference). On updates, omitting `tags` preserves the existing values, while sending an empty array clears all tags:

```json theme={null}
{
  "metadata": {
    "id": "payments-latency",
    "name": "Payments latency",
    "tags": ["payments", "production"]
  }
}
```

The authenticated application search endpoints accept repeated `tag` parameters and use match-any semantics:

```text theme={null}
GET /api/v1/searchAlerts?tag=payments&tag=checkout
GET /api/v1/dashboardSearch?tag=payments&tag=checkout
```

`GET /api/v1/resourceTags` returns an alphabetically sorted catalogue containing tags from alerts and dashboards that the caller can read. It never reveals tags that belong only to inaccessible resources.

## Imports, exports, and Kubernetes sync

* Metoro dashboard JSON imports and dashboard clones retain tags.
* Grafana imports start untagged; add tags after importing if needed.
* Alert and dashboard exports include tags.
* ConfigMap-managed alerts and dashboards support `metadata.tags`.
* `MetoroAlert` and `MetoroDashboard` resources support `spec.tags`.

Tags survive export, sync, and re-import round trips. See [Creating and Managing Alerts](/docs/alerts-monitoring/create_alert) and [Manage Dashboards with Kubernetes](/docs/dashboards/configmap-managed) for complete examples.