Adding a Service
Effortlessly add a new service and integrations for incident notifications - A step-by-step guide to creating and configuring a service for efficient incident management.
Last updated
Was this helpful?
Effortlessly add a new service and integrations for incident notifications - A step-by-step guide to creating and configuring a service for efficient incident management.
Last updated
Was this helpful?
A Service is a core component of your infrastructure/application for which alerts are generated.
Services in Squadcast represent specific systems, applications, components, products, or teams for which an incident is created. To check out some of the best practices for creating Services in Squadcast, refer to the guide here.
The User Role associated with the user in the Team must have required permissions to manage Services.
You need to have at least one Escalation Policy before you can add Services.
The number of Services that can be added to an Organization is determined by the plan that your account is currently on.
Navigate to Services -> Click on Add New Service. On the next screen, you will be guided through two steps.
2. Define Service: Enter the Name and Description based on the function that the service provides. Select an existing Escalation Policy and Owner. Enter Tags, and Click Save and Continue.
Tips
Give your services meaningful names that reflect the actual component name or functionality like - Login, Checkout, Payment API
You can also assign a Squad as the owner of a service
You can use tags to differentiate between business and technical services
3. Add Alert Source: Select the integration(s) you use to send alerts to this service from the search bar, dropdown, or from a list of our most popular integrations.
If you chose to add an integration to your service, you will now be in the service’s Integrations tab, where you’ll find the integration guide and an integration key. Follow the integration guide instructions to complete the configuration. Once you have completed the integration guide instructions, your service configuration is now complete.
4. Click on Done to Create a New Service.
To edit an existing service’s settings:
Navigate to Services -> Service Overview -> select or search for your desired service.
Click on the service to navigate to the Service Details page.
In the top right, click More -> Edit Service.
Once you have edited your preferred settings, click Save Changes.
To edit a service’s escalation policy:
Navigate to Services -> Service Overview -> select or search your desired service.
Click on the service to navigate to the Service Details page.
In the top right, click More -> Edit Service.
Under the escalation policy drop-down, search and select an escalation policy.
Click Save Changes.
To delete an existing service:
Navigate to Services -> Service Overview -> select or search for your desired service.
Click on the service to navigate to the Service Details page.
In the top right, select More -> Delete Service.
You will receive a prompt, click on Yes, Delete Services.
It will delete your Service.
If your Service has any open (triggered/ acknowledged) incidents, the system will not allow service deletion until those incidents are resolved. Click on Show Open Incidents to resolve and follow the same steps stated above to delete the service.
To resolve multiple incidents in one shot, check out the Take Bulk Actions documentation
To add an Alert Source Integration to your service:
Navigate to Services -> Service Overview -> select or search for your desired service.
In the extreme right, expand the accordion -> In the Alert Sources section, Add Alert Source.
Select the integration(s) you use to send alerts to this service from the search bar, dropdown, or from our most popular integrations list.
Click Add Alert Source.
Now your alert source is added, copy the Webhook URL.
Follow the Integration Guide to complete configuring the desired alert source.
Tips:
Incident auto-resolution is enabled by default provided the alert source supports it.
Email as an alert source does not support incident auto-resolution.
Reduce alert noise at the source end by sending in just actionable alerts that you want your on-call team to work on.
When not possible at the source end, use automation rules to group, suppress, tag, and route incidents intelligently.