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

Improve startup error reporting when ran as Windows service (#4291)

Browse Source
This commit is contained in:
Vlasta Hajek
2019-08-28 23:34:44 +02:00
committed by Daniel Nelson
parent 8c6ddcd7fa
commit 7ec54d4be9
8 changed files with 295 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/CONFIGURATION.md
View File

@@ -141,8 +141,12 @@ The agent table configures Telegraf and the defaults used across all plugins.
- **quiet**:
Log only error level messages.
- **logtarget**:
Log target - `file`, `stderr` or `eventlog` (Windows only).
The empty string means to log to stderr.
- **logfile**:
Log file name, the empty string means to log to stderr.
Log file name.
- **logfile_rotation_interval**:
The logfile will be rotated after the time interval specified. When set to

9
docs/WINDOWS_SERVICE.md
View File

@@ -56,8 +56,13 @@ You can install multiple telegraf instances with --service-name flag:
> C:\"Program Files"\Telegraf\telegraf.exe --service uninstall --service-name telegraf-1
```
Troubleshooting common error #1067
## Troubleshooting
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
**Troubleshooting common error #1067**
When installing as service in Windows, always double check to specify full path of the config file, otherwise windows service will fail to start
--config C:\"Program Files"\Telegraf\telegraf.conf
--config "C:\Program Files\Telegraf\telegraf.conf"