PagerDuty

• Automatically adds Root Cause Reports as Events in PagerDuty. This allows you to see details of root cause and direct the incident to the appropriate team.
• Each Zebrium RC Report includes a summary, word cloud and a set of log events showing symptoms and root cause. Plus a link to the full report in the Zebrium UI.
• This means faster MTTR and less time manually hunting for root cause.

How it Works

Our recommended mode of operation for Incident Management integrations is to use Zebrium’s Augment mode as an accurate mechanism for explaining the reason something went wrong. In this mode, you continue to use your existing rules as the primary source of problem detection and Incident creation. You can then review Zebrium RC Report findings directly in your Incident that was created by PagerDuty to explain the reason behind Incident.

Auto-Detect mode is useful when you want to direct all Root Cause Reports to PagerDuty for routing and dispositioning. Or, when you want to send only specific Root Cause Reports to PagerDuty after first reviewing in the Zebrium UI.

The two modes of operation are independent. You can configure Augment and/or Auto-Detect modes depending on your operational use-case.

Augment: Receive Signals from PagerDuty Incidents

1. Any PagerDuty Incident can trigger a webhook request for Root Cause Analysis from Zebrium.
2. Zebrium finds anomalous log patterns from your application that coincide with the Incident and creates a Root Cause Report.
3. Root Cause Report summaries are sent to PagerDuty using the notes API and Root Cause details are visible in your PagerDuty Incident.
4. If you need to drill down further to look at correlated logs across your entire app, it’s just one click from your Incident.

CLICK HERE To receive Signals from PagerDuty Incidents

Auto-Detect: Send Root Cause Detections to PagerDuty as Events

1. Zebrium continuously monitors all application logs and uses unsupervised machine learning to find anomalous log patterns that indicate a problem. These are automatically turned into Root Cause Reports highlighting details of any problems with over 95% accuracy.
2. Root Cause Report summaries are sent to PagerDuty using the Events API interface so Root Cause details are visible in PagerDuty.
3. If you need to drill down further to look at correlated logs across your entire app, it’s just one click from your Alert/Incident.

CLICK HERE To send Root Cause Detections to PagerDuty as Events