Skip to content
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

Report OTel Collector version in the collector health page and/or diagnostic pages #2382

Closed
CeeBeeCee opened this issue Jan 20, 2021 · 6 comments · Fixed by #2388
Closed

Comments

@CeeBeeCee
Copy link

Is your feature request related to a problem? Please describe.
It is hard to know what version of the collector is running without logging into the server to find out

Describe the solution you'd like
Add a version key-value pair to the health check and/or the tracez/pprof pages. Something like :
{"version": "0.18.0". status":"Server available","upSince":"2021-01-20T16:26:04.209548064Z","uptime":"9m34.530382956s"}

@bogdandrutu
Copy link
Member

bogdandrutu commented Jan 20, 2021

We have all these informations in "/debug/servicez" page if you enable the zpages extension. Not yet available status.

@bogdandrutu
Copy link
Member

Not sure about the "status" thing, how do we determine if status OK or NOT?

@CeeBeeCee
Copy link
Author

When I access the servicez page, it reports "latest" as the version and not 0.18 which is what I'm running (using docker). Anyway to get it to return the actual version number? Also, the status, upSince and uptime is the current response coming from the health_check extension. I was just proposing that we add version to it.

Version | latest
GitHash |
BuildType | release
Goversion | go1.14.13
OS | linux
Architecture | amd64

@bogdandrutu
Copy link
Member

Ok.. so you need only to fix the version then

@CeeBeeCee
Copy link
Author

Correct

@CeeBeeCee
Copy link
Author

@bogdandrutu : I see that you have closed this issue. Is there a way for me to test the changes? Perhaps from the otel/opentelemetry-collector-dev image on dockerhub?

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

Successfully merging a pull request may close this issue.

3 participants