Skip to content

Commit

Permalink
fix(Outlier EOL): Callout
Browse files Browse the repository at this point in the history 
Fixes #6764
  • Loading branch information
@barbnewrelic
barbnewrelic committed Mar 24, 2022
1 parent d29b404 commit 5e545b1
Show file tree
Hide file tree
Showing 2 changed files with 19 additions and 19 deletions.
18 changes: 7 additions & 11 deletions ...lic-alerts/advanced-alerts/advanced-techniques/outlier-detection-nrql-alert.mdx
View file
Expand Up @@ -12,17 +12,17 @@ redirects:
- /docs/alerts-applied-intelligence/new-relic-alerts/alert-conditions/outlier-detection-nrql-alert
---

[Alerts](/docs/alerts/new-relic-alerts/getting-started/introduction-new-relic-alerts) offers [NRQL conditions](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) in three [threshold types](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries#threshold-types): static, baseline, and outlier. This document explains how the outlier threshold type works, gives some [example use cases and NRQL queries](#example-use-cases), and explains how to [create an outlier condition](#create).

<Callout variant="important">
NRQL alerts do **not** affect alerts policies for a Synthetic monitor. For example, [muting a NRQL alert](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/muting-rules-suppress-notifications) will **not** mute a [Synthetic monitor's alerts.](/docs/synthetics/synthetic-monitoring/using-monitors/alerts-synthetic-monitoring#alerts-existing-monitor)
<Callout variant="important" title="EOL NOTICE">
As of March 31, 2022, we're discontinuing support for several capabilities, including NRQL outlier alert conditions. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com/t/nrql-outlier-alert-conditions-end-of-life/164167) and our [transition guide](https://docs.newrelic.com/docs/alerts-applied-intelligence/transition-guide#) for alert capabilities.
</Callout>

## What is outlier detection? [#feature]
Our alerting solution offers [NRQL conditions](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries) for static and baseline [threshold types](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries#threshold-types). This document explains how the outlier threshold type works, gives some [example use cases and NRQL queries](#example-use-cases), and explains how to [create an outlier condition](#create).

NRQL alerts do **not** affect alerts policies for a synthetic monitor. For example, [muting a NRQL alert](/docs/alerts-applied-intelligence/new-relic-alerts/alert-notifications/muting-rules-suppress-notifications) will **not** mute a [synthetic monitor's alerts](/docs/synthetics/synthetic-monitoring/using-monitors/alerts-synthetic-monitoring#alerts-existing-monitor).

In software development and operations, it is common to have a group consisting of members you expect to behave approximately the same. For example: for servers using a load balancer, the traffic to the servers may go up or down, but the traffic for all the servers should remain in a fairly tight grouping. See outlier detection in action in this NerdBytes video (2:51 minutes).
## What is outlier detection? [#feature]

<Video id="_Hh7HZViJW8" type="youtube" />
In software development and operations, it is common to have a group consisting of members you expect to behave approximately the same. For example: for servers using a load balancer, the traffic to the servers may go up or down, but the traffic for all the servers should remain in a fairly tight grouping.

The NRQL alert outlier detection feature parses the data returned by your [faceted NRQL query](/docs/insights/nrql-new-relic-query-language/nrql-resources/nrql-syntax-components-functions#sel-facet) and:

Expand Down Expand Up @@ -99,10 +99,6 @@ For more details on how this feature works, see [Outlier rules and logic](#rules

## Create an outlier alert condition [#create]

<Callout variant="important" title="EOL NOTICE">
As of March 31, 2022, we're discontinuing support for several capabilities, including NRQL outlier alert conditions. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com/t/nrql-outlier-alert-conditions-end-of-life/164167) and our [transition guide](https://docs.newrelic.com/docs/alerts-applied-intelligence/transition-guide#) for alert capabilities.
</Callout>

To create a NRQL alert that uses outlier detection:

1. When creating a condition, under **Select a product**, select **NRQL**.
Expand Down
20 changes: 12 additions & 8 deletions ...intelligence/new-relic-alerts/alert-conditions/create-nrql-alert-conditions.mdx
View file
Expand Up @@ -57,7 +57,7 @@ Once you've named and customized your condition, you can add it to an existing p

## NRQL alert syntax [#syntax]

Here's the basic syntax for creating all NRQL alert conditions. The [`FACET` clause](#facet) is required for outlier condition types. It's optional for static and baseline.
Here's the basic syntax for creating all NRQL alert conditions. The [`FACET` clause](#facet) is optional for static and baseline condition types.

```
SELECT function(attribute)
Expand Down Expand Up @@ -139,15 +139,15 @@ SELECT function(attribute)

<tr>
<td id="facet">
`FACET attribute`

**Required for outlier conditions**
`FACET` attribute
</td>

<td>
Include an optional `FACET` clause in your NRQL syntax depending on the [threshold type](#threshold-types): static or baseline.
Include an optional `FACET` clause in your NRQL syntax depending on the [threshold type](#threshold-types) (static or baseline).

Use the [`FACET`](/docs/insights/nrql-new-relic-query-language/nrql-resources/nrql-syntax-components-functions) clause to separate your results by attribute and alert on each attribute independently. No `LIMIT` clause is allowed, but all queries will receive the maximum number of facets possible. Faceted queries can return a maximum of 5000 values for [static and baseline](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries#threshold-types) conditions and a maximum of 500 values for [outlier](/docs/alerts/new-relic-alerts/defining-conditions/outlier-detection-nrql-alert) conditions.
Use the [`FACET`](/docs/insights/nrql-new-relic-query-language/nrql-resources/nrql-syntax-components-functions) clause to separate your results by attribute and alert on each attribute independently. No `LIMIT` clause is allowed, but all queries will receive the maximum number of facets possible.

Faceted queries can return a maximum of 5000 values for [static and baseline](/docs/alerts/new-relic-alerts/defining-conditions/create-alert-conditions-nrql-queries#threshold-types) conditions and a maximum of 500 values for [outlier](/docs/alerts/new-relic-alerts/defining-conditions/outlier-detection-nrql-alert) conditions.

<Callout variant="important">
If the query returns more than the maximum number of values, the alert condition can't be created. If you create the condition and the query returns more than this number later, the alert will fail. Modify your query so that it returns a fewer number of values.
Expand Down Expand Up @@ -276,7 +276,7 @@ Some elements of NRQL used in charts don’t make sense in the streaming context

## NRQL alert threshold examples [#examples]

Here are some common use cases for NRQL conditions. These queries will work for static and baseline [condition types](#threshold-types). The outlier condition type will require additional [`FACET` clauses](#facet).
Here are some common use cases for NRQL conditions. These queries will work for static and baseline [condition types](#threshold-types).

<CollapserGroup>
<Collapser
Expand Down Expand Up @@ -640,10 +640,14 @@ When you create a NRQL alert, you can choose from different types of conditions:

<tr>
<td>
[Outlier](/docs/outlier-detection-nrql-alerts)
Outlier (EOL)
</td>

<td>
<Callout variant="important" title="EOL NOTICE">
As of March 31, 2022, we're discontinuing support for several capabilities, including NRQL outlier alert conditions. For more details, including how you can easily prepare for this transition, see our [Explorers Hub post](https://discuss.newrelic.com/t/nrql-outlier-alert-conditions-end-of-life/164167) and our [transition guide](https://docs.newrelic.com/docs/alerts-applied-intelligence/transition-guide#) for alert capabilities.
</Callout>

Looks for group behavior and values that are outliers from those groups. Uses the same NRQL query form as the static type, but requires a `FACET` clause.
</td>
</tr>
Expand Down

0 comments on commit 5e545b1

Please sign in to comment.