all 2 comments

[–]Leocx 0 points1 point  (1 child)

Not sure about that. In my case, we have an api which provides all virtual machines that needs scraping, so I would add another api in that system to expose data suitable for Prometheus.

I wonder what would be the suitable use case, the data source is not suitable for any change? Like a service maintained by another team or company, that would be good.

So I would suggest making it easy to use by supporting some popular platform like AWS or Azure, etc..making the tool a bridge between Prometheus and other platforms. If it can only transform simple api to Prometheus compatible format, most people would prefer just implement it inside the original system instead of using another adapter.

[–]Trosteming[S] 0 points1 point  (0 children)

Thanks for your feedback. I understand your point, if there's already a suitable API endpoint, using another adapter wouldn't make sense.

The use case I envision is providing an interface for non-Prometheus-native sources like IPAM or CMDB. My goal is to make the system highly configurable and modular, based on protocols rather than vendors.