You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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:
Edit see also https://github.com/misterbisson/telegraf/tree/wip
The text was updated successfully, but these errors were encountered: