mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 09:19:04 -04:00
Use consistent examples in Task Manager documentation (#130317)
* Use consistent examples in Task Manager documentation * Remove telemetry from mission critical list Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
This commit is contained in:
parent
4cccb695af
commit
7cf6bf648b
3 changed files with 3 additions and 3 deletions
|
@ -21,7 +21,7 @@ $ curl -X GET api/task_manager/_health
|
|||
--------------------------------------------------
|
||||
// KIBANA
|
||||
|
||||
Monitoring the `_health` endpoint of each {kib} instance in the cluster is the recommended method of ensuring confidence in mission critical services such as Alerting and Actions.
|
||||
Monitoring the `_health` endpoint of each {kib} instance in the cluster is the recommended method of ensuring confidence in mission critical services such as Alerting, Actions, and Reporting.
|
||||
|
||||
[float]
|
||||
[[task-manager-configuring-health-monitoring]]
|
||||
|
|
|
@ -105,7 +105,7 @@ A recommended strategy is to follow these steps:
|
|||
3. If the throughput is insufficient, and {kib} instances exhibit low resource usage, incrementally scale vertically while <<kibana-page,monitoring>> the impact of these changes.
|
||||
4. If the throughput is insufficient, and {kib} instances are exhibiting high resource usage, incrementally scale horizontally by provisioning new {kib} instances and reassess.
|
||||
|
||||
Task Manager, like the rest of the Elastic Stack, is designed to scale horizontally. Take advantage of this ability to ensure mission critical services, such as Alerting and Reporting, always have the capacity they need.
|
||||
Task Manager, like the rest of the Elastic Stack, is designed to scale horizontally. Take advantage of this ability to ensure mission critical services, such as Alerting, Actions, and Reporting, always have the capacity they need.
|
||||
|
||||
Scaling horizontally requires a higher degree of coordination between {kib} instances. One way Task Manager coordinates with other instances is by delaying its polling schedule to avoid conflicts with other instances.
|
||||
By using <<task-manager-health-monitoring, health monitoring>> to evaluate the <<task-manager-health-evaluate-the-runtime,date of the `last_polling_delay`>> across a deployment, you can estimate the frequency at which Task Manager resets its delay mechanism.
|
||||
|
|
|
@ -6,7 +6,7 @@
|
|||
<titleabbrev>Troubleshooting</titleabbrev>
|
||||
++++
|
||||
|
||||
Task Manager is used by a wide range of services in {kib}, such as <<alerting-production-considerations, Alerting>>, Reporting, and Telemetry.
|
||||
Task Manager is used by a wide range of services in {kib}, such as <<alerting-production-considerations, Alerting>>, Actions, Reporting, and Telemetry.
|
||||
Unexpected behavior in these services might be a downstream issue originating in Task Manager.
|
||||
|
||||
This page describes how to resolve common problems you might encounter with Task Manager.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue