Skip to content

Commit

Permalink
feat(Alerts): Updated the content and screenshots
Browse files Browse the repository at this point in the history
  • Loading branch information
nbaenam committed May 16, 2023
1 parent 32704ca commit 15ca384
Show file tree
Hide file tree
Showing 8 changed files with 16 additions and 142 deletions.
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
---
title: Alert coverage gaps
title: Alert coverage gaps and condition recommendations
tags:
- Alerts and applied intelligence
- Applied intelligence
- Proactive detection
- Alert coverage gaps
metaDescription: Learn how alert coverage gaps in New Relic help you identify gaps in your alert system.
redirects:
- /docs/alerts-applied-intelligence/new-relic-alerts/get-started/condition-recommendations
---

import accountsAlertCoverageGapsHomepage from 'images/accounts_screenshot-full_alert-coverage-gaps-homepage.webp'
Expand All @@ -14,44 +16,42 @@ import accountsAddanAlert from 'images/accounts_screenshot-crop_add-an-alert.web

import accountsCreateaPolicyAlertCoverageGaps from 'images/accounts_screenshot-crop_create-a-policy-alert-coverage-gaps.webp'

Alert coverage gaps highlight areas in your stack where you're missing alert coverage. In our Alerts and AI section [we've created a homepage](https://one.newrelic.com/nrai/detection-gaps/home) where you can see all your uncovered entities so you can assess what information your team is lacking and address the coverage gap.
Alert coverage gaps highlight areas in your stack where you're missing alert coverage. In our Alerts and AI section, [we've created a homepage](https://one.newrelic.com/nrai/detection-gaps/home) where you can see all your uncovered entities so you can assess what information your team is lacking and address the coverage gap.

In an increasingly dynamic landscape, we know how important it is to stay on top of your stack and be proactively notified if anything goes wrong. But, as your team grows or changes, it can be hard to know if you're getting the alerts you need, when you need them. Alert coverage gaps gives your team a comprehensive list of all entities that your team *is not currenty covering*.
In an increasingly dynamic landscape, we know how important it's to stay on top of your stack and be proactively notified if anything goes wrong. But, as your team grows or changes, it can be hard to know if you're getting the alerts you need, when you need them. Alert coverage gaps gives your team a comprehensive list of all entities that your team *is not currenty covering*.

What does covering an entity mean? A covered entity means that you've set up an [alert](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/basic-alerting-concepts/) to notify you of how a particular entity is performing. For example, you might have created an alert condition that opens an incident if a host's CPU goes above 80%. An uncovered entity is part of your system that is unmonitored which means there could be unhealthy behavior that goes unchecked. We created [alert coverage gaps](https://one.newrelic.com/nrai/detection-gaps/home) to highlight uncovered entities so your team doesn't miss valuable data and you can prevent incidents before they happen.
What does covering an entity mean? A covered entity means that you've set up an [alert](/docs/alerts-applied-intelligence/applied-intelligence/incident-intelligence/basic-alerting-concepts/) to notify you of how a particular entity is performing. For example, you might have created an alert condition that opens an incident if the throughput of an APM entity exceeds 100 requests per minute. An uncovered entity is part of your system that is unmonitored which means there could be unhealthy behavior that goes unchecked. We created [alert coverage gaps](https://one.newrelic.com/nrai/detection-gaps/home) to highlight uncovered entities so your team doesn't miss valuable data and you can prevent incidents before they happen.

## Find your coverage gaps [#find-your-coverage-gaps]

On the Alerts and AI UI page, select alert coverage gaps in the navigation. There you will see a dashboard of all your entitites that are not currently covered.
To open alert coverage gaps, go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI** and select **Alert coverage gaps** in the left navigation pane. There you will see a list of all your entitites that are not currently covered.

<img
title="Alert coverage gap dashboard."
alt="A screenshot of the alert coverage gap dashboard"
title="Alert coverage gap page."
alt="A screenshot of the alert coverage gap page"
src={accountsAlertCoverageGapsHomepage}
/>

<figcaption>
When you select alert coverage gaps you will see a list of all your unmonitored entities.
Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI** and select alert coverage gaps in the left navigation pane. When you select alert coverage gaps you'll see a list of all your unmonitored entities.
</figcaption>

## Create an alert [#create-an-alert]

Once you've selected an entity you'd like to monitor, then you can create an alert condition to notify your team of any abnormal behavior.

New Relic will dynamically suggest the conditions we believe should be monitored based on the selected entity and your specific system. Some [recommended alerts](/docs/alerts-applied-intelligence/new-relic-alerts/get-started/condition-recommendations/) we might suggest are error percentage, apdex, or response time.
New Relic will dynamically suggest the conditions we believe should be monitored based on the selected entity and your specific system. Some recommended alerts we might suggest are error percentage, apdex, or response time.

If you're not in the EU, once you select an alert condition you'd like to monitor, you may get recommended alert conditions based off of a machine learning model. The model may set different recommended thresholds based on a comparison of your entities with other users. New Relic monitors what conditions those other users have set up for entities that look and behave similarly and makes recommendations to your team based on this information. This means that the way you get your data is constantly improving and is always rooted in a realtime understanding of the current observability landscape.

If you're not given recommended alert conditions, once you select an alert condition you'd like to monitor, then your team will be alerted when this signal deviates from its normal baseline, upper and lower, for at least 5 minutes by 3.00 standard deviations.
You'll get recommended alert conditions based on the entity type's defined [Golden Metrics](https://github.com/newrelic/entity-definitions). If you're not given recommended alert conditions, once you select an alert condition you'd like to monitor, then your team will be alerted when this signal deviates from its normal baseline, upper and lower, for at least 5 minutes by 3.00 standard deviations.

<img
title="Create an alert."
alt="A screenshot of creating an alert from the alert coverage gap dashboard"
alt="A screenshot of creating an alert from the alert coverage gap page"
src={accountsAddanAlert}
/>

<figcaption>
Creating an alert for an unmonitored entity.
Go to **[one.newrelic.com](https://one.newrelic.com/all-capabilities) > Alerts & AI**, select alert coverage gaps in the left navigation pane and click **Add alert**. Creating an alert for an unmonitored entity.
</figcaption>

Every alert condition needs to be routed through a [policy](/docs/alerts-applied-intelligence/new-relic-alerts/learn-alerts/rules-limits-alerts) so you will be given the option to either select an existing policy or create a new one.
Expand All @@ -66,7 +66,7 @@ Every alert condition needs to be routed through a [policy](/docs/alerts-applied
When you create an alert you will select which policy the alert will be grouped with.
</figcaption>

Once you've selected or created a policy attached to the alert condition, then you might need to add a [destination](https://docs.newrelic.com/docs/alerts-applied-intelligence/notifications/destinations). Destinations are where we send notifications about your New Relic data. You can link your notificaitions to third-party tools like Slack, Atlassian Jira, email and more.
Once you've selected or created a policy attached to the alert condition, then you might need to add a [destination](https://docs.newrelic.com/docs/alerts-applied-intelligence/notifications/destinations). Destinations are where we send notifications about your New Relic data. You can link your notificaitions to third-party tools like Slack, Atlassian Jira, email, and more.



Expand Down

This file was deleted.

This file was deleted.

This file was deleted.

Binary file modified src/images/accounts_screenshot-crop_add-an-alert.webp
Binary file not shown.
Binary file not shown.
Binary file not shown.
4 changes: 1 addition & 3 deletions src/nav/alerts-applied-intelligence.yml
Original file line number Diff line number Diff line change
Expand Up @@ -35,11 +35,9 @@ pages:
path: /docs/alerts-applied-intelligence/new-relic-alerts/alert-policies/update-or-disable-policies-conditions
- title: Infrastructure conditions
path: /docs/infrastructure/new-relic-infrastructure/infrastructure-alert-conditions/infrastructure-alerts-add-edit-or-view-host-alert-information
- title: UI condition recommendations (APM)
path: /docs/alerts-applied-intelligence/new-relic-alerts/get-started/condition-recommendations
- title: Alerts & AI overview page
path: /docs/alerts-applied-intelligence/new-relic-alerts/get-started/alerts-ai-overview-page
- title: Alert coverage gaps
- title: Alert coverage gaps and condition recommendations
path: /docs/alerts-applied-intelligence/applied-intelligence/alert-coverage-gaps
- title: Detect anomalies
pages:
Expand Down

0 comments on commit 15ca384

Please sign in to comment.