A service represents a system or component you monitor, such as an API, a database, or a checkout flow. Services are the usual target that alerts are routed to.
🧩 What's on a service
Name and key – the display name and a unique identifier.
Service ID – a unique ID you can copy for use in your monitoring tools and integrations.
Team – the team that owns the service. A service always belongs to exactly one team.
Description – optional notes about what the service covers.
➕ Creating a service
Select Add service, choose the team that owns it, and give it a name. You can edit the name, key, and description later, inline from the Services list.
🎯 How services route alerts
A service is the concrete destination an alert is sent to. When an alert comes in for a service, Phoenix Alerts pages the owning team using that team's escalation policy. You map your Impacted Products to services so the right team is paged for each product.
🗑️ Deleting a service
You can delete a service from its row. Any alerts that were routed to it will no longer have a target, so make sure another service covers that system first.