Skip to content

Add documentation for activator_autoscaler_reachable metric #6548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
prashanthjos wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Add documentation for activator_autoscaler_reachable metric #6548

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0aed46f
Add documentation for activator_autoscaler_reachable metric
prashanthjos Dec 29, 2025
316a43d
Correcting the metric name inline with knative standards
prashanthjos Dec 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/versioned/serving/observability/metrics/serving-metrics.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,6 +92,20 @@ Name | Type | Description
`kn.configuration.name` | string | Knative Configuration name associated with this Revision
`kn.revision.name` | string | The name of the Revision

### `kn.activator.autoscaler.reachable`

**Instrument Type:** Int64Gauge

**Unit ([UCUM](https://ucum.org)):** {reachable}

**Description:** Whether the autoscaler is reachable from the activator (1 = reachable, 0 = not reachable)

This metric helps operators identify connectivity issues between the activator and autoscaler components. The metric is recorded:

- When stats are successfully sent to the autoscaler (value = 1)
- When stats fail to send to the autoscaler (value = 0)
- Periodically every 5 seconds based on connection status check

### HTTP metrics

Since the activator receives and forwards requests to the user workload it has both HTTP server and client metrics.
Expand Down