Update "Find slow queries" to reference query logs instead of audit logs

[Copilot]

The "Find slow queries" section pointed users to audit logs to determine query source. Since 9.4, query logs do this properly: one config, end-to-end request duration, every query type. So the section now leads with that.

leem and Claude cleaned up after Copilot's initial flailing

[leemthompo]

@copilot we should version tags to keep the information clearly valid for users on different 9.x versions

introruce the new information on a new line and use an inline applies_to tag to make it clear that this is the recommendation for 9.5+

[Copilot]

@copilot we should version tags to keep the information clearly valid for users on different 9.x versions

introruce the new information on a new line and use an inline applies_to tag to make it cle...

Done in commit Add inline applies_to version tag for query logs recommendation (9.5+). I restored the audit logging info for older versions and added the query logs recommendation on a new line with an inline {applies_to} tag scoped to stack: ga 9.5.

[leemthompo]

@copilot put query logging first instead of the current approach which introduces the old approach first and then forces you to read through that and then says "For a more streamlined approach"

[Copilot]

@copilot put query logging first instead of the current approach which introduces the old approach first and then forces you to read through that and then says "For a more streamlined approach"

Reordered in the latest commit — query logging now comes first with the {applies_to} tag, followed by the audit logging approach introduced as a fallback "for earlier versions".

[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

• troubleshoot/elasticsearch/troubleshooting-searches.md

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 1 suggestion found

💡 Suggestions (1): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
troubleshoot/elasticsearch/troubleshooting-searches.md	241	Elastic.WordChoice	Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.

---

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.

[yetanothertw]

👍 LGTM, thank you