We’re excited to introduce monitor metadata, a new feature available in the General tab of monitor settings.
You can now add custom key/value metadata to monitors, making it easier to organize resources and add operational context to alerts and integrations.
What is monitor metadata?
Monitor metadata allows you to attach arbitrary key/value tags to a monitor without changing its name or configuration.
Navigate to:
Monitor → Settings → General → Metadata
and add custom values such as:
| Key | Value |
|---|---|
| team | Platform Engineering |
| owner | Sarah Johnson |
| project | Customer Portal |
| environment | Production |
You can add as many metadata fields as needed to fit your organization’s workflows.
Why use metadata?
As monitoring environments grow, it’s important to provide responders and external systems with additional context.
Monitor metadata helps you:
- Define monitor ownership
- Organize services and applications
- Identify environments
- Add business and operational context
- Improve incident routing and escalation workflows
- Enrich integrations with custom attributes
Metadata is automatically included in API responses, webhook payloads, PagerDuty incidents, and Opsgenie alerts, ensuring that important monitor context is available wherever alerts and monitoring data are consumed.
Getting started
- Open any monitor.
- Navigate to Settings → General.
- Scroll to the Metadata section.
- Add one or more key/value pairs.
- Save your changes.
That’s it. Your metadata will automatically be included in supported integrations and notification payloads.
We’re interested in hearing how you’d like to use metadata across your monitoring workflows. If there’s another integration, notification channel, or feature where you’d like to see metadata support, we’d love your feedback. Please reach out to our support team and let us know what you’re looking for – we use customer feedback to help prioritize future enhancements.
