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

Evaluation of using consul+prometheus to find addresses of node_exporters #8

Open
rosogon opened this issue Sep 24, 2020 · 1 comment
Assignees
Labels
runtime SODALITE Runtime Layer

Comments

@rosogon
Copy link

rosogon commented Sep 24, 2020

Basically it would work the same way it is working now, but instead of asking Openstack API for a list of instances Prometheus would ask Consul for a list of IPs: https://medium.com/trendyol-tech/consul-prometheus-monitoring-service-discovery-7190bae50516

@MarioMartReq , please evaluate needed efforts for the implementation and share here your findings.

@rosogon rosogon added the runtime SODALITE Runtime Layer label Sep 24, 2020
@MarioMartReq
Copy link
Contributor

I wrote my findings of this monitoring change in the following document:
https://docs.google.com/document/d/1PUzj2IHrCDV0s9lWED4I301GAQ7wrn7UmpKGP3ETyBU/edit#

@rosogon rosogon assigned rosogon and unassigned MarioMartReq Oct 2, 2020
@rosogon rosogon assigned fabeirojorge-sw and unassigned rosogon Oct 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
runtime SODALITE Runtime Layer
Projects
None yet
Development

No branches or pull requests

3 participants