Summary: Defines the mandatory tagging scheme for all Meraki networks in the dashboard — site code, region, and environment tags — to support automation, alerting, and operational reporting.
| Field | Value |
|---|---|
| Author | Mike |
| Owner | Network Team |
| Status | Draft |
| Version | 0.1 |
| Last Reviewed | 2026-05-14 |
| Review Due | 2026-08-14 |
| Approver | — |
| Approved Date | — |
| Version | Date | Author | Description |
|---|---|---|---|
| 0.1 | 2026-05-14 | Mike | Initial draft |
⚠️ Draft
This standard is a draft and has not been reviewed or approved. Do not apply it until it has been signed off.
This standard defines the mandatory network tags that must be applied to every Meraki network in the dashboard. Consistent tagging enables automation scripts and monitoring tools to filter and act on networks by site and region, ensures that development environments are excluded from production alerting, and provides a reliable basis for dashboard-level reporting across the estate.
This standard applies to all Meraki networks created in the organisation's Meraki dashboard, regardless of network type (MX, MS, MR, combined, or template-bound).
The following are out of scope:
Every Meraki network must have a site_code: tag. The value must be the four-letter site code for that location in uppercase letters (for example, site_code:UKPB).
Every Meraki network must have a region: tag. The permitted values are NAM (North America) and EMEAA (Europe, Middle East, Africa, and Asia). No other values are permitted.
Any Meraki network that is in development or staging — and for which production alerts should be suppressed — must have the environment:staging tag applied.
A network without the environment:staging tag is treated as a production network and will receive full alerting. This is the default state.
All tags must use the key:value format with no spaces around the colon and no leading or trailing spaces in the value.
Tag keys and values are case-sensitive in Meraki. All tag keys must be lowercase. Site code values must be uppercase. Region values must be uppercase (NAM, EMEAA).
| Tag | Format | Permitted Values | Example |
|---|---|---|---|
| Site code | site_code:<XXXX> |
Four-letter site code, uppercase | site_code:UKPB |
| Region | region:<value> |
NAM or EMEAA |
region:EMEAA |
| Environment | environment:staging |
Fixed value | environment:staging |
Meraki network tags are the primary mechanism for attaching metadata to a network that can be read by automation, the Meraki API, and third-party tooling. Standardising the tag format and permitted values ensures that any script or integration querying the dashboard for region:EMEAA or site_code:ABCD produces a reliable, complete result set.
The environment:staging tag provides a lightweight mechanism to suppress alerts for development networks without requiring a separate dashboard organisation. Any alerting tool or automation runbook can check for the presence of this tag and skip the network accordingly. Using a fixed, well-known tag value (rather than ad hoc values such as dev, test, or staging-do-not-alert) avoids fragmentation over time.
The NAM / EMEAA region taxonomy reflects the two primary geographic groupings used across the organisation for reporting and on-call purposes.