You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Logz.io is an AI-powered observability platform that helps teams monitor, troubleshoot, and secure their applications using logs, metrics, and traces. It also offers GenAI-driven features to enhance observability workflows.
10
10
11
-
Integrating Logz.io with PagerDuty lets you automatically create incidents when alerts are fired, ensuring your on-call teams receive real-time notifications and can respond quickly, based on your PagerDuty service configurations.
11
+
Logz.io integrates with PagerDuty to automatically create incidents from Logz.io alerts. This ensures on-call teams receive real-time notifications and can respond quickly, based on PagerDuty service configurations.
12
+
13
+
Beyond basic alerting, this integration also supports AI-driven Root Cause Analysis (RCA). Incidents in PagerDuty can trigger Logz.io’s RCA Agent, which analyzes observability data (logs, metrics, traces, deployments) and enriches incidents with contextual insights and recommended fixes.
12
14
13
15
## Prerequisites
14
16
15
17
Before you begin you’ll need:
16
18
17
-
* Logz.io access with Admin role.
18
-
* PagerDuty access with Admin permissions.
19
-
* A new or existing PagerDuty service.
19
+
* Logz.io access with Admin role
20
+
* PagerDuty access with Admin permissions
21
+
* A new or existing PagerDuty service
20
22
21
-
## Step 1: Set up the integration in PagerDuty
23
+
## Step 1: Configure PagerDuty
22
24
23
-
You can connect Logz.io to either a new or an existing service in PagerDuty.
25
+
You can connect Logz.io to a new or existing service in PagerDuty.
24
26
25
27
### Option A: Create a new service
26
28
@@ -48,17 +50,17 @@ In your **Logz.io account**, go to **Settings > Notification Endpoints** and cli
48
50
49
51
Choose **PagerDuty** as the endpoint type. Enter a name and optional description, then paste the **Integration Key** copied from PagerDuty.
50
52
51
-
Before using the endpoint, click**Run the test** to verify that Logz.io can send data to PagerDuty successfully.
53
+
Click**Run the test** to verify that Logz.io can send data to PagerDuty successfully.
52
54
53
55
Click **Add a new endpoint** to save.
54
56
55
-
56
-
57
-
58
57
:::note
59
58
You can create multiple Logz.io integrations in PagerDuty by adding them to new or existing services. Each integration generates a unique key that can be used to create a separate notification endpoint in Logz.io.
60
59
:::
61
60
61
+
62
+
63
+
62
64
## Step 3: Attach the endpoint to a Logz.io alert
63
65
64
66
In **Logz.io**, navigate to the **Alerts page**. Select an existing alert or create a new one.
@@ -71,15 +73,19 @@ When triggered, the alert sends a notification to PagerDuty, which generates a n
71
73
72
74
## PagerDuty integration with Logz.io's RCA capabilities
73
75
74
-
Connect PagerDuty incidents to Logz.io’s Root Cause Analyzer (RCA) so each incident triggers an automatic analysis and send findings back to PagerDuty.
76
+
PagerDuty incidents can automatically trigger Logz.io’s Root Cause Analyzer (RCA), triggering an automatic analysis and sending findings back to PagerDuty.
75
77
76
78
### How it works
77
79
78
-
Within PagerDuty’s Incident Workflows, a new action is available: “Initiate RCA in Logz.io”. No custom scripting is needed - the action is built-in.
80
+
When an alert in Logz.io fires, a PagerDuty incident is created. PagerDuty’s automation agent immediately handles the initial triage by opening communication channels and, if configured, updating the status page.
81
+
82
+
Once the incident is active, PagerDuty enriches it with context from similar past incidents. This includes historical timelines, successful remediation steps, and information about who resolved comparable issues.
83
+
84
+
Logz.io’s RCA Agent then runs a deep analysis of the real-time logs, metrics, and traces, combining this data with the enriched incident context. The output is a recommended fix or next step tailored to the current problem.
79
85
80
-
When an incident triggers, Logz.io automatically runs AI-powered Root Cause Analysis (RCA) across logs, metrics, traces, and deployments. Results are returned directly inside PagerDuty notifications (email, Slack, etc.), shortening investigation time.
86
+
For low-risk issues, the RCA Agent can attempt an automatic remediation, such as restarting a service. If remediation is not safe or fails, PagerDuty escalates the incident to a human responder, who receives the RCA summary and recommended fix.
81
87
82
-
Logz.io’s RCA uses historical PagerDuty incidents to learn how similar issues were resolved, and builds dynamic playbooks based on those past actions, so users don’t need to manually maintain RCA instructions. Optionally, teams can embed existing Confluence/Jira runbooks or add instructions in plain English.
88
+
Finally, once the incident is resolved, PagerDuty updates stakeholders, records the RCA findings, and stores them for future reference. The next time a similar incident occurs, PagerDuty can surface these previous learnings to reduce resolution time even further.
83
89
84
90
Read more about Logz.io's [AI Agent Root Cause Analyzer](https://docs.logz.io/docs/user-guide/observability/assistantiq/#ai-agent-root-cause-analyzer).
0 commit comments