Skip to content
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

Investigate use of prometheus #24

Open
dylanmcreynolds opened this issue May 19, 2020 · 1 comment
Open

Investigate use of prometheus #24

dylanmcreynolds opened this issue May 19, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@dylanmcreynolds
Copy link
Collaborator

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.

@dylanmcreynolds
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants