4f357a91ac
* re-arrange telemetry docs and add overview with navigation * update job and task status section * fix navigation * Update website/source/docs/telemetry/overview.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * Update website/source/docs/telemetry/overview.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * Update website/source/docs/telemetry/overview.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * Update website/source/docs/telemetry/metrics.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * Update website/source/docs/telemetry/metrics.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * fix formatting for nomad.plan.evaluate metric * clarifications on collection interval and namespace labell * fix typo * Update website/source/docs/telemetry/overview.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * Update website/source/docs/telemetry/overview.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com> * Update website/source/docs/telemetry/overview.html.md Co-Authored-By: Chris Baker <cgbaker@hashicorp.com>
764 B
764 B
layout | page_title | sidebar_current | description |
---|---|---|---|
docs | Telemetry | docs-telemetry | Telemetry docs home page |
Telemetry
The Nomad client and server agents collect a wide range of runtime metrics related to the performance of the system. Operators can use this data to gain real-time visibility into their cluster and improve performance. Additionally, Nomad operators can set up monitoring and alerting based on these metrics in order to respond to any changes in the cluster state.
Please refer to the documentation listed below or in the sidebar to learn more about how you can leverage the telemetry Nomad exposes.