Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proposal: pushing metrics directly to Prometheus #4140

Closed
rollcat opened this issue May 4, 2018 · 3 comments
Closed

Proposal: pushing metrics directly to Prometheus #4140

rollcat opened this issue May 4, 2018 · 3 comments

Comments

@rollcat
Copy link

rollcat commented May 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.

@krasi-georgiev
Copy link
Contributor

https://groups.google.com/forum/#!forum/prometheus-developers
Proposals are best discussed in the google group as more people are subscribed there and will be a better place for such discussion.

it might be worth doing some search as I suspect this topic has already been discussed.
Don't forget to describe your use case and why it can't be solved with the pull model or via the push gateway.

@brian-brazil
Copy link
Contributor

This has been discussed extensively, and this is an explicit non-goal of the project.

@lock
Copy link

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.

@lock lock bot locked and limited conversation to collaborators Mar 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants