-
Notifications
You must be signed in to change notification settings - Fork 3.6k
add prometheus exporter plugin that exposes key nodeos metrics #9902
Comments
I have added more examples since this enhancement was originally created. |
How does this relate to #9996 |
Well my ideal solution is that there is a prometheus exporter for all the metrics and no log scraping is needed. However, if developing a prometheus exporter plugin is not on on the radar, then generate a log message instead and I'll scrape the log (as I do today). So really there are 2 things: 1) generate useful metrics for debugging and 2) log them and/or expose via prometheus exporter plugin. |
Example, my log scraper currently generates something like this:
|
+1 We also pull data out from the nodes via get info and scraping the configs/supported_apis/etc.:
|
This would be incredibly helpful to Automation, and no-doubt to the community at-large since Prometheus is a common mechanism for vacuuming up metrics. |
For monitoring, nodeos should have a prometheus exporter plugin (that runs on a separate port), which exposes key metrics that would be useful for monitoring.
Metrics such as
Where possible, attribute actions to a specific producer (eg when counting dropped blocks, specify which producer missed those blocks)
The text was updated successfully, but these errors were encountered: