clarify which parts of TM are experimental (elastic#101757)

gmmorris · Jun 9, 2021 · 54c0713 · 54c0713
1 parent 0dcd603
commit 54c0713
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 0 deletions.
diff --git a/docs/user/production-considerations/task-manager-health-monitoring.asciidoc b/docs/user/production-considerations/task-manager-health-monitoring.asciidoc
@@ -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.

diff --git a/docs/user/production-considerations/task-manager-troubleshooting.asciidoc b/docs/user/production-considerations/task-manager-troubleshooting.asciidoc
@@ -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.