You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to have some sort of metrics for monitoring the OpenNebula Core. Here are some metrics I would find useful:
counters for each success and failed API calls
authentication failures
number of read/writes to the DB
latency to the DB (time spent reading or writing)
some stats on the internals (time spent waiting for a lock, number of failed lock request, etc.).
And have a method to easily export the metrics to ex. Ganglia (perhaps making metrics struct available to other processes through shared memory). The metrics should be very simple and lightweight, I'm thinking of plain counters that are initialized to 0 when OpenNebula starts.
The same metrics could be used for measuring the impacts of optimization / changes to the core or to the DB.
The text was updated successfully, but these errors were encountered:
Author Name: Simon Boulet (Simon Boulet)
Original Redmine Issue: 2026, https://dev.opennebula.org/issues/2026
Original Date: 2013-05-13
It would be great to have some sort of metrics for monitoring the OpenNebula Core. Here are some metrics I would find useful:
And have a method to easily export the metrics to ex. Ganglia (perhaps making metrics struct available to other processes through shared memory). The metrics should be very simple and lightweight, I'm thinking of plain counters that are initialized to 0 when OpenNebula starts.
The same metrics could be used for measuring the impacts of optimization / changes to the core or to the DB.
The text was updated successfully, but these errors were encountered: