dom
/
telegraf
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Document --service-display-name flag for Windows service

This commit is contained in:
Daniel Nelson 2019-12-10 13:13:03 -08:00
parent 7cfde0cf4d
commit 05cefe61bd
No known key found for this signature in database
GPG Key ID: CAAD59C9444F6155
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/WINDOWS_SERVICE.md
View File

@ -48,18 +48,21 @@ Telegraf can manage its own service through the --service flag:
## Install multiple services ## Install multiple services
You can install multiple telegraf instances with --service-name flag: Running multiple instances of Telegraf is seldom needed, as you can run
multiple instances of each plugin and route metric flow using the metric
filtering options. However, if you do need to run multiple telegraf instances
on a single system, you can install the service with the `--service-name` and
`--service-display-name` flags to give the services unique names:
``` ```
> C:\"Program Files"\Telegraf\telegraf.exe --service install --service-name telegraf-1 > C:\"Program Files"\Telegraf\telegraf.exe --service install --service-name telegraf-1 --service-display-name "Telegraf 1"
> C:\"Program Files"\Telegraf\telegraf.exe --service install --service-name telegraf-2 > C:\"Program Files"\Telegraf\telegraf.exe --service install --service-name telegraf-2 --service-display-name "Telegraf 2"
> C:\"Program Files"\Telegraf\telegraf.exe --service uninstall --service-name telegraf-1
``` ```
## Troubleshooting ## Troubleshooting
When Telegraf runs as a Windows service, Telegraf logs messages to Windows events log before configuration file with logging settings is loaded. When Telegraf runs as a Windows service, Telegraf logs messages to Windows events log before configuration file with logging settings is loaded.
Check event log for an error reported by `telegraf` service in case of Telegraf service reports failure on its start: Event Viewer->Windows Logs->Application Check event log for an error reported by `telegraf` service in case of Telegraf service reports failure on its start: Event Viewer->Windows Logs->Application
**Troubleshooting common error #1067** **Troubleshooting common error #1067**