maxmustermann/kibana
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

clarify which parts of TM are experimental (#101757)

Browse source
This commit is contained in:
Gidi Meir Morris 2021-06-09 17:26:03 +01:00 committed by GitHub
parent ac2e247c5b
commit 03541e6196
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/user/production-considerations/task-manager-health-monitoring.asciidoc
View file

@ -6,6 +6,8 @@
<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 health monitoring API provides a reliable endpoint that can be monitored.

2
docs/user/production-considerations/task-manager-troubleshooting.asciidoc
View file

@ -60,6 +60,8 @@ For details on scaling Task Manager, see <<task-manager-scaling-guidance>>.
[[task-manager-diagnosing-root-cause]]
==== 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.
By analyzing the different sections of the output, you can evaluate different theories that explain the drift in a deployment.