Skip to content

Commit cb0b68e

Browse files
Merge pull request #21997 from newrelic/NR-459576-ai-log-summarization
[feat][Aert AI summary][DO NOT MERGE]: Add AI log summarization enhancements for log-based alerts
2 parents 9f2add2 + c835c74 commit cb0b68e

File tree

2 files changed

+37
-4
lines changed

2 files changed

+37
-4
lines changed

src/content/docs/alerts/incident-management/response-intelligence-ai.mdx

Lines changed: 37 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,15 @@ The AI-powered issue page provides a concise summary that includes the affected
3030
src="/images/nr-ai-summary.webp"
3131
/>
3232

33-
**What’s impacted?**<br/>
33+
## Access AI summary [#access-ai-summary]
34+
35+
To view the AI summary for any alert issue:
36+
37+
1. Go to **[one.newrelic.com](https://one.newrelic.com) > Alerts > Issues & activity**.
38+
2. Select an alert issue.
39+
3. Expand the <DNT>**AI summary**</DNT> section.
40+
41+
**What's impacted?**<br/>
3442
First responders need to assess the "blast radius" to determine the severity of an issue and decide on the next steps. This widget provides an overview of the affected entities along with the impact to the end users of the application or service.
3543

3644
**What happened previously?**<br/>
@@ -39,7 +47,7 @@ Many IT issues tend to reoccur. Knowing if an issue has happened before, why it
3947
**What to check?**<br/>
4048
First responders often need contextual guidance on immediate actions to mitigate an issue. This widget provides customized steps to help them quickly restore services to normal operational levels. Additionally, the Potential causes tab identifies likely causes through causal analysis, covering a range of possible anomalies and performance issues. For more information, refer to casual analysis.
4149

42-
## Causal analysis
50+
## Causal analysis [#causal-analysis]
4351
The causal analysis engine identifies potential symptoms that might have triggered an alert event and suggests immediate mitigating actions to address them.
4452

4553
Consider a scenario where a PHP application encounters a memory leak, leading to a failure in the throughput SLI and triggering an alert. Our engine investigates by moving from the service level to the APM application and then to the infrastructure container to detect the symptom.
@@ -55,11 +63,36 @@ At the moment, New Relic only supports causal analysis for APM entities.
5563
src="/images/potential_issues.webp"
5664
/>
5765

58-
### Mitigating actions & visualizations
66+
### Mitigating actions & visualizations [#mitigating-actions-visualizations]
5967

6068
For every identified potential cause, the engine offers tailored mitigation actions that guide users through the necessary steps to quickly restore services and entities to their normal operational states. We recognize that many of our customers typically rely on NRQL to analyze significant queries, hence we provide relevant visuals alongside the underlying query for each cause.
6169

62-
### New Relic AI generated analysis
70+
### New Relic AI generated analysis [#ai-generated-analysis]
6371

6472
In some scenarios, our causal engine may not identify an algorithm-driven cause. However, we have insights that, when combined with with LLMs, can offer you actionable steps. To access this capability, you must have the New Relic AI entitlement enabled.
6573

74+
## AI log summarization for log-based alerts [#ai-log-summarization]
75+
76+
For alert issues triggered by log conditions, the AI summary provides enhanced analysis by automatically examining up to 100,000 log entries from a contextual time window around your alert. This log analysis surfaces patterns, anomalies, and potential causes that aren't immediately visible in the alert itself.
77+
78+
When you expand the <DNT>**AI summary**</DNT> section for a log-based alert, following are details you'll get:
79+
80+
* <DNT>**Analysis context**</DNT>: The number of logs analyzed, time range, and entity name.
81+
* <DNT>**What happened**</DNT>: A summary explaining the incident with insights beyond the alert itself.
82+
* <DNT>**Findings (3-4)**</DNT>: Key patterns and anomalies with a specific remediation step.
83+
84+
<img
85+
title="The alerts issues feed."
86+
alt="A screenshot of the alerts issues
87+
feed."
88+
src="/images/ai-log-summary.webp"
89+
/>
90+
91+
To explore findings in detail, click into each finding. This displays comprehensive information below the AI summary section, including:
92+
93+
* Detailed explanation of each finding.
94+
* Specific remediation steps to resolve the issue.
95+
96+
This log-specific analysis helps you understand potential causes and resolve incidents faster by automatically surfacing critical information from thousands of log entries.
97+
98+

static/images/ai-log-summary.webp

746 KB
Loading

0 commit comments

Comments
 (0)