Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(Alerts): Added information about loss of signal and gap filling … #4074

Merged
merged 1 commit into from Sep 27, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
Expand Up @@ -120,6 +120,15 @@ There are two violation thresholds: critical (red) and warning (yellow). Define
Warning violations do not open incidents. A critical violation can open incidents, but you must define that decision through your [incident preferences](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#incident-practices).
</Callout>

## Decide what happens when there's no signal

Loss of signal occurs when New Relic stops receiving data for a while; technically, we detect loss of signal after a significant amount of time has elapsed since data was last received in a time series. Loss of signal can be used to trigger or resolve a violation, which you can use to set up alerts.

You can configure loss of signal settings by condition in the UI or [configure loss of signal via the NerdGraph API](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/alerts-nerdgraph/nerdgraph-api-loss-signal-gap-filling/#loss-of-signal).

## Use non-null values when there's no signal

By default, gaps in data signals are filled with null values. In cases where you need to be able to create conditions based on those data gaps, you can fill gaps with a custom value or the last known value. You can configure this setting by condition in the UI or [configure gap filling values via NerdGraph](/docs/alerts-applied-intelligence/new-relic-alerts/advanced-alerts/alerts-nerdgraph/nerdgraph-api-loss-signal-gap-filling/#customize)

## Define your incident preferences [#incident-practices]

Expand All @@ -139,7 +148,6 @@ When a policy and its conditions have a focused scope (like managing the perform

Decide how you get incident notifications by using our [notification channel best practices](/docs/new-relic-solutions/best-practices-guides/alerts-applied-intelligence/alerts-best-practices/#channel-practices).


## Select your notification channels [#channel-practices]

Tailor notifications to the most useful channel and policy so you can avoid alert fatigue and help the right personnel receive and respond to incidents they care about in a systematic way.
Expand All @@ -154,7 +162,6 @@ For vital notifications and incident responses, select a notification channel th

Do not rely on email for quick notifications in case of delays.


## Understand muting rules [#mute-practices]

Mute alerts during routine events, such as maintenance or planned downtime.
Expand All @@ -163,10 +170,10 @@ You can also silence a policy, a specific entity, and a condition when needed. I

If you're new to Alerts, learn how to [create and manage muting rules](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/muting-rules-suppress-notifications/).


## What's next?

To learn more about using alerts:

* Learn about the [API](/docs/alerts/rest-api-alerts/new-relic-alerts-rest-api/rest-api-calls-new-relic-alerts).
* Read technical details about [min/max limits and rules](/docs/alerts/new-relic-alerts/getting-started/minimum-maximum-values).
* Read more about about [when you might want to use loss-of-signal and gap-filling settings](https://discuss.newrelic.com/t/relic-solution-how-can-i-figure-out-when-to-use-gap-filling-and-loss-of-signal/120401).