Ability to interact with metrics

[akashs2795]

Purser currently calculates costs using allocation of resources. If this product is to be a standard for Kubernetes costing, there is a need to have Utilisation based costing as a functionality in purser.

Basic requirement for this is that the utilisation metrics from various components in the cluser be stored in a metrics store as time-series metrics.

This issue tracks this specific task of introducing a metric-store agnostic approach of saving utilisation metrics in purser.

[kreddyj]

Hi @akashs2795 , thanks for the new feature suggestion. If you have a plan or a possible road map for this, I suggest you to create a documentation (docs/planning/utilization.md) with all the details relating to it.

[akashs2795]

I ll be doing so and will raise a PR for the same so that we can track and review the planning doc appropriately