Integrate OpenCost/KubeCost to drill down cost to API / component level

[ankitnayan]

We can integrate OpenCost with SigNoz so that users can narrow down costs from cluster to API or components. Eg, an API starts producing too many Kafka messages increasing the resource needs of Kafka altogether.

With more and more software adopting OTEL, we can drill down resource usage of software to maybe a set of APIs or product features. Eg, wouldn't it be awesome if the Ops team can tag a service owner saying, your XYZ APIs are making Postgres consume 20% more resources after the last release?

Or, feature F is less critical to business but creates a lot of load on the queue. Can we associate the breakdown of costs of common softwares to individual service owners, features, etc.

Would love to hear more thoughts on this.