Add CPS ML datafeed troubleshooting docs for serverless#7403
Draft
valeriy42 wants to merge 3 commits into
Draft
Conversation
Publish user-facing diagnose/resolve pages for cross-project anomaly detection datafeeds, with a hub under Elasticsearch troubleshoot and links from CPS and ML run-jobs topics. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
Co-authored-by: Cursor <cursoragent@cursor.com>
valeriy42
marked this pull request as draft
July 16, 2026 10:51
The CPS user guide lives under explore-analyze, not deploy-manage. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Contributor
Elastic Docs Style Checker (Vale)Summary: 1 warning, 29 suggestions found
|
| File | Line | Rule | Message |
|---|---|---|---|
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-stale-project-reference.md | 38 | Elastic.Spelling | 'misrouted' is a possible misspelling. |
💡 Suggestions (29): Optional style improvements. Apply when helpful.
| File | Line | Rule | Message |
|---|---|---|---|
| troubleshoot/elasticsearch/machine-learning.md | 41 | Elastic.Clone | Use Clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 2 | Elastic.Clone | Use Clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 12 | Elastic.Clone | Use Clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 14 | Elastic.Clone | Use Cloning only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 14 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 20 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 24 | Elastic.Clone | Use cloned only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 26 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 30 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 36 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 36 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 38 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 46 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 46 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-clone-project-routing.md | 56 | Elastic.Clone | Use clone only when referring to cloning a GitHub repository or creating a copy that is linked to the original. Often confused with 'copy' and 'duplicate'. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-cloud-token-mint-failure.md | 40 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-cloud-token-runtime-failure.md | 14 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-cloud-token-runtime-failure.md | 83 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-field-mapping-mismatch.md | 26 | Elastic.Semicolons | Use semicolons judiciously. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-field-mapping-mismatch.md | 26 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-field-mapping-mismatch.md | 55 | Elastic.Semicolons | Use semicolons judiciously. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-routing-no-match.md | 14 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-routing-no-match.md | 40 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-scope-too-broad.md | 43 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-search-scope-changed.md | 30 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-search-scope-changed.md | 75 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-stale-project-reference.md | 14 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-stale-project-reference.md | 62 | Elastic.WordChoice | Consider using 'can, might' instead of 'may', unless the term is in the UI. |
| troubleshoot/elasticsearch/machine-learning/cps-datafeed-stale-project-reference.md | 62 | Elastic.Semicolons | Use semicolons judiciously. |
The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.
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
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.
troubleshoot/elasticsearch/with eleven topic pages for cross-project anomaly detection datafeeds (linked project skips, scope changes, routing, cloud token mint/runtime, field mapping, schema drift, scope, migration, and clone routing).troubleshoot/toc.ymland link from cross-project search, project routing, and ML run-jobs topics.applies_to, Diagnose/Resolve structure, and verbatim searchable error message examples; no internal engineering references.