Update "Historical data for training" sections within Predict docs #21047
+2
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hi @amohammed-2 👋 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). |
amohammed-2
changed the title
WriteMayur
reviewed
Jun 30, 2025
WriteMayur
reviewed
Jun 30, 2025
src/content/docs/query-your-data/explore-query-data/use-charts/nrql-predictions.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: WriteMayur <[email protected]>
…/nrql-predictions.mdx Co-authored-by: WriteMayur <[email protected]>
WriteMayur
added
content
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
We've recently updated the default behavior in how we gather historical data for training and have updated our public facing documentation accordingly so customers are aware of the changes.
Overall, we use a historical data spanning
3 * seasonalitywhen we have a PREDICT query with the following:USINGclausehyperparameterwith aseasonalitywhich is notNONEorAUTOseasonalitythat's greater than the query duration