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
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"}
The text was updated successfully, but these errors were encountered:
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.
@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?
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"}
The text was updated successfully, but these errors were encountered: