-
Notifications
You must be signed in to change notification settings - Fork 163
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
[jaeger-v2] Document changes to admin port / services #750
Comments
24 tasks
2 tasks
I did some updates to the docs per : #751 The following seem to still be in the v1 docs and I believe should be somewhere in v2 docs, let me know what you think:
|
yes, those ports would still be relevant (sometimes the ports might be different) |
yurishkuro
added a commit
that referenced
this issue
Nov 2, 2024
## Which problem is this PR solving? Part of #750 ## Description of the changes Adjusting command line and other components from v1 to v2. ## Checklist - [X] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [X] I have signed all commits --------- Signed-off-by: Jonah Kowall <[email protected]> Signed-off-by: Yuri Shkuro <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
Is anything else pending on this issue or can we close @yurishkuro ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
address: 0.0.0.0:8888
(address: 0.0.0.0:8889
for ingester)expvar
extension:port: 27777
healthcheckv2
extension:endpoint: "0.0.0.0:13133"
The text was updated successfully, but these errors were encountered: