Name Last Update
..
README.md Loading commit data...
buildout.hash.cfg Loading commit data...
gowork.cfg Loading commit data...
grafana-config-file.cfg.in Loading commit data...
influxdb-config-file.cfg.in Loading commit data...
instance-input-schema.json Loading commit data...
instance-output-schema.json Loading commit data...
instance.cfg.in Loading commit data...
software.cfg Loading commit data...
software.cfg.json Loading commit data...
telegraf-config-file.cfg.in Loading commit data...

grafana / telegraf / influxdb

Custom telegraf plugins

See https://github.com/influxdata/telegraf to learn about plugins.

Useful plugins in this context are probably exec or httpjson.

Telegraf will save in the telegraf database from the embedded influxdb server.

Grafana

You'll have to add yourself the influxdb data source in grafana, using the parameters published by the slapos instance.

http://docs.grafana.org/features/datasources/influxdb/

When adding datasource, use proxy option, otherwise Grafana makes your browser query influxdb directly, which also uses a self signed certificate. One workaround is to configure your browser to also accept influxdb certificate before using grafana, but using proxy seems easier.

Influxdb

Influxdb backups are not done automatically by this software release.

One important thing to notice is that the backup protocol is enabled on ipv4 provided by slapos, so make sure this ip is not reachable from untrusted sources.

TODO

  • influxdb and telegraf runs with very low priority, this could become an option
  • make one partition for each service and use switch software type
  • make it easier to add custom configuration (how ?)