Incident List View
A bird's-eye view of all the incidents your team has encountered
Incidents signify problems or issues that require attention and resolution. When triggered on services, an escalation policy prompts notifications to be sent to on-call responders, who are responsible for promptly mitigating the issue.
The Incident List provides a convenient, single-glance view of all your incidents and their relevant information.
Note: To view the Incident List for a specific team, simply select the desired team from the team picker located at the top.
All
Open
Triggered
Acknowledged
Resolved
Suppressed
This section lists all the incidents of your team for the selected time period. You can select one or more incidents to perform bulk actions.
Note: This also includes all the Suppressed incidents.
This section lists all the Triggered and Acknowledged incidents of your team for the selected time period. You can select one or more incidents to perform bulk actions.
Note: You have the option to switch to the respective sections to exclusively view incidents specific to those states.
This section lists all the Triggered incidents of your team for the selected time period. You can select one or more incidents to perform bulk actions.
Note: You have the ability to perform actions such as Acknowledge, Reassign, Resolve, and Update Tags for individual incidents or in bulk.
This section lists all the Acknowledged incidents of your team for the selected time period. You can select one or more incidents to perform bulk actions.
Note: You have the ability to perform actions such as Reassign, Resolve, and Update Tags for individual incidents or in bulk.
This section lists all the Resolved incidents of your team for the selected time period.
Note: Once resolved, this action cannot be changed or undone.
Moreover, you have the ability to perform actions such as Update Tags, and Start/View Postmortem for individual incidents. Bulk actions are not supported for Resolved incidents.
This section lists all the Suppressed incidents of your team for the selected time period.
Note: You have the ability to Update Tags for individual incidents. Bulk actions are not supported for Suppressed incidents.
Depending on your specific use case, there are multiple methods available to trigger incidents in Squadcast:
Method | Manner |
|---|---|
A common practice is to integrate with third-party platforms, like monitoring tools, and configure them to trigger incidents in Squadcast when certain conditions are met. To learn more, visit our Integrations Library. | |
You can trigger an incident and promptly notify the on-call responder by manually opening an incident on a service.
This method is commonly used to test notification rules or to directly inform the on-call person about an issue with a particular service. | |
By leveraging the ability to create incidents from the mobile app, you have the ability to trigger an incident on the go. | |
We natively integrate with various tools. If you're using an integration that isn't listed, but the tool supports webhook-based integration, you can utilize our incident webhook integration.
This integration can also be leveraged for triggering incidents in your internal services based on your specific use case. | |
You can expand your customer support, by letting your stakeholders & customers report issues that trigger incidents in Squadcast. | |
By leveraging email integration for a service, you have the ability to trigger an incident simply by sending an email to the designated email address associated with the integration. | |
If your account has the Slack integration configured, you may also trigger an incident using Slack slash commands. |
To create a new incident using the web app,
- 1.Navigate to the Incidents List page -> Click Create New Incident on top right.
- 2.In the side panel, enter the Incident Title, optional Description, select the Service, specify who should be notified under Assign To, add Tags.
- 3.Click on Create to complete.
Image. Create Incident Manually
To search for a specific incident, enter its Incident Message in the Search field and hit enter.
To perform bulk actions, please select one or more incidents.
Status Section | Permissible Bulk Actions |
|---|---|
All | Based on the selection you make, you have the capability to perform actions similar to those displayed for each section. |
Open | ✅ Acknowledge ✅ Reassign ✅ Resolve
Note: If you choose one or more Acknowledged incidents in the bulk selection, performing bulk Acknowledgement won't be possible. |
Triggered | ✅ Acknowledge ✅ Reassign ✅ Resolve |
Acknowledged | ✅ Reassign ✅ Resolve |
Resolved | Bulk actions are not supported for Resolved incidents. |
Suppressed | Bulk actions are not supported for Suppressed incidents. |
Note: Bulk actions for updating Tags are unavailable.
Image. Perform Bulk Actions
When you star incidents in Squadcast, you mark them as important. This helps you remember to look at them later.
Image. Star Important Incidents
To star an incident,
- 1.Navigate to the Incidents List page -> navigate to your desired Status Tab.
- 2.Click on thenext to the Incident message, to mark the incident as important.⭐
To search for Starred Incidents,
- 1.Navigate to the Incidents List page -> click on Filters icon.
- 2.Under Show Starred Incidents, click Yes -> Click Apply.
To download incidents,
- 1.Navigate to the Incidents List page -> add the Filters of your choice.
- 2.Click Download All -> Select the export format option (CSV or JSON) from the drop-down.
- 3.Click Download to complete.
Image. Download Incidents
Incident Export Limit:
Please note, currently, the export of incidents is limited to a maximum of 1000 per export. Please adjust your filters to ensure the listed incidents remain within this limit for each export. There are no restrictions on the number of exports you can perform.
For unlimited incident exports, you can utilize our Export Async API. Upon completion, you will receive an email notification with the download link. For further details, refer to our Export Async API Documentation.
🔹 Best Practice Tip 🔹 For enhanced efficiency, we encourage utilizing our public API to export incidents in CSV or JSON format. Please refer to the API documentation available here.
Last modified 3mo ago