-
Notifications
You must be signed in to change notification settings - Fork 171
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
Add default healthcheck port in the documentation #80
Conversation
Signed-off-by: Louis-Etienne Dorval <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@black-adder could you verify for accuracy?
content/docs/deployment.md
Outdated
@@ -88,6 +88,7 @@ Port | Protocol | Function | |||
14267 | TChannel | used by **jaeger-agent** to send spans in jaeger.thrift format | |||
14268 | HTTP | can accept spans directly from clients in jaeger.thrift format | |||
9411 | HTTP | can accept Zipkin spans in JSON or Thrift (disabled by default) | |||
14269 | HTTP | Health check at **/** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't healthcheck at /health
endpoint?
is there an issue / other PR this one can be linked to, for references / background? |
I was about to create an issue, but I saw this: #64 Here's various places I found the information about healthcheck:
|
As for the
|
@jpkrohling is this some sort of convention that we're serving health check at |
Not really. The key part, though, is that it's on a dedicated port so that an admin can block this port from being exposed over the public internet. The handler will respond to any request on that port. |
By the way: I think we'll (or should) end up consolidating the ports as part of jaegertracing/jaeger#773, so, we might end up with just two ports (private network, public internet). |
Thanks, @ledor473 |
No description provided.