Change:
## Metric lifecycle <del> Alpha metric →  Stable metric →  Deprecated metric →  Hidden metric → Deletion </del> <ins> Alpha metric →  Stable metric →  Deprecated metric →  Hidden metric → Deleted metric </ins> <del> Alpha metrics have no stability guarantees; as such they can be modified or deleted at any time. </del> <ins> Alpha metrics have no stability guarantees. These metrics can be modified or deleted at any time. </ins> <del> Stable metrics can be guaranteed to not change; Specifically, stability means: </del> <ins> 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 </ins> <del> * the metric itself will not be deleted (or renamed) * the type of metric will not be modified </del> <ins> Deprecated metrics are slated for deletion, but are still available for use. These metrics include an annotation about the version in which they became deprecated. </ins> <del> 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. </del> <ins> For example: </ins> <del> Before deprecation: </del> <ins> * Before deprecation </ins> <del> ``` # HELP some_counter this counts things # TYPE some_counter counter some_counter 0 ``` </del> <ins> ``` # HELP some_counter this counts things # TYPE some_counter counter some_counter 0 ``` </ins> <del> After deprecation: </del> <ins> * After deprecation </ins> <del> ``` # HELP some_counter (Deprecated since 1.15.0) this counts things # TYPE some_counter counter some_counter 0 ``` </del> <ins> ``` # HELP some_counter (Deprecated since 1.15.0) this counts things # TYPE some_counter counter some_counter 0 ``` </ins> <del> 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. </del> <ins> 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. </ins> <del> Once a metric is deleted, the metric is not published. You cannot change this using an override. </del> <ins> Deleted metrics are no longer published and cannot be used. </ins> <del> ## Show Hidden Metrics </del> <ins> ## Show hidden metrics </ins> 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.

Discussion:
This is a Bug Report Problem: The text unclearly says: "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." (Note the problems, such as "Deprecated metric signal ...," "to check annotation," unclear references to versions (when metric will be gone, when declared deprecated, other?), etc.) Proposed Solution: Have a fluent English speaker (who knows Kubernetes) edit that. Page to Update:
/language en /sig instrumentation
Issues go stale after 90d of inactivity. Mark the issue as fresh with . Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle stale
/triage accepted
Stale issues rot after 30d of inactivity. Mark the issue as fresh with . Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with . Send feedback to sig-testing, kubernetes/test-infra and/or . /lifecycle rotten
I'd like to try a pass at this. /assign
Not sure if I'm able to do this, but let's try: /remove-lifecycle rotten