[Draft for feb release]feat(On-demand forecast): Added On-demand forecasting content for PP #19667
Conversation
Updated the existing topics and added a new one for On-demand forecasting capability on chart.
sujitnewrelic
added
content
|
Hi @sujitnewrelic 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
- Added SS - Updated syntax - Add customization
|
| 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> | ||
|
|
||
| If you have opted for On-demand forecasting, you can add forecast to line and area charts, which uses historical data to project future trends. |
There was a problem hiding this comment.
Should it be On-Demand Forecasting, or should "On-demand forecasting" be otherwise set out as the name of a feature?
I'd also say "...you can add FORECAST to...", since it's a NRQL keyword, or change it to "you can add forecasting..." or "you can add a forecast..."
There was a problem hiding this comment.
- Rechecking with Meda on the official feature name. I understand, it is "On-demand forecasting"
- Changes it to "you can add a forecast..."
| Select <DNT>**Make a forecast**</DNT> from the <DNT>**Options**</DNT> menu on the chart. | ||
| The forecast apears in dotted lines with the defult range set to 20% of the query window, highlighted in gray. | ||
|
|
||
| You can further refine your query for the forecast by adjusting the range as per your need. Refer [on-demand forecasting](/docs/query-your-data/explore-query-data/use-charts/on-demand-forecasting) for more details. |
| @@ -46,6 +47,10 @@ To access the Data Explorer, navigate to the bottom <DNT>**Query your data**</DN | |||
| 1. **Define the Scope**: Select the data type (metric, event, or log), the account, and the entities. | |||
| 2. **Select the Time Range**: Use the time picker to define the time range for your query. | |||
| 3. **Build Your Search**: Use the blocks on the left to browse the available data and construct your search. Blocks are searchable, and you can use the actions in the action menu to create and update your query. | |||
| 4. **Refine your query**: Modify your query by adding filters, facets, and aggregations. | |||
| 5. **Customize the chart visualization**: Upgrade your chart visualization from the customization options available. | |||
| 6. **Make forecast for a line chart (If opted for on-demand forecast)**: Use <DNT>**Make a forecast**</DNT> from the **Options** menu to get a forecasted trend. | |||
There was a problem hiding this comment.
Make a forecast for a line chart?
|
|
||
|
|
||
| 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. |
| Forecasting is a powerful tool for decision-making, helping teams to allocate resources effectively, and plan for potential challenges. | ||
|
|
||
| <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)
| 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. |
There was a problem hiding this comment.
There's a typo in the customize-forecasting-range anchor.
|
|
||
| 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. |
|
|
||
|
|
||
| ### 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. |
There was a problem hiding this comment.
"through NRQL query" sounds a little awkward, maybe "through editing the NRQL query"?
|
|
||
| ### 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. | ||
| 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"
|
|
||
| ```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'
TIMESERIES 1 hour FACET event SINCE 1 day ago 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. |
|
|
||
| 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. |
|
|
||
| ```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
|
|
||
| ```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 that aren't already capitalized.
| The `FORECAST` clause allows you to project future data trends based on historical data. | ||
| By default, the forecast window is set to 20% of the query window, and the historical data span is twice the query window. | ||
|
|
||
| you can customize these values using the `by <time range>` and `using <a historical data span>` parameters to tailor the forecast to your specific needs. |
There was a problem hiding this comment.
Same re: capitalizing keywords
|
|
|
|
|
Updated the existing topics and added a new one for On-demand forecasting capability on chart.