NRQL Predictions

Overview

NRQL Predictions in New Relic uses your metric's historical data patterns to predict future trends, providing insights into how metrics might behave in the future. This proactive approach helps you visualize trends and anticipate potential issues, enabling timely interventions to maintain optimal system performance. This feature currently supports predictions for both seasonal (data that has a recurring, repeatable pattern on a set cadence) and non-seasonal time series. Metrics that exhibit a strong trend or defined seasonal pattern are best suited for NRQL predictions. These predictions are best utilized when added to existing dashboards to give a quick visual indicator as to where your metrics are headed.

Examples of situations where you might want to add a prediction to your chart:

• Your application is producing more logs over the past few hours and the disk space is running out.
• Your application is steadily running out of memory, threatening to crash the entire container.
• You need to project future revenue based upon observed seasonal and trend patterns.

While NRQL Predictions themselves do not identify potential issues, they equip you with the information you need to assess trends and plan for future challenges. To generate alerts when the predictions indicate an impending problem, you can enroll for the Predictive alerts feature, currently available in public preview. Predictive Alerts works alongside NRQL Predictions to generate predictions for your metrics and alert when those predictions pass a static threshold.

Pricing

Your use of NRQL Predictions is billable during preview in accordance with your Order as applicable to the pricing model associated with your Account. New Relic Query Language queries related to use of this feature are billable as the Core Compute Product. If this feature becomes generally available, your use will be billable in accordance with your Order.

For further details on pricing, please contact our sales team or refer to your Order.

Usage

NRQL Predictions can be generated in two ways: either directly on charts you have already created or by writing a NRQL query using the PREDICT clause.

Add a prediction to an existing chart.

Predictions can only be added to charts that depict time series, such as a line or area chart. To add a prediction to an existing chart, follow these steps:

Access a line or area chart

1. Go to one.newrelic.com > All capabilities.
2. To add a prediction to a line or area chart, select it from Dashboards, or open it from Metrics and events.

Add a prediction

To add a prediction, from the menu, select Predict trend. In Data Explorer, the prediction appears on the chart. The prediction range is automatically set to 20% of the query window. To indicate where the prediction is on the chart, the area is highlighted in gray and the predicted values are connected by a dashed line.

The PREDICT clause is appended to the query and generates a prediction using the NRQL predictions default behavior. You can refine the query by fine-tuning according to your requirements and re-run it to get the updated predictions.

Sugerencia

When you add a prediction to an area chart, it changes to a line chart containing the prediction.

Add to dashboard

To add a chart containing a prediction to a dashboard:

1. Click Add to dashboard.
2. Enter a widget name.
3. Either select an existing dashboard or create a new one.

Use the PREDICT clause.

The NRQL syntax includes the PREDICT clause to streamline the use of NRQL predictions. For usage details and examples, refer to the NRQL syntax documentation.

Example of using PREDICT in a NRQL query:

FROM Transaction SELECT count(*) WHERE error IS TRUE TIMESERIES PREDICT

Copia

The default prediction on the chart appears as follows:

Default behavior

Currently, NRQL predictions only supports the Holt-Winters algorithm, also known as exponential smoothing, for both seasonal and non-seasonal time series. This is a commonly used and standard algorithm for forecasting and prediction tasks. We support hourly, daily, and weekly seasonal lengths for the Holt-Winters model.

In general, the default behavior should be sufficient for the majority of NRQL prediction use cases.

The PREDICT clause in a query comes with the following default behaviors:

• Seasonality: Automatically detects whether seasonality is present in the historic data. If seasonality is detected, the identified season length is used in the Holt-Winters seasonal algorithm. If no seasonality is found, it constructs a non-seasonal model.
• Hyperparameters: Sets the hyperparameters for the Holt-Winters algorithm based upon the seasonality and historical data.
• Prediction window: Predicts a range equal to 20% of the total time span specified in your query window.
• Historical data for training: Uses historical data from the last three query windows (the current one and the two preceding it). However, if you provide a seasonality hyperparameter that is greater than the query window, the model instead uses historical data spanning a period equal to three times the seasonality.
• Time interval: Aligns with the data point interval of the time series in the query window to ensure consistency in data projection.

Customizing the predictive model

You can customize the predictions by manually setting the training model's hyperparameters and adding the USING and BY keywords. To learn more about NRQL and its syntax, refer to NRQL documentation. Generally, the only hyperparameter most users will want to adjust will be the seasonality. The algorithm will perform best when a known seasonality (or known non-seasonality) is specified by the user. The other hyperparameters for the Holt-Winters algorithm are accessible and changeable, but default values are determined based on the historical data for your metric.

FROM Transaction SELECT count(*) WHERE error IS TRUE TIMESERIES PREDICT BY 30 minutes

FROM Transaction SELECT count(*) WHERE error IS TRUE TIMESERIES PREDICT USING 2 days

Example query with the PREDICT clause specifying custom hyperparameters, and adding the BY and USING keywords:

FROM Transaction SELECT count(*) WHERE error IS TRUE TIMESERIES PREDICT holtwinters(seasonality: AUTO, alpha: 0.2) BY 1 hour USING 2 hours

This query sets the seasonality to automatic detection and emphasizes historical data by adjusting the level smoothing factor. It predicts one hour into the future and trains the model using the query window length along with the previous two hours of historical data. The chart displays the customized prediction as follows: