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.

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

Document diag-addr and some key endpoints #2103

Closed
klizhentas opened this Issue Jul 21, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@klizhentas
Copy link
Contributor

klizhentas commented Jul 21, 2018

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:

remote_clusters{cluster="one"} 1
remote_clusters{cluster="two"} 1

trusted_clusters{cluster="one",state="connected"} 0
trusted_clusters{cluster="one",state="connecting"} 0
trusted_clusters{cluster="one",state="disconnected"} 0
trusted_clusters{cluster="one",state="discovered"} 1
trusted_clusters{cluster="one",state="discovering"} 0

@klizhentas klizhentas added this to the 3.0.0 "San Antonio" milestone Jul 21, 2018

@kontsevoy kontsevoy closed this Sep 22, 2018

kontsevoy added a commit that referenced this issue Sep 22, 2018

kontsevoy added a commit that referenced this issue Sep 22, 2018

kontsevoy added a commit that referenced this issue Sep 22, 2018

kontsevoy added a commit that referenced this issue Sep 26, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment