-
Notifications
You must be signed in to change notification settings - Fork 2
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
Duplicated timeseries in CollectorRegistry #3
Comments
@turque, It is happen because every thread try to register the metrics and collectors do not accept it. I'm working in a fix to it. |
@turque could you please check if v0.0.2 solved your issue? |
@Ziul I tested it and the duplicated error did not occur but it's not generating metrics They apscheduler dependency don't install automatically, we need install manually. |
@turque looks like you’re having some issues with the registry. In v0.0.2 we did some changes to avoid the use of a custom registry. If you are using a custom registry yet, check this test where the If yet the issues continue, please share some of your tests here, so we can help you. |
Missing dependency included in version 0.0.3. Thank you! |
Dears,
I'm having difficulties using this module with pytest.
I split my pytest in multiples files for better organization.
Using flask-prometheus-metrics i d'nt have test problem whit, but whit this flask_monitor only first test file pass whit successful and the others fail
`self = <prometheus_client.registry.CollectorRegistry object at 0x7fe30a7c8220>, collector = prometheus_client.metrics.Histogram(request_seconds)
E ValueError: Duplicated timeseries in CollectorRegistry: {'request_seconds_bucket', 'request_seconds_created', 'request_seconds_count', 'request_seconds_sum'}
env/lib/python3.8/site-packages/prometheus_client/registry.py:29: ValueError
`
if i merge all test-files the test pass whit successful.
Do you have ideia about this problem?
The text was updated successfully, but these errors were encountered: