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

Metrics forwarder #13

Closed
tgross opened this issue Sep 15, 2016 · 2 comments
Closed

Metrics forwarder #13

tgross opened this issue Sep 15, 2016 · 2 comments

Comments

@tgross
Copy link
Contributor

tgross commented Sep 15, 2016

ContainerMonitor supports the Prometheus API but its clear, particularly given the poor story around long-term persistence (ref #12), that we want to have a blueprint for metrics forwarding using the Prometheus API. This metrics forwarder would scrape Prometheus endpoints and then forward to an end-user's existing metrics collectors (ex. graphite, ES, nagios, etc.).

Open questions for this issue:

  • what metrics collector(s) should we support?
  • what existing tooling is there for scraping Prometheus and forwarding the metrics? telegraf seems promising.
  • should this be a separate blueprint or keep it in this repo as an alternative option?

Edit see also https://github.com/misterbisson/telegraf/tree/wip

@misterbisson
Copy link
Contributor

https://github.com/influxdata/telegraf is designed specifically for this purpose. It supports a number of inputs, including prometheus and generic json, as well as a number of outputs.

I created https://github.com/misterbisson/telegraf/tree/wip to start work on this, please watch tickets in that repo to define it.

@misterbisson
Copy link
Contributor

misterbisson commented Dec 10, 2017

Closing this in favor of autopilotpattern/telegraf#1 and autopilotpattern/telegraf#2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants