-
Notifications
You must be signed in to change notification settings - Fork 29
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
Prometheus - metric has label dimensions inconsistent with previously collected metrics in the same metric family #47
Comments
The last link leads to this page which says that this limitation was removed in newer versions of prometheus/client_golang. |
Shat is another issue you are runnign into after upgrading the prometheus package? |
Hi @nileshsimaria after upgrading the vendored code the metrics that are considered invalid now are being exposed, however there are other metrics missing from the output that work fine now (for example most gauge values from Honestly I haven't looked into it any further to date but it seems to me that debugging the issue with the more recent dependency version is the way to go. Tracking this should propably happen in it's own PR. |
btw we ran into this with collecting data from devices running different JunOS versions. After all were at the same version again (and a restart of jtimon later), everything was working again (still, not so nice to loose telemetry data in such cases). |
Hi,
I'm using the latest version from git.
When trying to collect the endpoint
/junos/services/label-switched-path/usage/
I'm presented with the following error messages when accessing the Prometheus metrics page:There's various pieces of information here and here. The last link says that this limitation was removed in a later build of the Prometheus client library.
The text was updated successfully, but these errors were encountered: