*This chart has been deprecated as of version 0.2.1 and will not be updated. Please use the telegraf-s and telegraf-ds charts instead.*
[Telegraf](https://github.com/influxdata/telegraf) is a plugin-driven server agent written by the folks over at [InfluxData](https://influxdata.com) for collecting & reporting metrics.
## TL;DR
...
...
@@ -20,10 +18,10 @@ This chart bootstraps a `telegraf` deployment on a [Kubernetes](http://kubernete
## Installing the Chart
To install the chart with the release name `my-release`:
To install the chart with the release name `telegraf`:
The command deploys Telegraf on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation.
...
...
@@ -32,145 +30,37 @@ The command deploys Telegraf on the Kubernetes cluster in the default configurat
## Uninstalling the Chart
To uninstall/delete the `my-release` deployment:
To uninstall/delete the `telegraf` deployment:
```console
$ helm delete my-release
$ helm delete telegraf
```
The command removes all the Kubernetes components associated with the chart and deletes the release.
## Configuration
The default configuration parameters are listed in `values.yaml`. To change the defaults, specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example,
The default configuration parameters are listed in `values.yaml`.
```console
$ helm install--name my-release \
--set single.enabled=false\
stable/telegraf
$ helm install--name telegraf stable/telegraf
```
The above command prevents the single telegraf instance from deploying.
Alternatively, a YAML file that specifies the values for the above parameters can be provided while installing the chart. For example,
The following telegraf output plugins are supported for both the daemonset and the single instance. To enable them uncomment them in `.Values.{{ "daemonset" | "single" }}.outputs`:
The single telegraf also supports all service plugins. To enable them uncomment the named plugin in `.Values.single.inputs` section. The associated service exposes the ports if it is enabled:
To enable additional input plugins uncomment them in the `.Values.single.inputs` section. The input plugins supported by the single telegraf instance are as follows: