title: Sending metrics from telegraf to prometheus
body: <p>I'm running <code>prometheus</code> and <code>telegraf</code> on the same host.</p>
  
  <p>I'm using a few inputs plugins:</p>
  
  <ul>
  <li>inputs.cpu</li>
  <li>inputs.ntpq</li>
  </ul>
  
  <p>I've configured to the <code>prometheus_client</code> output plugin to send data to prometheus</p>
  
  <p>Here's my config:</p>
  
  <pre><code>    [[outputs.prometheus_client]]
        ## Address to listen on.
        listen = ":9126"
  
        ## Use HTTP Basic Authentication.
        # basic_username = "Foo"
        # basic_password = "Bar"
  
        ## If set, the IP Ranges which are allowed to access metrics.
        ##   ex: ip_range = ["192.168.0.0/24", "192.168.1.0/30"]
        # ip_range = []
  
        ## Path to publish the metrics on.
        path = "/metrics"
  
        ## Expiration interval for each metric. 0 == no expiration
        #expiration_interval = "0s"
  
        ## Collectors to enable, valid entries are "gocollector" and "process".
        ## If unset, both are enabled.
        # collectors_exclude = ["gocollector", "process"]
  
        ## Send string metrics as Prometheus labels.
        ## Unless set to false all string metrics will be sent as labels.
        # string_as_label = true
  
        ## If set, enable TLS with the given certificate.
        # tls_cert = "/etc/ssl/telegraf.crt"
        # tls_key = "/etc/ssl/telegraf.key"
  
        ## Export metric collection time.
        #export_timestamp = true
  
  Here's my prometheus config
  
  # my global config
  global:
    scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
    evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
    # scrape_timeout is set to the global default (10s).
  
  # Alertmanager configuration
  alerting:
    alertmanagers:
    - static_configs:
      - targets:
        # - alertmanager:9093
  
  # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
  rule_files:
    # - "first_rules.yml"
    # - "second_rules.yml"
  
  # A scrape configuration containing exactly one endpoint to scrape:
  # Here it's Prometheus itself.
  scrape_configs:
    # The job name is added as a label `job=&lt;job_name&gt;` to any timeseries scraped from this config.
    - job_name: 'prometheus'
  
      # metrics_path defaults to '/metrics'
      # scheme defaults to 'http'.
  
      static_configs:
        - targets: ['localhost:9090']
  
  #  - job_name: 'node_exporter'
  #    scrape_interval: 5s
  #    static_configs:
  #      - targets: ['localhost:9100']
  
    - job_name: 'telegraf'
      scrape_interval: 5s
      static_configs:
        - targets: ['localhost:9126']
  </code></pre>
  
  <p>If i'm going to <code>http://localhost:9090/metrics</code> i don't see any metrics which are coming from telegraf.</p>
  
  <p>I've captured some logs from telegraf as well</p>
  
  <p><code>/opt telegraf --config /etc/telegraf/telegraf.conf --input-filter filestat --test
  ➜  /opt tail -F  /var/log/telegraf/telegraf.log
  2019-02-11T17:34:20Z D! [outputs.prometheus_client] wrote batch of 28 metrics in 1.234869ms
  2019-02-11T17:34:20Z D! [outputs.prometheus_client] buffer fullness: 0 / 10000 metrics.
  2019-02-11T17:34:30Z D! [outputs.file] wrote batch of 28 metrics in 384.672µs
  2019-02-11T17:34:30Z D! [outputs.file] buffer fullness: 0 / 10000 metrics.
  2019-02-11T17:34:30Z D! [outputs.prometheus_client] wrote batch of 30 metrics in 1.250605ms
  2019-02-11T17:34:30Z D! [outputs.prometheus_client] buffer fullness: 9 / 10000 metrics.</code></p>
  
  <p>I don't see an issue in the logs.</p>