Browse documentation

Respond

Create useful alerts

Notify the right people about customer-impacting failures without creating noise.

An alert should describe a condition someone can act on. Start with customer symptoms and critical journeys, then add service-level alerts only where they support that response.

Add a destination

Open Settings → Notifications and create a notification channel for direct rule delivery. Send a test notification before attaching it to a production rule. Add personal contact methods only when the rule routes through an escalation policy or on-call schedule.

Available destinations depend on the connections enabled for your organization. Webhooks can cover destinations without a dedicated integration.

Create a rule

Open Alerts and create a rule. Define:

  • the project and environment;
  • the signal or customer being watched;
  • the threshold and evaluation window;
  • how long the condition must remain true; and
  • the notification destination.

Use a sustained window for noisy metrics. Use immediate notification only for conditions where one event is actionable, such as a critical customer error.

Test before enabling

Use the rule test action and confirm the message contains enough context to begin an investigation: the condition, severity, project, environment, time, and a link back to Teml.

Respond to an alert

  1. Acknowledge when someone takes ownership.
  2. Open the linked customer, Issue, trace, or service evidence.
  3. Create an incident when coordination or a durable case file is needed.
  4. Resolve after the condition has cleared and follow-up is recorded.

Use a silence for planned maintenance or a known temporary condition. Give every silence an owner and expiration time.

Tune based on outcomes

Review alerts that fired without action and alerts that should have fired but did not. Change the condition, window, or routing rather than training the team to ignore noise.