You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is worth documenting our diag-addr endpoint as it's used in Kubernetes deployments and prometheus endpoint is used in production to check health of components:
New readyz endpoint is added to existing
/metrics and /healthz endpoints activated by
diag addr-flag:
teleport start --diag-addr=127.0.0.1:1234
Readyz endpoint will report 503 if node or
proxy failed to connect to the cluster and 200 OK
otherwise.
Additional prometheus gagues report connection
count for trusted and remote clusters:
Description
It is worth documenting our diag-addr endpoint as it's used in Kubernetes deployments and prometheus endpoint is used in production to check health of components:
New readyz endpoint is added to existing
/metrics and /healthz endpoints activated by
diag addr-flag:
teleport start --diag-addr=127.0.0.1:1234
Readyz endpoint will report 503 if node or
proxy failed to connect to the cluster and 200 OK
otherwise.
Additional prometheus gagues report connection
count for trusted and remote clusters:
The text was updated successfully, but these errors were encountered: