Require tags on every monitor

If you use monitor tags for governance, ownership, or reporting, you can now require them, so no monitor is created or saved without the tags you rely on.

Choose the level of enforcement:

• Require at least one tag. Any tag is accepted.
• Require a specific tag key, for example owner, with any value.
• Require a specific key with allowed values, for example lifecycle set to production, experimental, or deprecated.

Required keys and values are case-sensitive. Set requirements with the updateRequiredMonitorFields API mutation.

Learn more here: Setting required monitor tags