From 61e317ab0681a16daf953b76d4757f51c145616d Mon Sep 17 00:00:00 2001
From: Corey Eichelberger <eichelbc@illinois.edu>
Date: Tue, 19 May 2020 15:02:42 -0500
Subject: [PATCH] Telegraf updates

---
 telegraf/10-agent.conf        | 54 +++++++++++++++++++++++++++++++++++
 telegraf/20-input-cpu.conf    | 10 +++++++
 telegraf/20-input-system.conf |  2 ++
 3 files changed, 66 insertions(+)
 create mode 100644 telegraf/10-agent.conf
 create mode 100644 telegraf/20-input-cpu.conf
 create mode 100644 telegraf/20-input-system.conf

diff --git a/telegraf/10-agent.conf b/telegraf/10-agent.conf
new file mode 100644
index 0000000..0816bab
--- /dev/null
+++ b/telegraf/10-agent.conf
@@ -0,0 +1,54 @@
+# Configuration for telegraf agent
+[agent]
+  ## Default data collection interval for all inputs
+  interval = "10s"
+  ## Rounds collection interval to 'interval'
+  ## ie, if interval="10s" then always collect on :00, :10, :20, etc.
+  round_interval = true
+
+  ## Telegraf will send metrics to outputs in batches of at most
+  ## metric_batch_size metrics.
+  ## This controls the size of writes that Telegraf sends to output plugins.
+  metric_batch_size = 1000
+
+  ## For failed writes, telegraf will cache metric_buffer_limit metrics for each
+  ## output, and will flush this buffer on a successful write. Oldest metrics
+  ## are dropped first when this buffer fills.
+  ## This buffer only fills when writes fail to output plugin(s).
+  metric_buffer_limit = 10000
+
+  ## Collection jitter is used to jitter the collection by a random amount.
+  ## Each plugin will sleep for a random time within jitter before collecting.
+  ## This can be used to avoid many plugins querying things like sysfs at the
+  ## same time, which can have a measurable effect on the system.
+  collection_jitter = "0s"
+
+  ## Default flushing interval for all outputs. Maximum flush_interval will be
+  ## flush_interval + flush_jitter
+  flush_interval = "10s"
+  ## Jitter the flush interval by a random amount. This is primarily to avoid
+  ## large write spikes for users running a large number of telegraf instances.
+  ## ie, a jitter of 5s and interval 10s means flushes will happen every 10-15s
+  flush_jitter = "0s"
+
+  ## By default or when set to "0s", precision will be set to the same
+  ## timestamp order as the collection interval, with the maximum being 1s.
+  ##   ie, when interval = "10s", precision will be "1s"
+  ##       when interval = "250ms", precision will be "1ms"
+  ## Precision will NOT be used for service inputs. It is up to each individual
+  ## service input to set the timestamp at the appropriate precision.
+  ## Valid time units are "ns", "us" (or "µs"), "ms", "s".
+  precision = ""
+  ## Logging configuration:
+  ## Run telegraf with debug log messages.
+  debug = false
+  ## Run telegraf in quiet mode (error log messages only).
+  quiet = false
+  ## Specify the log file name. The empty string means to log to stderr.
+  logfile = ""
+
+  ## Override default hostname, if empty use os.Hostname()
+  hostname = ""
+  ## If set to true, do no set the "host" tag in the telegraf agent.
+  omit_hostname = false
+
diff --git a/telegraf/20-input-cpu.conf b/telegraf/20-input-cpu.conf
new file mode 100644
index 0000000..30cdaa2
--- /dev/null
+++ b/telegraf/20-input-cpu.conf
@@ -0,0 +1,10 @@
+# Read metrics about cpu usage
+[[inputs.cpu]]
+  ## Whether to report per-cpu stats or not
+  percpu = true
+  ## Whether to report total system cpu stats or not
+  totalcpu = true
+  ## If true, collect raw CPU time metrics.
+  collect_cpu_time = false
+  ## If true, compute and report the sum of all non-idle CPU states.
+  report_active = false
diff --git a/telegraf/20-input-system.conf b/telegraf/20-input-system.conf
new file mode 100644
index 0000000..3423876
--- /dev/null
+++ b/telegraf/20-input-system.conf
@@ -0,0 +1,2 @@
+[[inputs.system]]
+  # no configuration
-- 
GitLab