Leverage Multiple Alert Sources in Squadcast to reflect your actual system infrastructure on your Service Dashboard
Having your Incident Management Tool reflect your system architecture is a big milestone in reducing cognitive load on your on-call team.
In order to help our users move one step closer to this milestone, we recently released the functionality to add multiple alert sources to a service.
You can now model your service dashboard to mimic your actual system architecture. A simple example service dashboard of a video streaming platform would be:
For each service, you can see an active endpoint for the list of available integrations. Active Integrations for a service are denoted by a green dot against their name.
When an incident is triggered for a service, you will also have the details of the source of the trigger on the Incident dashboard and Incident details page.
So, when an incident is triggered for a service, the on-call team will know instantly which service has been impacted without spending a lot of time trying to dig that data out, thus reducing MTTA and MTTR and adhering to SLAs.
This in contrast with our earlier one-alert-per-service configuration, is a much cleaner, less populated service dashboard resulting in improved response times.
If you have other best practices to share or just need help with the set-up, feel free to drop a line to our Support Team.
Squadcast is an incident management tool that’s purpose-built for SRE. Create a blameless culture by reducing the need for physical war rooms, unify internal & external SLIs, automate incident resolution, and create a knowledge base to effectively handle incidents.
Leverage Multiple Alert Sources in Squadcast to reflect your actual system infrastructure on your Service Dashboard
Having your Incident Management Tool reflect your system architecture is a big milestone in reducing cognitive load on your on-call team.
In order to help our users move one step closer to this milestone, we recently released the functionality to add multiple alert sources to a service.
You can now model your service dashboard to mimic your actual system architecture. A simple example service dashboard of a video streaming platform would be:
For each service, you can see an active endpoint for the list of available integrations. Active Integrations for a service are denoted by a green dot against their name.
When an incident is triggered for a service, you will also have the details of the source of the trigger on the Incident dashboard and Incident details page.
So, when an incident is triggered for a service, the on-call team will know instantly which service has been impacted without spending a lot of time trying to dig that data out, thus reducing MTTA and MTTR and adhering to SLAs.
This in contrast with our earlier one-alert-per-service configuration, is a much cleaner, less populated service dashboard resulting in improved response times.
If you have other best practices to share or just need help with the set-up, feel free to drop a line to our Support Team.
Squadcast is an incident management tool that’s purpose-built for SRE. Create a blameless culture by reducing the need for physical war rooms, unify internal & external SLIs, automate incident resolution, and create a knowledge base to effectively handle incidents.
