Services#

Services describe the affected systems inside IncidentRelay: APIs, databases, queues, websites, infrastructure components or business services.

Use this section for service ownership and impact modeling:

• Service model
• Service notification policies
• Service default stakeholders
• Service standards and events
• SLI/SLO
• Services API

Why services matter#

Routes answer how an alert entered IncidentRelay.

Services answer what system is affected.

Service context can improve:

• routing and triage;
• runbook discovery;
• owner and stakeholder visibility;
• dependency impact analysis;
• operational analytics.

Recommended setup#

• Create services for the systems your teams operate.
• Add ownership, links and runbooks.
• Configure service match rules or route default services.
• Create notification policies for shared service delivery rules.
• Assign notification policies to services.
• Select the required notification channel mode on routes.
• Add service default stakeholders when lifecycle notifications are useful.
• Review service impact and analytics during incident response.