When using tick-charts/telegraf-s I cannot use the inputs.http plugin

telegraf

#1

I am trying to deploy the tick stack using the tick-charts repo. I want to use the telegraf http input plugin however when I deploy the chart with the following addition to values.yaml:

  http:
    ## Adapted from https://github.com/influxdata/telegraf/tree/master/plugins/inputs/http
    ## One of more URLs from whic to read formatted metrics
    urls:
      - "http://metrics:80/workflow-phase-counter"
    ## HTTP method
    method: "GET"
    ## Optional HTTP heads
    #headers: {}
    ## Optional HTTP basic auth credentials
    #username: ""
    #password: ""
    ## Optional SSL config
    #ssl_ca: ""
    #ssl_cert: ""
    #ssl_key: ""
    ## Use SSL but skip chain & host verification
    #insecure_skip_verify: false
    ## Amount of time allowed to complete the HTTP request
    timeout: "5s"
    ## Data format to consume.
    ## Each data format has its own unique set of configuration options, read
    ## more about them here:
    ## https://github.com/influxdata/telegraf/blob/master/docs/DATA_FORMATS_INPUT.md
    data_format: "json"

I get the following error:

$ kubectl logs -f gaige-telegraf-s-69fc897bbf-6c8jj
2018/04/12 21:49:07 I! Using config file: /etc/telegraf/telegraf.conf
2018/04/12 21:49:07 E! Error parsing /etc/telegraf/telegraf.conf, Undefined but requested input: http

#2

This plugin is only in the upcoming 1.6. For some use cases you can use the httpjson plugin instead in 1.5.


#3

What is the procedure for tick-charts getting updated when there is a version bump like this? When can I expect the chart to be updated?


#4

I don’t see this plugin anywhere in the values.yaml file for telegraf-s


#5

Hi @gaigepr, looks like the docker hub has been updated: https://hub.docker.com/r/library/telegraf/ . it usually takes 24 - 48 hours after a release for everything to be updated.

As for the tick-charts, we are working on finding an internal maintainer for those. Until then, you will need to update the values.yaml locally. The README has instructions on how to do that. We are happy to review a PR for those updates if you’re interested in contributing.

Thanks,
Russ