kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Updating docs/concepts/cluster-administration/system-metrics 

Copy editing _Metric lifecycle_ section for clarity.

fixes: https://github.com/kubernetes/website/issues/20652

Signed-off-by: Nate W <4453979+nate-double-u@users.noreply.github.com>
This commit is contained in:
Nate W 2020-11-28 11:07:00 -08:00
parent 9e010e5e19
commit e38868f479
1 changed files with 23 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
content/en/docs/concepts/cluster-administration/system-metrics.md
View File

@ -50,39 +50,41 @@ rules:
## Metric lifecycle ## Metric lifecycle
Alpha metric → Stable metric → Deprecated metric → Hidden metric → Deletion Alpha metric → Stable metric → Deprecated metric → Hidden metric → Deleted metric
Alpha metrics have no stability guarantees; as such they can be modified or deleted at any time. Alpha metrics have no stability guarantees. These metrics can be modified or deleted at any time.
Stable metrics can be guaranteed to not change; Specifically, stability means: Stable metrics are guaranteed to not change. This means:
* A stable metric without a deprecated signature will not be deleted or renamed
* A stable metric's type will not be modified
* the metric itself will not be deleted (or renamed) Deprecated metrics are slated for deletion, but are still available for use.
* the type of metric will not be modified These metrics include an annotation about the version in which they became deprecated.
Deprecated metric signal that the metric will eventually be deleted; to find which version, you need to check annotation, which includes from which kubernetes version that metric will be considered deprecated. For example:
Before deprecation: * Before deprecation
``` ```
# HELP some_counter this counts things # HELP some_counter this counts things
# TYPE some_counter counter # TYPE some_counter counter
some_counter 0 some_counter 0
``` ```
After deprecation: * After deprecation
``` ```
# HELP some_counter (Deprecated since 1.15.0) this counts things # HELP some_counter (Deprecated since 1.15.0) this counts things
# TYPE some_counter counter # TYPE some_counter counter
some_counter 0 some_counter 0
``` ```
Once a metric is hidden then by default the metrics is not published for scraping. To use a hidden metric, you need to override the configuration for the relevant cluster component. Hidden metrics are no longer published for scraping, but are still available for use. To use a hidden metric, please refer to the [Show hidden metrics](#show-hidden-metrics) section.
Once a metric is deleted, the metric is not published. You cannot change this using an override. Deleted metrics are no longer published and cannot be used.
## Show Hidden Metrics ## Show hidden metrics
As described above, admins can enable hidden metrics through a command-line flag on a specific binary. This intends to be used as an escape hatch for admins if they missed the migration of the metrics deprecated in the last release. As described above, admins can enable hidden metrics through a command-line flag on a specific binary. This intends to be used as an escape hatch for admins if they missed the migration of the metrics deprecated in the last release.