Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upProposal: pushing metrics directly to Prometheus #4140
Comments
This comment has been minimized.
This comment has been minimized.
|
https://groups.google.com/forum/#!forum/prometheus-developers it might be worth doing some search as I suspect this topic has already been discussed. |
krasi-georgiev
closed this
May 4, 2018
This comment has been minimized.
This comment has been minimized.
|
This has been discussed extensively, and this is an explicit non-goal of the project. |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 22, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
rollcat commentedMay 4, 2018
I think push vs pull has been mentioned a long time ago, on numerous occasions, and in numerous sources already, but after briefly reviewing open (and closed) issues I haven't found anything of a decisive "yes" / "no" / "maybe" / "send a patch".
From what I gathered, pushgateway, due to its design, is only ever recommended for certain, specialized use cases.
The high-level proposal is to expose an endpoint, where clients could push metrics directly, ideally via HTTP POST. Basically integrate (parts of) pushgateway into "core" Prometheus, and make push-based metric collection a first-class citizen.
Clients that only expose metrics via the scrape/GET endpoint, could be bridged by a local scraper that later pushes the metrics via POST.