updated Readme

Added easier telegraf troubleshooting step
This commit is contained in:
VictorRobellini 2021-03-04 22:22:12 -05:00 committed by GitHub
parent 2853b5c3eb
commit 146424a6ea
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -110,10 +110,15 @@ I also included a wrapper script for Unbound DNS. I'm not currently using it, b
### Telegraf Plugins ### 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/) - 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 #### Telegraf Config
debug = true debug = true