MonSpark Docs
  • 👋Welcome to MonSpark
  • Overview
    • 💡What Is Monitoring?
    • ✨Types of Monitoring
    • 🛠️Getting Started with MonSpark
  • Fundamentals
    • 🔔Alerting
      • 📒Integrations
      • 🚨Escalation Policies
    • ⚠️Incidents
    • 📣Status Pages
    • 🏅Summary
    • 🔍Auto Discovery
  • Website Monitoring
    • 💻What is Website Monitoring?
    • 🛠️Getting started with Website Monitoring
    • ⚙️Working With Monitors
      • ⏯️Pausing/Resuming Monitors
      • 🗑️Deleting Monitors
      • 💠Bulk Create
      • 📄Reporting
    • 📈Availability
      • Uptime Monitor
        • Uptime Monitor Create
        • Understanding Uptime Monitor Details
      • Ping Monitor
        • Ping Monitor Create
      • TCP Monitor
        • TCP Monitor Create
    • 🛡️Security
      • Domain Expiration Monitor
        • Domain Expiration Monitor Create
      • DNS Record Monitor
        • DNS Record Monitor Create
      • IP Blacklist Monitor
        • IP Blacklist Monitor Create
      • Whois Monitor
        • Whois Monitor Create
      • Subdomain Monitor
        • Subdomain Monitor Create
      • Port Discovery Monitor
        • Port Discovery Monitor Create
    • ✨SEO
      • Lighthouse Audits
        • Lighthouse Monitor Create
      • Sitemap Monitor
        • Sitemap Monitor Create
      • URL Monitor
        • URL Monitor Create
    • ⛓️Integrity
      • Text Monitor
        • Text Monitor Create
      • Screenshot Monitor
        • Screenshot Monitor Create
      • Cookie Monitor
        • Cookie Monitor Create
      • Technology Monitor
        • Technology Monitor Create
      • Source Code Monitor
        • Source Code Monitor Create
    • 🕐Cronjob Monitoring
  • Server Monitoring
    • 🖥️What is Server Monitoring?
    • 🛠️Getting Started with Server Monitoring
      • 🖥️Servers
      • ⏰Alarms
      • 🗃️Rules
  • Transaction Monitoring
    • 🔮What is Transaction Monitoring?
  • Extras
    • ⛑️Troubleshooting and Support
      • IP Whitelisting
    • ⁉️FAQs
    • 💬Appendix
Powered by GitBook
On this page

Was this helpful?

  1. Fundamentals

Incidents

PreviousEscalation PoliciesNextStatus Pages

Last updated 1 year ago

Was this helpful?

Understanding Incidents


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.

To see the details, you can click on the name or the URL of the monitor.


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.

Indicates the start point of the incident.

Indicates the status of the incident whether it's ongoing or resolved.

Indicates the severity of the incident. In this way, you will take action accordingly.

You can find more information about the incident such as when the incident started and what caused the incident.

Acknowledgment

You can easily acknowledge the incident. Furthermore, you can create a rule for an incident to bypass acknowledgments.

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.

You will be provided with incident details which will help you to understand the incident's cause and why it started.

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.

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.

  • 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.

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.

Time Badge

Status Badge

Severity Level Badge

For a better understanding of how the steps escalate, please refer to the document.

⚠️
Understanding the Escalation Policies
Incident List
Incident Details
Incident Details - Timeline