telegraf-inputs-plugin | 易学教程

Telegraf test input and output plugins error multiple conf files

阅读更多关于 Telegraf test input and output plugins error multiple conf files

问题 Telegraf version: Telegraf v1.0.1 I have the following files: /etc/telegraf/telegraf.conf main config file (which you create/get for free while installing telegraf). This file doesn't have any [[output.<plugin>]] stanza in it but does have valid default inputs.xx plugins enabled. /etc/telegraf/telegraf.d/1-company-output-plugin.conf (This file has valid outputs.<pluginname> plugin). /etc/telegraf/telegraf.d/telegraf-additional-inputs-plugins.conf (this file has additional inputs.<pluginname>

Telegraf test input and output plugins error multiple conf files

阅读更多关于 Telegraf test input and output plugins error multiple conf files

How to Insert a new string into telegraf.conf's inputs.ping using ansible regexp

阅读更多关于 How to Insert a new string into telegraf.conf's inputs.ping using ansible regexp

问题 I'm trying to use ansible to update telegraf.conf's [[inputs.ping]]. telegraf.conf looks like the following: [[inputs.ping]] urls = ["tac-temp1","tac-temp2", "tac-temp3","tac-temp4"] #tac count = 30 timeout = 15.0 [inputs.ping.tags] name = "tac" [[inputs.ping]] urls = ["prod-temp1","prod-temp2", "prod-temp3","prod-temp4"] #prod count = 30 timeout = 15.0 [inputs.ping.tags] name = "prod" [[inputs.ping]] urls = ["test-temp1","test-temp2", "test-temp3","test-temp4"] #test count = 30 timeout = 15

Monitoring nginx (500's) with telegraf

阅读更多关于 Monitoring nginx (500's) with telegraf

问题 I'd like to understand what my nginx instance is returning and who it's asking to handle requests. What fraction of my queries get handled by rails, what fraction are handled directly by nginx, what fraction are heading off to nginx_status, etc. Similarly, I'd also like to understand things like how many of which HTTP result codes I'm returning. If there's a peak in 500's, I'd like to know. The telegraf nginx plugin provides some very basic stats on nginx but no more. I've seen some vaguely

telegraf - exec plugin - aws ec2 ebs volumen info - metric parsing error, reason: [missing fields] or Errors encountered: [ invalid number]

阅读更多关于 telegraf - exec plugin - aws ec2 ebs volumen info - metric parsing error, reason: [missing fields] or Errors encountered: [ invalid number]

Machine - CentOS 7.2 or Ubuntu 14.04/16.xx Telegraf version: 1.0.1 Python version: 2.7.5 Telegraf supports an INPUT plugin named: exec . First please see EXAMPLE 2 in the README doc there. I can't use JSON format as it only consumes Numeric values for metrics. As per the docs: If using JSON, only numeric values are parsed and turned into floats. Booleans and strings will be ignored. So, the idea is simple, you specify a script in exec plugin section, which should spit some meaningful info(in either JSON -or- influx data format in my case as I have some metrics which contains non-numeric values

telegraf - exec plugin - aws ec2 ebs volumen info - metric parsing error, reason: [missing fields] or Errors encountered: [ invalid number]

阅读更多关于 telegraf - exec plugin - aws ec2 ebs volumen info - metric parsing error, reason: [missing fields] or Errors encountered: [ invalid number]

问题 Machine - CentOS 7.2 or Ubuntu 14.04/16.xx Telegraf version: 1.0.1 Python version: 2.7.5 Telegraf supports an INPUT plugin named: exec. First please see EXAMPLE 2 in the README doc there. I can't use JSON format as it only consumes Numeric values for metrics. As per the docs: If using JSON, only numeric values are parsed and turned into floats. Booleans and strings will be ignored. So, the idea is simple, you specify a script in exec plugin section, which should spit some meaningful info(in