From f05fb9676ea199b81bc571268b71b4224036af67 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 19 Jun 2026 13:29:54 +0000 Subject: [PATCH 1/5] Initial plan From 31ea34e7497926852fa8e9957c0fe50dbcea58c8 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 19 Jun 2026 13:32:02 +0000 Subject: [PATCH 2/5] docs: clarify kibana scalability guidance --- .../production-guidance/kibana-in-production-environments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/production-guidance/kibana-in-production-environments.md b/deploy-manage/production-guidance/kibana-in-production-environments.md index 3d38e28ff5..7737c89c07 100644 --- a/deploy-manage/production-guidance/kibana-in-production-environments.md +++ b/deploy-manage/production-guidance/kibana-in-production-environments.md @@ -19,9 +19,9 @@ How you deploy {{kib}} largely depends on your use case. If you are the only use ## Scalability -With the introduction of new capabilities such as [{{kib}} Alerting](/explore-analyze/alerting.md) and the [Detection Rules](/solutions/security/detect-and-alert.md) engine, critical components for [Observability](/solutions/observability.md) and [Security](/solutions/security.md) solutions, the scalability factors have evolved significantly. +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). -Now, Kibana’s resource requirements extend beyond user activity. The system must also handle workloads generated by automated processes, such as scheduled alerts, background detection rules, and other periodic tasks. These operations are managed by [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md), which is responsible for scheduling, executing, and coordinating all background tasks. +This background work includes alerting rules, detection rules, reports, and other periodic tasks that Task Manager schedules, executes, and coordinates. Additionally, the task manager enables distributed coordination across multiple {{kib}} instances, allowing {{kib}} to function as a logical cluster in certain aspects. From b4ee219c0c832af1605d8ceaef65581d5e4941b3 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Fri, 19 Jun 2026 13:35:58 +0000 Subject: [PATCH 3/5] docs: restore task manager context in kibana scaling copy --- .../production-guidance/kibana-in-production-environments.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/production-guidance/kibana-in-production-environments.md b/deploy-manage/production-guidance/kibana-in-production-environments.md index 7737c89c07..0287f1372d 100644 --- a/deploy-manage/production-guidance/kibana-in-production-environments.md +++ b/deploy-manage/production-guidance/kibana-in-production-environments.md @@ -19,9 +19,9 @@ How you deploy {{kib}} largely depends on your use case. If you are the only use ## Scalability -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). +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. -This background work includes alerting rules, detection rules, reports, and other periodic tasks that Task Manager schedules, executes, and coordinates. +This background work includes alerting rules, detection rules, reports, and other periodic tasks managed by [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md), which schedules, executes, and coordinates these tasks. Additionally, the task manager enables distributed coordination across multiple {{kib}} instances, allowing {{kib}} to function as a logical cluster in certain aspects. From eb3736e7d491426c75ee8e44bb53159436111383 Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Fri, 19 Jun 2026 12:40:01 -0400 Subject: [PATCH 4/5] Update deploy-manage/production-guidance/kibana-in-production-environments.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> --- .../production-guidance/kibana-in-production-environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/production-guidance/kibana-in-production-environments.md b/deploy-manage/production-guidance/kibana-in-production-environments.md index 0287f1372d..0a1d19952e 100644 --- a/deploy-manage/production-guidance/kibana-in-production-environments.md +++ b/deploy-manage/production-guidance/kibana-in-production-environments.md @@ -21,7 +21,7 @@ How you deploy {{kib}} largely depends on your use case. If you are the only use 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. -This background work includes alerting rules, detection rules, reports, and other periodic tasks managed by [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md), which schedules, executes, and coordinates these tasks. +This background work includes alerting rules, detection rules, reports, and other periodic tasks that [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md) schedules, executes, and coordinates. Additionally, the task manager enables distributed coordination across multiple {{kib}} instances, allowing {{kib}} to function as a logical cluster in certain aspects. From 91f6668df34060d749546ec88b3548d67256a2df Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Thu, 25 Jun 2026 15:59:46 -0400 Subject: [PATCH 5/5] Update deploy-manage/production-guidance/kibana-in-production-environments.md --- .../production-guidance/kibana-in-production-environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/production-guidance/kibana-in-production-environments.md b/deploy-manage/production-guidance/kibana-in-production-environments.md index 0a1d19952e..dcba906605 100644 --- a/deploy-manage/production-guidance/kibana-in-production-environments.md +++ b/deploy-manage/production-guidance/kibana-in-production-environments.md @@ -21,7 +21,7 @@ How you deploy {{kib}} largely depends on your use case. If you are the only use 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. -This background work includes alerting rules, detection rules, reports, and other periodic tasks that [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md) schedules, executes, and coordinates. +Background work includes alerting rules, detection rules, reports, and other periodic tasks that [{{kib}} Task Manager](./kibana-task-manager-scaling-considerations.md) schedules, executes, and coordinates. Additionally, the task manager enables distributed coordination across multiple {{kib}} instances, allowing {{kib}} to function as a logical cluster in certain aspects.