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
Thanks for an excellent looking implementation! coming from the Java world, I've been looking for one like this, but for some reason it isn't as visible as scales - though IMO your implementation is much clearer and clean.
I have a Flask app to which I added metrology integration, just added a few simple counters, just to test it out.
When running locally on my machine (using gunicorn and aiohttp worker), everything works just great, metrics get reported to the remote graphite (hosted-graphite), and local logger as well. But our application is deployed to production in a docker, so when I tried running this in our local testing env (using docker-compose), anything connected to metrics just doesn't seem to work anymore.
I connected to the docker and tested the connection using shell and python code, and the metrics came through, so I think it is not an issue with connectivity, but some other thing in the code.
Just for clarification, the code is run exactly the same way (same requirements.txt, same gunicorn and parameters).
No error messages are displayed in the log. Any idea as to how I might debug this?
Thank you!
The text was updated successfully, but these errors were encountered:
Thanks for an excellent looking implementation! coming from the Java world, I've been looking for one like this, but for some reason it isn't as visible as scales - though IMO your implementation is much clearer and clean.
I have a Flask app to which I added metrology integration, just added a few simple counters, just to test it out.
When running locally on my machine (using gunicorn and aiohttp worker), everything works just great, metrics get reported to the remote graphite (hosted-graphite), and local logger as well. But our application is deployed to production in a docker, so when I tried running this in our local testing env (using docker-compose), anything connected to metrics just doesn't seem to work anymore.
I connected to the docker and tested the connection using shell and python code, and the metrics came through, so I think it is not an issue with connectivity, but some other thing in the code.
Just for clarification, the code is run exactly the same way (same requirements.txt, same gunicorn and parameters).
No error messages are displayed in the log. Any idea as to how I might debug this?
Thank you!
The text was updated successfully, but these errors were encountered: