What a service is
A service is whatever you’d name in a sentence like “the checkout API is down” - an app, a queue, a job, a database. Every alert in Warrn belongs to a service, and every service belongs to a team. That chain is how Warrn decides who to page when something breaks.
If a team is “who owns this,” a service is “what they own.”
Creating a service
Open the team that will own it and click New service. You need to be a team admin. A service needs a name (visible everywhere this service appears) and an optional description.
What lives on a service
- Integrations - alert sources (CloudWatch, Sentry, Grafana, Pingdom, webhooks), plus Slack/Jira/Confluence overrides for this service.
- Alert intelligence - the per-service AI Triage toggle, gated by the team’s master switch.
- Knowledge - runbooks and notes scoped to this service.
On-call
A service doesn’t have its own on-call. It inherits from its team. To change who gets paged for this service, edit the team’s on-call schedule.
Deleting a service
Admins can delete a service from its detail page. Past alerts and incidents linked to the service stay in the system for history, but the service itself is removed and any integrations attached to it stop routing.
If a service is just changing owners, reassign it to another team instead of deleting and recreating.
