Documents the model memory estimation in the edit job flyout

[nastasha-solomon]

Summary

Documents the Apply estimation option in the Kibana edit job flyout for anomaly detection and data frame analytics jobs to fix #6495.

Previews

• Working with anomaly detection at scale | Set the model memory limit - Added a sentence pointing users to Apply estimation in the edit flyout as a faster alternative to calling the estimate API manually. Also updated the tip to lead with the new UI option before the API fallback.

• Run a job | Model memory limits -
  Added a new paragraph in the model memory limit section. This is the primary how-to page for running AD jobs. Users who hit memory issues land here, so it's the right place to surface the new shortcut before they resort to recreating the job.

• Data frame analytics limitations: Made two changes:

  • Corrected an overbroad limitation statement ("You cannot update DFA configurations"). It now accurately says most settings can't be updated, but model_memory_limit can. Added the Apply estimation option alongside the API.
  • Expanded the memory limitation section with actionable guidance (how to estimate, how to fix a job that fails to start due to memory), which was previously missing entirely.

• Working with data frame analytics at scale | 7. Set the model memory limit- New section that explains what model_memory_limit controls, how to update it via API or the new UI option, and how to get an estimate. This section was modeled after the equivalent section on the "Working with anomaly detection at scale" page.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes - Cursor + Auto
• No

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• explore-analyze/machine-learning/anomaly-detection/anomaly-detection-scale.md
• explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md
• explore-analyze/machine-learning/data-frame-analytics/ml-dfa-limitations.md
• explore-analyze/machine-learning/data-frame-analytics/ml-dfa-scale.md

[github-actions]

Vale Linting Results

Summary: 5 suggestions found

💡 Suggestions (5)

File	Line	Rule	Message
explore-analyze/machine-learning/anomaly-detection/anomaly-detection-scale.md	85	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'.
explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md	103	Elastic.Semicolons	Use semicolons judiciously.
explore-analyze/machine-learning/anomaly-detection/ml-ad-run-jobs.md	110	Elastic.WordChoice	Consider using 'efficiently' instead of 'simply', unless the term is in the UI.
explore-analyze/machine-learning/data-frame-analytics/ml-dfa-scale.md	84	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.
explore-analyze/machine-learning/data-frame-analytics/ml-dfa-scale.md	86	Elastic.Wordiness	Consider using 'all' instead of 'all of '.

---

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.