On the Overview page, you'll find a consolidated view of your current alert events. The Issues & activity page has views of your active issues and recent alert events.
Why it matters
The Overview and Issues & activity pages provide analytics on how your system is (or isn't) performing. You can quickly switch between the Overview, Issues and Alert events to scan for critical problems affecting your systems.
Overview page
The overview page shows a high-level view of recent and current alert events. With this page, you'll get quick insight into how many critical alert events you have, how many have been closed, and which policies are creating the most alert events. This page also shows the top sources of your muted alert events.
Dashboard title | What it is |
|---|---|
Opened alert events by priority (time series) | A time series view that counts the number of alert events opened during a time period. This chart only tracks open events. It doesn't track the open or closed state of the alert event. |
Opened alert events by priority (pie) | This chart uses the same data as the time series chart of the same name. It quickly shows you the breakdown between warning and critical alert events. Click the pie chart to filter the whole page by warning or critical alert events. |
Closed alert event durations | A distribution of how long each alert event was open (duration), before being closed. Generally, it's better to have shorter durations for your alert events. If you're seeing a lot of long duration alert events, you may want to write a custom filter to investigate those more deeply. |
Muted alert events | If you've written some muting rules, you'll see them here. If you're not using any muting rules, you'll see 100% “Not muted” alert events. Click this chart to filter by muted alert events to quickly see where they're coming from. |
Top policies creating alert events | A chart of the top five policies generating the most alert events. Click a policy name to filter the whole page by that policy's alert events. |
Top conditions creating alert events | A chart of the top five conditions generating the most alert events. Click a policy name to filter the whole page by that condition's alert events. |
Top sources of alert events | A chart of the entities generating the most alert events. If available, it uses the entity name. Otherwise, it will use the event type. Click an entity to filter the whole page by that entity's alert events. |
Issues
On the Issues & activity page, issues are groups of alert events that describe the underlying problem of your symptoms. When a new alert event is created, alert event intelligence opens an issue and evaluates other open issues for correlations. An issue will contain arrays of all the tags (metadata) from all the alert events it contains.
The issues feed includes all of your issues and can be searched and filtered using the top of page component.
By default, the issues feed is filtered to only show the active issues. You can also filter by issue priority, source, alert condition, alert policiy, entity, or issue ID.
By default, issues are sorted by most recently created issue.
Click an issue to open its issue page.
Issues feed columns
Column name | Values |
|---|---|
State | Created, active, acknowledged, investigating, closed |
Priority | Low, medium, high, critical |
Issue name | The issue's name |
Created | When the issue was created (in absolute or relative time) |
Duration | How much time has passed since the issue was created |
Entities | A list of the impacted entities. If the list is too long to be shown, mouseover the value to see the list. |
Analysis summary | The machine learning module's output for the issue |
Path | The Sources -> Destination path |
Alert events | The number of related alert events |
Alert events
On the Issues & activity page, alert events are events that describe the symptoms affecting your system over time. These symptoms are detected by your monitoring tools, which evaluate your data streams and events.
New Relic alert event metadata comes from any of the following sources:
- Inheriting all the tags from the alert condition that triggered it
- All the facets, values, and where conditions are added as tags if the NRQL alert condition contains a facet or where condition
- All the tags from an entity are added if the result of the NRQL alert condition can be mapped to that single entity
External alert event medadata is what was received as tag.*.
The alert events feed includes all of your alert events: New Relic alert events and external alert events.
You can filter the feed by source, alert event state, and priority.
Default behavior
By default, the feed is sorted by last updated at the top.
Click an alert event's row to see the alert event's details.
Alert events feed columns
Column name | Values |
|---|---|
State | Open, Closed |
Priority | Low, Medium, High, Critical |
Alert event name | The alert event's name |
Created | When the alert event was created (in absolute or relative time) |
Duration | How much time has passed since the alert event was created |
Entities | A list of the entities impacted by the alert event. If the list is too long to be displayed, mouseover the value to see the list. |
Analysis summary | The machine learning module's output for the alert event |
Source | The source system of the alert event |
Events | The number of events aggregated in the alert event |