Business-Impact-Tagged Alerts

Tag alerts with business impact for prioritisation.

Why tag with business impact

Engineers need technical context; executives need business context. The same alert can serve both audiences if tagged correctly.

Tags like "revenue-impacting", "compliance-critical", "customer-facing" let the right humans get the right view automatically.

Without tags, every alert escalates the same way; with tags, the routing matches the stakes.

The tag set

Keep it small: 5 to 7 tags maximum. "revenue", "compliance", "data-loss", "security", "reputation", "internal".

Apply at the service level, not the alert level. Every alert on the checkout service is revenue-impacting; tag once per service.

Maintain in the service catalog (Backstage, OpsLevel). Drift from there into PagerDuty and your alerting system.

Routing by tag

Revenue-impacting and compliance-critical: page on-call plus a Slack channel that includes leadership.

Internal-only: page on-call only, no leadership notification.

Data-loss: page on-call, infrastructure leads, and the data team. Three audiences for one alert.

Dashboards by tag

Build a "revenue-impacting open incidents" dashboard. Filter the incident list by tag.

Track MTTR per tag. Revenue alerts should resolve faster than internal ones; if not, priorities are wrong.

Show the tag distribution in your weekly ops review. The mix tells you where attention is going.

Get started

Define your tag set in 30 minutes. Don't over-engineer; you can add tags later.

Tag your top 20 services this week. Push tags into PagerDuty as service properties.

Build one tag-filtered dashboard. The first dashboard sells the rest.