Adds section to Security prebuilt ML jobs reference table #5627
Merged
Conversation
Contributor
🔍 Preview links for changed docs |
Contributor
✅ Vale Linting ResultsNo issues found on modified lines! 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. |
nastasha-solomon
approved these changes
Mar 25, 2026
benironside
approved these changes
Mar 25, 2026
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.
Summary
Closes elastic/security-docs#2974
Adds a "Data requirements" section to the Security anomaly detection configurations page to clarify what users need to use prebuilt ML jobs.
This addresses the core request in #2974: users can now see that they need to install one of the supported integrations listed in each job's table, and that no additional configuration is required beyond the integration's standard setup.
Changes
Supported Integrationscolumn and integration documentationGenerative AI disclosure
To help us ensure compliance with the Elastic open source and documentation guidelines, please answer the following:
-->