Clarify Kibana scalability guidance around interactive and background workloads

[Copilot]

closes elastic/docs-content-internal#1135

The Kibana production guidance described longstanding capabilities as “new” and used an imprecise “user activity” framing for scalability. This update rewrites the section to describe the actual load model without implying a recent architectural shift.

• Problem

  • The existing copy suggested Kibana scalability had recently changed because of alerting and detection features.
  • It also contrasted “user activity” with “automated processes,” which obscures the more useful distinction between request-driven and scheduled/background work.

• What changed

  • Replaced the “new capabilities” language with workload-based guidance.
  • Reframed Kibana scaling as a mix of:
    • interactive UI traffic
    • API requests
    • background work executed by Kibana Task Manager
  • Updated the follow-on sentence to describe Task Manager-managed workloads directly, using concrete examples: alerting rules, detection rules, reports, and other periodic tasks.

• Updated wording shape

  Scaling {{kib}} requires accounting for a mix of interactive UI traffic, API requests, and background work executed by [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md).
  
  This background work includes alerting rules, detection rules, reports, and other periodic tasks that Task Manager schedules, executes, and coordinates.

[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: queued.

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

[github-actions]

🔍 Preview links for changed docs

• deploy-manage/production-guidance/kibana-in-production-environments.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

No 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.

[shainaraskas]

@copilot please add to your description the issue that this fixes

[Copilot]

@copilot please add to your description the issue that this fixes

I can’t edit the PR description directly from here, but the issue reference to add is Closes elastic/docs-content-internal#1135.

[github-actions]

Docs review summary

Focus areas

• Style and clarity: One moderate issue on line 24 — "managed by ... which schedules, executes, and coordinates these tasks" describes Task Manager's role twice. See inline comment. Otherwise the rewrite is clear and direct. Vale found zero findings.
• Jargon: No issues. Task Manager is introduced with its full {{kib}} Task Manager form and linked on first use.
• Frontmatter and applies_to: No changes; existing frontmatter (applies_to, products, navigation_title) is valid.
• Content type fit: No concerns; this is a concise scalability overview section within a production-guidance page.
• Parent issue satisfaction: Satisfied — the PR removes "new capabilities" framing, reframes Kibana scaling around concrete workload types (interactive UI traffic, API requests, background work), and introduces Task Manager with specific examples (alerting rules, detection rules, reports).

Notes

• Line 26 (unchanged) uses "the task manager" (lowercase) while the PR now introduces "{{kib}} Task Manager" (capitalized) on the preceding line. Not part of this diff, but worth aligning if the section is touched again.

Generated by Docs review agent for issue #7026 · 97.5 AIC · ⌖ 17.8 AIC · ⊞ 32.9K

[wajihaparvez]

Suggested change

	Scaling {{kib}} requires accounting for a mix of interactive UI traffic, API requests, and background work. The relative impact of each can vary depending on the features and solutions you use.
	Scaling {{kib}} requires accounting for a mix of interactive UI traffic, API requests, and background work.

Do we really need this line about impact? Suggest deleting or moving it somewhere else. The next sentence continues talking about background work so this line is kind of interrupting that flow

[shainaraskas]

I want to keep it so it's still keeping the nuance of solutions/features ... will edit the next sentence so it's less abrupt

[wajihaparvez]

LGTM! One small suggestion