Services can refer to specific systems, applications, or tools that generate alerts. You will be able to quickly communicate with all concerned users whenever a service is impacted by an incident.
You need to have at least one escalation policy before you can add a Service.
The escalation policy that you assign to a service is its default escalation policy. If routing rules are configured for this service, it can override the default policy and will escalate based on the configured rules.
You can create a service under Services (Sidebar) → Add Service.
Give your service a name and a description.
Then search for and assign the relevant escalation policy to the service.
You can choose to add an email address prefix to the service for it to function as an alternative alert source for the particular service.
If you leave it blank, Squadcast will automatically fill in the prefix-key which you can use.
Once you have created a service, you can send alerts for this service from multiple sources.
To get trigger endpoints of different alert sources for a given service, click on the Alert Sources button of the service as shown below.
Select the type of Alert Source from the dropdown and you'll get the corresponding triggering endpoint as well as a link to documentation on how to setup that alert source.
The dropdown has all the available active endpoints that can be used to send in alerts into Squadcast.
The details of the alert source can be accessed in the Incident Dashboard and Incident Details pages.
So, now when the incident comes for a service via a given alert source, you can see the Service in the Impact On column and Alert Source in Via column, in incident listing page:
and on the incident details page:
We are currently working on improving the UI to show you the list of integrated alert sources for each service.
We recommend adding the names of the integrated alert sources under the Service Description so as to keep a note of all the end-points.
Updated 4 months ago