We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When pushing metrics, most libraries do encode the labels value before sending them, following the specs by the pushgateway (https://github.com/prometheus/pushgateway/blob/master/README.md#url)
So sending metrics{instance="localhost:80"} 1 should return metrics{instance="localhost:80"} 1 on the gateway side.
metrics{instance="localhost:80"} 1
The issue I have with gravel-gateway is that the labels value are not being decoded, and the gateway display instead:
metrics{instance="localhost%3A80"} 1
Fix will be to decode all labels value before any processing
The text was updated successfully, but these errors were encountered:
8359816
v1.7.0
3d38354
This is a bit of a bug fix release that solves: - #27 - #29 - sinkingpoint/openmetrics-parser#2 Signed-off-by: sinkingpoint <colin@quirl.co.nz>
No branches or pull requests
When pushing metrics, most libraries do encode the labels value before sending them, following the specs by the pushgateway (https://github.com/prometheus/pushgateway/blob/master/README.md#url)
So sending
metrics{instance="localhost:80"} 1
should returnmetrics{instance="localhost:80"} 1
on the gateway side.The issue I have with gravel-gateway is that the labels value are not being decoded, and the gateway display instead:
Fix will be to decode all labels value before any processing
The text was updated successfully, but these errors were encountered: