Enhancement (What you would like to be added):
There is a need to get insights into data that it stores in the DB (bbolt-DB). This provides valuable information on which resource type has the most keys and size.
@istvanballok recently executed the following command to get that data out of etcd:
It would be beneficial for the operators/devs to get easy access to this data either on demand or as custom metrics that are exposed to prometheus.
NOTE: The above is just one set of information. We should identify additional information/custom-metrics that is not available out-of-the-box from etcd over time.
Motivation (Why is this needed?):
Use cases:
Operators can inspect the etcd data to know why etcd DB is close to the 8GB mark and perhaps take corrective actions.
Developers can inspect this data over a period of time and fine tune the resource that get stored in etcd.
Approach/Hint to the implement solution (optional):
Apart from the above mentioned metrics, additional requirements post discussion with @istvanballok
Rate of object writes by resource type
Top 10 property paths with frequent changes. E.g if a resource is getting too many updates then expose a metric to also capture which property changes most of the times.
Enhancement (What you would like to be added): There is a need to get insights into data that it stores in the DB (bbolt-DB). This provides valuable information on which resource type has the most keys and size. @istvanballok recently executed the following command to get that data out of etcd:
Example output:
It would be beneficial for the operators/devs to get easy access to this data either on demand or as custom metrics that are exposed to prometheus.
Motivation (Why is this needed?): Use cases:
Approach/Hint to the implement solution (optional):