[Draft for feb release]feat(On-demand forecast): Added On-demand forecasting content for PP #19667
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,129 @@ | ||
| --- | ||
| title: On-demand forecasting | ||
| tags: | ||
| - Forecast on a chart | ||
| redirects: | ||
| freshnessValidatedDate: never | ||
| --- | ||
| <Callout title="preview"> | ||
| We're still working on this feature, but we'd love for you to try it out! | ||
|
Check notice on line 9 in src/content/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting.mdx
|
||
|
|
||
| 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). | ||
| </Callout> | ||
|
|
||
|
|
||
| Forecasting in New Relic involves using historical data to predict future trends and potential performance issues. | ||
| By analyzing historical data, forecasting provides insights in to how these metrics might behave in the future. | ||
|
|
||
| This proactive approach helps you to anticipate issues before they occur, enabling timely interventions to maintain optimal system performance. | ||
|
Check notice on line 17 in src/content/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting.mdx
|
||
| Forecasting is a powerful tool for decision-making, helping teams to allocate resources effectively, and plan for potential challenges. | ||
|
Check notice on line 18 in src/content/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting.mdx
|
||
|
|
||
| <Callout variant="tip"> | ||
| New Relic currently uses the Holt-Winters model for forecasting, which reliably captures seasonal patterns and trends in your data. | ||
|
There was a problem hiding this comment. It'd be nice to have an explanatory link for Holt-Winters, maybe this one: https://en.wikipedia.org/wiki/Exponential_smoothing#Triple_exponential_smoothing_(Holt_Winters) |
||
| </Callout> | ||
|
|
||
| ## Getting started [#getting-started-on-demand-forecast] | ||
| Waiting for the content to add here. | ||
|
|
||
| <img | ||
| title="On-demand forecasting" | ||
| alt="On-demand forecasting" | ||
| src="/images/on-demand-forecast.webp" | ||
| /> | ||
|
|
||
| <figcaption> | ||
| <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Metrics and events**</DNT>: Forecasted view. | ||
| </figcaption> | ||
|
|
||
| ## Create a forecast [#create-forecast] | ||
| Follow these steps to create a forecast on a line or area chart in New Relic: | ||
|
|
||
| <Steps> | ||
|
|
||
| <Step> | ||
| ### Access a line or area chart [#access-a-line-chart] | ||
|
|
||
| 1. Go to [one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities). | ||
| 2. Choose a line or area chart from <DNT>**Dashboards**</DNT>, or open it from <DNT>**Metrics and events**</DNT>. | ||
| </Step> | ||
|
|
||
| <Step> | ||
| ### Make a forecast [#make-a-forecast] | ||
|
|
||
| In the upper-right corner of the chart, select <DNT>**Make a forecast**</DNT> from the <DNT>**Options**</DNT> menu. | ||
| The forecasted chart opens in <DNT>**Data explorer**</DNT>. | ||
| The forecast range is automatically set to 20% of the query window, and highlighted in gray. The graph appears in dotted lines within the forecast range. | ||
|
|
||
| The chart query is pre-populated with the `FORECAST` function. you can [refine the query](#customize-forecastsing-range) as per your requirements and run it to get the updated graph. | ||
|
Check notice on line 56 in src/content/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting.mdx
|
||
|
There was a problem hiding this comment. There's a typo in the customize-forecasting-range anchor. |
||
|
|
||
| </Step> | ||
|
|
||
| <Step> | ||
| ### Add to dashboard [#add-to-dashboard] | ||
|
|
||
| 1. Click <DNT>**Add to dashboard**</DNT>. | ||
| 2. Enter a widget name. | ||
| 3. Search and slect a dashboard in which you want to add the widget, or create a new dashboard for it. | ||
|
|
||
|
|
||
| You can now view the forecasted chart on the selected dashboard. | ||
|
|
||
| </Step> | ||
|
|
||
| </Steps> | ||
|
|
||
| ## Default forecasting range [#default-forecasting-range] | ||
| The default forecast range in New Relic provides a baseline for projecting future trends based on historical data. | ||
| This range is automatically set to ensure users receive meaningful insights without a manual NRQL configuration. | ||
| Understanding these default settings helps users make informed decisions about when and how to customize their forecasts for more precise predictions. | ||
|
|
||
| ### Default values [#default-values] | ||
| When you create a forecast in New Relic, the system automatically appends the `FORECAST` function to the existing chart query, and sets the following default values: | ||
| * **Forecast range**: The forecast covers 20% of the total time specified in your query window, allowing you to see a short-term projection based on current trends. | ||
| * **Historical data**: The system analyzes historical data that is twice the length of your query window, providing a comprehensive dataset to enhance the accuracy of the forecast. | ||
|
Check failure on line 81 in src/content/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting.mdx
|
||
|
|
||
|
|
||
| ### Customize the forecasting range [#customize-forecastsing-range] | ||
| You can customize a chart forecast through NRQL query to adjust the projection window and refine the accuracy as per your requirements. | ||
|
Check notice on line 85 in src/content/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting.mdx
|
||
|
There was a problem hiding this comment. "through NRQL query" sounds a little awkward, maybe "through editing the NRQL query"? |
||
| Refer to the [NRQL documentation](/docs/nrql/get-started/introduction-nrql-new-relics-query-language) to get familiar with the NRAQL query. | ||
|
There was a problem hiding this comment. "to get familiar with NRQL" or "to get familiar with NRQL querying" |
||
|
|
||
| When you create a forecast of a chart, the revised NRQL query appears with the `FORECAST` function, as in the following example: | ||
|
|
||
| ```sql | ||
| FROM NrAiIncidentDebug SELECT count(*) WHERE environment like 'production' | ||
| TIMESERIES 1 hour facet event since 1 day ago FORECAST | ||
|
There was a problem hiding this comment. I'd capitalize the keywords, i.e. FROM NrAiIncidentDebug SELECT count(*) WHERE environment LIKE 'production' |
||
| ``` | ||
| The forecasted chart appears as following: | ||
|
|
||
| <img | ||
| title="default forecast" | ||
| alt="default forecast" | ||
| src="/images/on-demand-forecast-default.webp" | ||
| /> | ||
|
|
||
| <figcaption> | ||
| <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > dashboards**</DNT>: default forecast. | ||
|
|
||
| </figcaption> | ||
|
|
||
| You can customize the query using the following keywords to refine the forecast: | ||
| * **`by <a time range>`**: Project the forecast up to the specified time range. | ||
|
|
||
| * **`using <a historical data span>`**: Analyze historical data from the defined span to project the forecast. | ||
|
|
||
|
|
||
| Example: | ||
|
|
||
| ```sql | ||
| FROM NrAiIncidentDebug SELECT count(*) WHERE environment like 'production' | ||
| TIMESERIES 1 hour facet event since 1 day ago FORECAST by 1 day using 30 days | ||
|
There was a problem hiding this comment. Same re: capitalizing keywords |
||
| ``` | ||
|
|
||
| The refined forecast of the chart appears as following: | ||
|
|
||
| <img | ||
| title="Refined forecast" | ||
| alt="Refined forecast" | ||
| src="/images/on-demand-forecast-refined.webp" | ||
| /> | ||
|
|
||
| <figcaption> | ||
| <DNT>**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > dashboards**</DNT>: refined forecast. | ||
|
|
||
| </figcaption> | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd capitalize the keywords that aren't already capitalized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.