From 146424a6eab489c66b3187f67b3d897f02ded2cc Mon Sep 17 00:00:00 2001
From: VictorRobellini <39597627+VictorRobellini@users.noreply.github.com>
Date: Thu, 4 Mar 2021 22:22:12 -0500
Subject: [PATCH] updated Readme

Added easier telegraf troubleshooting step
---
 README.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 16aebc4..30b488a 100644
--- a/README.md
+++ b/README.md
@@ -110,10 +110,15 @@ I also included a wrapper script for Unbound DNS.  I'm not currently using it, b
 
 ### Telegraf Plugins
 
-- You can run most plugins from a shell/ssh session to verify the output.
+- You can run most plugins from a shell/ssh session to verify the output. (the environment vars may be differet when telegraf is executing them)
 - If you're copying from a windows system, make sure the [CRLF is correct](https://www.cyberciti.biz/faq/howto-unix-linux-convert-dos-newlines-cr-lf-unix-text-format/)
 
-To troubleshoot plugins, add the following lines to the agent block in /usr/local/etc/telegraf.conf and send a HUP to the telegraf pid. You're going to need to do this from a ssh shell. One you update the config you are going to need to tell telegraf to read the new configs. If you restart telegraf from pfSense, this will not work since it will overwrite your changes.
+#### Telegraf Troubleshooting
+If you get no good output from running the plugin directly, try the following command before moving to the below step.
+
+    # telegraf --test --config /usr/local/etc/telegraf.conf
+
+To troubleshoot plugins further, add the following lines to the agent block in /usr/local/etc/telegraf.conf and send a HUP to the telegraf pid. You're going to need to do this from a ssh shell. One you update the config you are going to need to tell telegraf to read the new configs. If you restart telegraf from pfSense, this will not work since it will overwrite your changes.
 
 #### Telegraf Config
     debug = true