Open dylanmcreynolds opened 4 years ago
Update to this issue, I think I don't want prometheus in the splash-deploy. While it's still probably easiest to run prometheus from docker, I don't want to muddy splash-deploy with it. For this initial test, fire up prometheus however you want, but don't put it in splash-deploy docker-compse*.yml
It's important to have some sort of instrumentation framework available for services. One popular framework is prometheus. Let's try it out.
See this: https://rollout.io/blog/monitoring-your-synchronous-python-web-applications-using-prometheus/
This issue describes a trial of prometheus. We will plug the code into Flask as outlined in that blog post. Then, in splash-deploy, we will fire up a prometheus service in the docker-compose such that it talks the /metrics endpoint and collects information. Success this task will be a system that captures response times and information and can be viewed with the prometheus web app. We hope to gain knowledge about how useful prometheus might be in deployments.