Overview

Global Admins and Team Managers can change a service at any time: edit its settings, pause it with maintenance or disable it, and delete it when it is no longer needed.

Where
Services > the service
Pause
Maintenance or disable
Delete
Only with no open incidents

Edit a service

Open the service from Services, change the settings or integrations, and save. A new escalation policy applies to new incidents only.

Pause a service

Option What happens Ends
Maintenance No new incidents, and open incidents are not notified. Messages that would have opened an incident are kept in the maintenance log. Automatically at the time you set, or when you click End Maintenance
Disable No new incidents, no notifications, and nothing is logged. Only when you enable it again

Set maintenance for a period from now (Maintenance Upto) or schedule a future start and end. The service list shows each service as Active, Disabled, Under Maintenance, Scheduled in future, or Not in Maintenance.

Maintenance tags: pause only part of a service

With Maintenance Tags, only matching messages are held; everything else is processed as normal. With no tags, the whole service is in maintenance.

Each tag set is a filter: it matches when all its tags appear in the API payload or email body. The service is in maintenance for a message when any filter matches.

Filter Tags
Filter 1 production-server01
Filter 2 user-registration, production-server02
Message contains Result
production-server01 Filter 1 matches: held (maintenance).
production-server02 No filter matches: processed normally.
user-registration in production-server02 Filter 2 matches: held (maintenance).

Incidents created from the web ignore tags; they are only blocked when the service is disabled or fully in maintenance.

Delete a service

Click Delete Service and confirm. You cannot delete a service that still has unresolved incidents: resolve them first.