Alert attributes

​

What attributes enable

• Automatically page the right teams based on the alert context. Configure alert routes to use attributes for dynamic routing.
• For example, route alerts to the team owning the affected service.

• Automatically set incident custom fields from alert attributes.
• For example, when multiple alerts are grouped into one incident, the incident’s affected Teams custom field can aggregate all team attributes from those alerts and show which teams were impacted.
• This enables better insights and reporting on incidents.

• Drive automations based on alert context using attributes in workflow conditions.
• For example, use impacted Customer attribute to automatically add the account’s Customer success manager to incidents.
• Another example, use the Github user attribute to page the engineer who last worked on this area.

• Aggregate and analyze alerts across different sources and identify patterns.
• Catalog-powered attributes allow for more granular insights than plain text attributes.
• For example, use feature attribute to analyze which product areas generate the most alerts, helping prioritize reliability work.

• Route alerts to specific Slack or Microsoft Teams channels dynamically based on context.
• For example, use Team attribute to send alerts to the right team channel.

​

Define attributes

1. Using the sidebar, navigate to Settings → Alerts
2. Click the Settings icon (gear icon in top right)
3. Select Attributes
4. Click + Add attribute to create a new attribute (see recommended attributes below)
5. Configure the fields:
   • Name: What to call the attribute (e.g., Team, Service, Customer)
   • Resource type: Link to Catalog types or store as plain text (String)
   • Multi-value: Allow multiple values per alert
   • Required: Mark as required when this attribute is critical for routing and escalation
6. Click Save changes

​

Recommended attributes

​

Labels

• cluster: us-east-1
• namespace: production
• resource_type: pod
• severity: critical

​

Required attributes

​

Extract attributes from sources

​

Extract using AI

1. Follow the alert source setup steps and navigate to the final stage Configure your setup
2. Click Review attributes to see AI suggestions based on your payload
3. For each suggested attribute:
   • Click Accept to add the attribute extraction (e.g., parse Team from payload)
   • Click Skip to ignore the suggestion
4. Accepted attributes appear in Your attributes section

​

Extract with custom logic

1. In the Attributes section during source setup, click + Add
2. Select Link an existing attribute and choose an attribute from your catalog
3. The attribute automatically maps to matching fields in your payload

1. In the Attributes section during source setup, click + Add
2. Select Create a new attribute and enter the attribute name (e.g., Team slack channel)
3. Write JavaScript (ES5) expression to extract the value from your payload
4. Configure the result type (String, Customer, Business functionality, etc.)

// Extracts feature name from tags like ["feature:payments", "env:prod"]
$.metadata.tags.filter(function(tag) {
  return tag.startsWith("feature:")
})

// Try multiple possible locations for team name
$.metadata.team || $.labels.team || "unknown"

​

FAQs