-
Notifications
You must be signed in to change notification settings - Fork 22
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
chore: add host resources related graphs #29
Comments
We might need to run additional container for the resource metrics (cAdvisor) - @alrevuelta already has it in the waku-simulator, so it would be easy to integrate For the location, I don't think it would be that easy - we have this in network-monitor, but the way it works is that NM calls some IP-to-location service and then exposes that vie metrics. So we could have it, but we would have to figure out how/where to translate the peer IP to location (and I don't think it belongs to nwaku, so maybe an external tool querying nwaku REST for peers info and then doing the translation?) |
mem/cpu metrics, sure, but I would leave the location out of scope. Note though that at some point we might need to split nwaku-compose into two: "professional operators" and "average users". We already have prometheus, grafana, postgres + (cadvisor for this?) services, so this setup starts looking more like a professional node operator one than for a user that just wants to quickly run a nwaku node. Unsure though where nwaku-compose should sit. |
We can always provide more guidance on starting particular services, but I think as long as the default behaviour of |
Would be good to add to the default Grafana some host resources monitoring to better gauge resource usage and whether upgrade is needed:
Some less useful but WoW effect metrics could also be added such as:
The text was updated successfully, but these errors were encountered: