Add build info metric #278
Comments
|
I'm not sure how you'd go about this with Java, but I'll be interested to see how practical it is. |
brian-brazil
pushed a commit
that referenced
this issue
Jun 8, 2018
* Registering JMX Exporter build info By adding the Implementation-Version manifest entry it is possible to retrieve the lib version at runtime by checking the class Package. This allows the tracking of which JVMs are running which versions of the exporter. Closes #278 Signed-off-by: Hugo Picado <hugo.pcd@gmail.com> * Registering jmx_exporter build info for HTTP Server As now we are exporting the build info for different modules, besides the version, the name of the module was also added so we can distinguish between both. Signed-off-by: Hugo Picado <hugo.pcd@gmail.com> Closes #278
qinghui-xu
pushed a commit
to qinghui-xu/jmx_exporter
that referenced
this issue
Sep 18, 2020
* Registering JMX Exporter build info By adding the Implementation-Version manifest entry it is possible to retrieve the lib version at runtime by checking the class Package. This allows the tracking of which JVMs are running which versions of the exporter. Closes prometheus#278 Signed-off-by: Hugo Picado <hugo.pcd@gmail.com> * Registering jmx_exporter build info for HTTP Server As now we are exporting the build info for different modules, besides the version, the name of the module was also added so we can distinguish between both. Signed-off-by: Hugo Picado <hugo.pcd@gmail.com> Closes prometheus#278
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be really helpful to have something like
jmx_exporter_build_info(e.g. with the jar version), so that it'd be easier to track which JVMs are running which versions of the exporter.@brian-brazil if you don't object, we might have a go at implementing this.
The text was updated successfully, but these errors were encountered: