# Incidents

### Understanding Incidents {% @arcade/embed flowId="4ca5IWioNP5snv1Xqopf" url="" %} *** **Incidents** You'll be provided an overview of the most important information about incidents. #### Ongoing Incidents You can view ongoing incidents listed under this section. #### Resolved Incidents You can view resolved incidents listed under this section. #### Name and URL You can view the name and the URL of the monitor where the incident is happening. {% hint style="info" %} To see the details, you can click on the name or the URL of the monitor. {% endhint %} *** {% tabs %} {% tab title="List View" %}

Ongoing and resolved incident details are provided here. The monitor's name and the URL where the incident is happening are also available at first glance. **Time Badge**

Indicates the start point of the incident. **Status Badge**

Indicates the status of the incident whether it's ongoing or resolved. **Severity Level Badge**

Indicates the severity of the incident. In this way, you will take action accordingly. {% hint style="info" %} You can find more information about the incident such as when the incident started and what caused the incident. {% endhint %} **Acknowledgment** You can easily acknowledge the incident. Furthermore, you can create a rule for an incident to bypass acknowledgments. {% hint style="warning" %} Keep in mind that acknowledging the incident will stop further escalations to the next steps if they are not configured to bypass acknowledgment. You can also unacknowledge the incident, which will reactive the escalation to the next steps. {% endhint %} {% endtab %} {% tab title="Details View" %}

You will be provided with incident details which will help you to understand the incident's cause and why it started. {% hint style="info" %} In the example given, you can see that the monitor went down because a 500 status code was received. Moreover, the lifecycle timings of the incident are provided to understand what might have gone wrong. {% endhint %} #### **Timeline**

The timeline section provides a chronological record of the key events that transpired during an incident. It offers a clear understanding of the incident's lifecycle, from initial detection to resolution.
* **Incident Started:** Documents the exact time when the incident was first identified. * **Step:** Documents the actions taken in accordance with the configuration of the Escalation Policy. {% hint style="info" %} For a better understanding of how the steps escalate, please refer to the [Understanding the Escalation Policies](https://docs.monspark.com/fundamentals/escalation-policies#steps) document. {% endhint %} * **X opened the incident:** Documents the exact time when the incident details are first viewed, along with the teammate who accessed them. * **Incident Acknowledged:** Documents the exact time when the incident is acknowledged, along with the teammate responsible for the acknowledgment. * **Incident Resolved:** Documents the exact time when the incident was deemed fixed and normal operations were restored. {% hint style="info" %} Clicking the "Open Details" button allows you to access the incident details on a separate page. This enables you to copy the link and share it with your teammates as required. {% endhint %} {% endtab %} {% endtabs %}