Monitor Tag Policies

Overview

Monitor tag policies allow you to enforce data validation on tags and tag values on your Datadog monitors. This ensures that alerts are sent to the correct downstream systems and workflows for triage and processing.

After set up, tag policies apply to all Datadog monitors
  • To create a new monitor, it must adhere to your organization’s tag policies.
  • Existing monitors that violate your organization’s tag policies continue to provide alerts and notifications, but must be updated to match the tag policies before you can modify other settings.

Configure monitor tag policies

  1. Navigate to the Monitors > Settings page.
  2. Configure tag policies. There are three data validation rules that are enforced through tag policies:
    • Require tags with mandatory values
    • Require tags only
    • Optional tags with mandatory values
  3. Click the green checkmark to save the policy.
Monitor setting tag policies page

Require tags with mandatory values

To enforce mandatory tags, select the Required check box and specify both the tag key and values. In this example, monitors are required to have the cost_center tag. The value must be set to cc1, cc2, or cc3.

The Monitors Settings page displaying a tag policy for a required tag with mandatory values

Require tags only

You can require a tag but allow users to specify their own values. In this example, monitors are required to have the product_id tag. The value can be anything specified by the user.

The Monitors Settings page displaying a tag policy in which only the tag is required

Optional tag with mandatory values

To make a tag optional but require that monitors with the tag use specific values, enter the values for the tag in the Values field. In this example, the env tag is optional. However, if a monitor uses this tag, the value must be set to dev, staging, or prod.

The Monitors Settings page displaying a tag policy for an optional tag with mandatory values

Permissions

To configure monitor tag policies, you must be assigned a role with the MONITOR_CONFIG_POLICY_WRITE_PERMISSION permission.

For more information, see Role Based Access Control and Role Permissions.

Further Reading

Additional helpful documentation, links, and articles: