clarify which parts of TM are experimental (#101757)
This commit is contained in:
parent
ac2e247c5b
commit
03541e6196
|
@ -6,6 +6,8 @@
|
||||||
<titleabbrev>Health monitoring</titleabbrev>
|
<titleabbrev>Health monitoring</titleabbrev>
|
||||||
++++
|
++++
|
||||||
|
|
||||||
|
experimental[]
|
||||||
|
|
||||||
The Task Manager has an internal monitoring mechanism to keep track of a variety of metrics, which can be consumed with either the health monitoring API or the {kib} server log.
|
The Task Manager has an internal monitoring mechanism to keep track of a variety of metrics, which can be consumed with either the health monitoring API or the {kib} server log.
|
||||||
|
|
||||||
The health monitoring API provides a reliable endpoint that can be monitored.
|
The health monitoring API provides a reliable endpoint that can be monitored.
|
||||||
|
|
|
@ -60,6 +60,8 @@ For details on scaling Task Manager, see <<task-manager-scaling-guidance>>.
|
||||||
[[task-manager-diagnosing-root-cause]]
|
[[task-manager-diagnosing-root-cause]]
|
||||||
==== Diagnose a root cause for drift
|
==== Diagnose a root cause for drift
|
||||||
|
|
||||||
|
experimental[]
|
||||||
|
|
||||||
The following guide helps you identify a root cause for _drift_ by making sense of the output from the <<task-manager-health-monitoring>> endpoint.
|
The following guide helps you identify a root cause for _drift_ by making sense of the output from the <<task-manager-health-monitoring>> endpoint.
|
||||||
|
|
||||||
By analyzing the different sections of the output, you can evaluate different theories that explain the drift in a deployment.
|
By analyzing the different sections of the output, you can evaluate different theories that explain the drift in a deployment.
|
||||||
|
|
Loading…
Reference in a new issue