Adding a Service

Service - The core components of your infrastructure from which alerts are generated

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.

πŸ“˜

Note:

You need to have at least one Escalation Policy before you can add a Service.

The Escalation Policy that you assign to a service will be its default Escalation Policy. If Routing Rules are configured for this Service, escalation will be based on the configured rules and hence, overriding the default Escalation Policy.

  • You can create a Service under Services (Sidebar) β†’ Add Service.

  • Give your Service a name and a description.

  • From the drop-down, choose and assign the relevant Escalation Policy for the Service.

🚧

Optional

You can choose to add an email address prefix to the Service for it to function as an alternative alert source for that Service.

If you leave it blank, Squadcast will automatically fill in the prefix-key which you can use.

  • Status Based Deduplication is enabled by checking the box with the information message and choosing the appropriate time window for which you'd like this deduplication rule to hold true.

πŸ“˜

Note:

While creating a Service, Status based Deduplication checkbox is disabled by default. You can enable the checkbox if you want Status based Deduplication for the Service. Before clicking on Save, ensure to verify and edit the duration for which you want the Deduplication rule to hold true.

  • Once this is enabled, you will see this Deduplication Rule reflect in the Deduplication Rules section.

You can edit, delete or change the execution priority of the rule to fit your use-case better.

  • Once you have created a Service, you can send alerts for this service from multiple sources.

Adding Multiple Alert Sources for one Service

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 that lists our native integrations and you will get the corresponding trigger endpoint as well as a link to the documentation on how to setup that Alert Source.

πŸ“˜

Note:

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, Incident List 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 the Incident Dashboard:

and on the Incident Details page:

Similarly, on the Incident List page, for every incoming incident, the Service affected is listed under Service and the Alert Source is listed under Alert source.

Pro Tip

πŸ‘

Pro Tip:

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 easily keep a note of all the configured end-points.

Updated 11 days ago



Adding a Service


Service - The core components of your infrastructure from which alerts are generated

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.