[DO NOT MERGE](Feat: NRQL Predictions): Removed preview callout and updated pricing section for GA #20887
Conversation
…pdated pricing section for GA. Expected to be published on 30th June. Sync with Alex (PM) before merging.
sujitnewrelic
added
content
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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). |
sujitnewrelic
changed the title
| @@ -887,6 +886,18 @@ Here're some examples: | |||
| FROM Transaction SELECT count(*) WHERE error IS TRUE TIMESERIES PREDICT USING 2 days | |||
| ``` | |||
| </Collapser> | |||
|
|
|||
| <Collapser id="slideby-with-predict" title={<>Use the <InlineCode>SLIDE BY</InlineCode> clause.</>}> | |||
| If your forecast has a lot of variation over short periods of time, it may be difficult to see the trends in the data. To smoothen out the spiky chart, you can use the [`SLIDE BY` clause](/#slide-by). This clause aggregates the data into overlapping time windows with a specified slide interval, which can help reduce noise in the data and make it easier to see trends. | |||
There was a problem hiding this comment.
The link for SLIDE BY is incorrect here. We should update this to be: /docs/nrql/nrql-syntax-clauses-functions/#slide-by
| @@ -887,6 +886,18 @@ Here're some examples: | |||
| FROM Transaction SELECT count(*) WHERE error IS TRUE TIMESERIES PREDICT USING 2 days | |||
| ``` | |||
| </Collapser> | |||
|
|
|||
| <Collapser id="slideby-with-predict" title={<>Use the <InlineCode>SLIDE BY</InlineCode> clause.</>}> | |||
| If your forecast has a lot of variation over short periods of time, it may be difficult to see the trends in the data. To smoothen out the spiky chart, you can use the [`SLIDE BY` clause](/#slide-by). This clause aggregates the data into overlapping time windows with a specified slide interval, which can help reduce noise in the data and make it easier to see trends. | |||
There was a problem hiding this comment.
I believe we want to use "predict" rather than "forecast " here. Could we change the first sentence of the above text to:
Smooth out your prediction trends using the [`SLIDE BY` clause](/docs/nrql/nrql-syntax-clauses-functions/#slide-by) if the data in your line chart varies significantly.
…
Expected to be published on 30th June. Sync with Alex (PM) before merging.