I'm brand new to Prometheus and my head is spinning after spending time reading the docs so I hope someone can offer a little advice.
We have a mature client-server system involving dozens of (mostly) C++ modules; workstations and servers all run on Windows and modules mostly communcate via DCOM. We want to start recording metrics about real-time state which is new to me. I understand Prometheus is pull-based and appears to pull only via HTTP(?) so I am struggling how to reconcile this with our system. Engineering HTTP endpoints into our modules is realistically unlikely and some of our modules use obscure tech which doesn't even allow this. Our metrics would generally come from: - in-memory state in a few key modules running on the app-server - state of the machines themselves e.g. CPU/RAM use - database data, e.g. many metrics would map nicely to SQL queries "how many widgets are active?" My initial thought would be to create new module(s) which exist solely to expose metrics to Prometheus, essentially a bridge - does that seem reasonable? I'm open to the answer that perhaps a pull-based system is simply not optimal and we should look at a different tool? Sorry for the long post, I hope I've been able to give enough information where I'm coming from. Thanks. -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/24247126-1737-4b16-9fc8-3e25a67741f7n%40googlegroups.com.
