Skip to content
This repository was archived by the owner on Jan 5, 2022. It is now read-only.

Working OOTB Dashboards & telegraf plugin updates#88

Open
tomklapka wants to merge 6 commits into
influxdata:masterfrom
tomklapka:plugin_updates
Open

Working OOTB Dashboards & telegraf plugin updates#88
tomklapka wants to merge 6 commits into
influxdata:masterfrom
tomklapka:plugin_updates

Conversation

@tomklapka

@tomklapka tomklapka commented Feb 19, 2019

Copy link
Copy Markdown
  • tick stack components updated to their latest version,
  • telegraf-ds now sends system metrics (cpu, mem, net, disk, diskio, swap...),
  • telegraf-s plugins conf. updated to match actual telegraf plugin configurations,
  • Influxdb, system, kubernetes overview and docker dashboards are fully functional by default.
  • contains fix for Init Chronograf: no dashboard on the list #69

@jackzampolin

Copy link
Copy Markdown
Contributor

This looks really good! I don't have time to review in depth tho!

@russorat

Copy link
Copy Markdown
Contributor

Let's remove the eks updates from this PR and keep it focused on updating the telegraf configs.

also, let's enable prometheus plugin scrape targets by default. https://github.com/influxdata/telegraf/tree/master/plugins/inputs/prometheus#kubernetes-scraping

@tomklapka

Copy link
Copy Markdown
Author

@russorat Regarding Prometheus pod scraping - it's a matter of plugin configuration and relevant annotations on pods. Beside that there should be something in the pod which can collect and serve prometheus metrics if I'am not mistaken. The simplest sample solution could be to enable prometheus client output telegraf plugin which will then serve metrics at least on one pod in the cluster and then collect them back in the same pod - not ideal real world usage.

boxrick added a commit to boxrick/tick-charts that referenced this pull request May 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

Successfully merging this pull request may close these issues.

3 participants