|
| 1 | +--- |
| 2 | +title: Predictive capability |
| 3 | +tags: |
| 4 | + - Alerts |
| 5 | + - Alert conditions |
| 6 | + - Predictive alerts |
| 7 | + - Predictive threshold |
| 8 | +translate: |
| 9 | + - jp |
| 10 | +metaDescription: 'Set predictive threshold on your chart.' |
| 11 | +redirects: |
| 12 | + |
| 13 | +freshnessValidatedDate: never |
| 14 | +--- |
| 15 | +<Callout title="preview"> |
| 16 | + We're still working on this feature, but we'd love for you to try it out! |
| 17 | + |
| 18 | + This feature is currently provided as part of a preview program pursuant to our [pre-release policies](/docs/licenses/license-information/referenced-policies/new-relic-pre-release-policy). |
| 19 | +</Callout> |
| 20 | + |
| 21 | +<DNT>**Predictive Alerts**</DNT> in New Relic uses historical data to build models that predict when a static threshold is going to be breached. You can specify how far into the future you want to predict, providing flexibility in your alerting strategy. When a value is predicted to reach the static threshold within the future window you have set, a predictive alert event triggers with the event title prefix <DNT>**Prediction:**</DNT>, allowing you to take corrective measures before potential disruptions occur. |
| 22 | + |
| 23 | +<Callout variant="tip"> |
| 24 | + New Relic currently uses the [Holt-Winters model](https://en.wikipedia.org/wiki/Exponential_smoothing#Triple_exponential_smoothing_(Holt_Winters)) for predicting, which supports hourly, daily, and weekly seasonal patterns and trends in your data. |
| 25 | +</Callout> |
| 26 | + |
| 27 | +To enable <DNT>**Predictive Alerts**</DNT>, enable <DNT>**[NRQL Predictions](/docs/query-your-data/explore-query-data/use-charts/nrql-predictions)**</DNT> (Now in public preview), which provides the query functionality required for evaluation of predictive thresholds. The <DNT>**NRQL Predictions**</DNT> and <DNT>**Predictive Alerts**</DNT> features are available only to **[Advanced Compute](https://newrelic.com/pricing/compute#pricing_plan-compute)** customers. To enroll, navigate to <DNT>**[one.newrelic.com > Administration](https://one.newrelic.com//admin-portal) > Preview & Trials**</DNT>, and enable <DNT>**NRQL Predictions**</DNT> and <DNT>**Predictive Alerts**</DNT> features. |
| 28 | + |
| 29 | +## Set predictive threshold for an alert condition [#set-predictive-threshold] |
| 30 | +To set or update an alert condition with the predictive capability, follow these steps: |
| 31 | + |
| 32 | +<Steps> |
| 33 | + |
| 34 | + <Step> |
| 35 | + ### Edit or set up a new alert condition [#create-alert-condition] |
| 36 | + |
| 37 | + #### To edit an existing alert condition: |
| 38 | + 1. Select an alert condition from <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Alert Conditions**</DNT>, and edit the <DNT>**Signal behavior**</DNT>. |
| 39 | + 2. From the <DNT>**Signal behavior**</DNT> section, click <DNT>**Edit**</DNT>. The <DNT>**Set thresholds**</DNT> page opens. |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | + #### To set up a new alert condition: |
| 44 | + 1. Go to <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Alert Conditions**</DNT>. |
| 45 | + 2. Click <DNT>**+ New alert condition > Use guided mode**</DNT>. You can also write a NRQL query to create an alert condition. |
| 46 | + 3. If you are using the guided mode, follow the on-screen instuctions till you are at the <DNT>**Set thresholds**</DNT> section. If you are writing a NRQL query, run the query to get the data on the chart, and click <DNT>**Next**</DNT> to get to the <DNT>**Set thresholds**</DNT> section. |
| 47 | + |
| 48 | + </Step> |
| 49 | + |
| 50 | + <Step> |
| 51 | + ### Set static thresholds [#set-static-thresholds] |
| 52 | + |
| 53 | + Under the <DNT>**Set condition thresholds**</DNT> section of the <DNT>**Set thresholds**</DNT> page, set a static threshold as follows: |
| 54 | + 1. Select <DNT>**Static**</DNT>. |
| 55 | + 2. Select severity level for the alert condition. |
| 56 | + 3. Set the threshold value. |
| 57 | + |
| 58 | + </Step> |
| 59 | + |
| 60 | + <Step> |
| 61 | + ### Set predictive threshold [#set-predictive-threshold] |
| 62 | + |
| 63 | + 1. Under <DNT>**Set condition thresholds**</DNT> section, enable the <DNT>**Predict future behavior**</DNT> toggle. |
| 64 | + 2. Set a look-ahead time for the predictive threshold. This is how far you want to look into the future to predict the threshold breach. |
| 65 | + * **Minimum look-ahead time**: Two times of the [window duration](/docs/alerts/create-alert/create-alert-condition/alert-conditions/#window-duration). |
| 66 | + * **Maximum look-ahead time**: 360 times of the [window duration](/docs/alerts/create-alert/create-alert-condition/alert-conditions/#window-duration). |
| 67 | + <Callout variant="tip"> |
| 68 | + To look further ahead into the future, you can increase the [window duration](/docs/alerts/create-alert/create-alert-condition/alert-conditions/#window-duration). |
| 69 | + </Callout> |
| 70 | + <Callout variant="tip"> |
| 71 | + When the window duration is set to 1 minute, the model utilizes historical data from the past 2.5 days to generate predictions. To increase the span of the historical data for model processing, you can increase the [window duration](/docs/alerts/create-alert/create-alert-condition/alert-conditions/#window-duration). |
| 72 | + </Callout> |
| 73 | + |
| 74 | + 3. Set the predicted alert event behavior, when the actual signal crosses the threshold. |
| 75 | + * Close predicted alert event and open an actual alert event (recommended). |
| 76 | + * Continue to keep the predicted alert event open. |
| 77 | + |
| 78 | + <img |
| 79 | + title="predictive-alerts" |
| 80 | + alt="predictive-alerts" |
| 81 | + src="/images/predictive-alerts.webp" |
| 82 | + /> |
| 83 | + |
| 84 | + <figcaption> |
| 85 | + <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Alerts > Alert Conditions**</DNT>: Predict future behavior. |
| 86 | +</figcaption> |
| 87 | + |
| 88 | +<Callout variant="tip"> |
| 89 | + By selecting the <DNT>**Close predicted alert event and open one for the occurring event.**</DNT> option, you can distinguish between predicted and actual alert events. |
| 90 | +</Callout> |
| 91 | + |
| 92 | + |
| 93 | + </Step> |
| 94 | + |
| 95 | + <Step> |
| 96 | + ### Save conditions [#save-conditions] |
| 97 | + Refer [Add alert condition details](/docs/alerts/create-alert/create-alert-condition/alert-conditions/#add-details) to complete the alert condition setup, and then save it. |
| 98 | + |
| 99 | + </Step> |
| 100 | + |
| 101 | +</Steps> |
| 102 | + |
| 103 | +## Post-promotion behavior [#post-promotion-behavior] |
| 104 | +As the Predictive capability feature is in public preview, it is available for a limited promotion period. After this period ends, the following changes occur in alerts: |
| 105 | +* Predictive alert events are no longer available in the UI. |
| 106 | +* Alert conditions are re-registered with only the static portion of the threshold. This re-registration resets the aggregation window, potentially delaying alert detection if a condition's threshold is breached during the process. |
0 commit comments