Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Service results in no log output #1786

Closed
peter-murray opened this issue Sep 19, 2016 · 1 comment · Fixed by #1838
Closed

Windows Service results in no log output #1786

peter-murray opened this issue Sep 19, 2016 · 1 comment · Fixed by #1838
Labels
bug unexpected problem or unintended behavior help wanted Request for community participation, code, contribution platform/windows

Comments

@peter-murray
Copy link
Contributor

Bug report

System info:

  • telegraf version 1.0.0
  • Windows Server 2012R2

Steps to reproduce:

Install the Windows service and then run it, there is no log output provided in files or the event log.

Expected behavior:

Log some output from the telegraf process

Actual behavior:

Nothing logged anywhere

Additional info:

In the old days of using the nssm wrapped approach, you could just redirect the stdout and stderr to a file, which worked fine.

Now that the service is being run using the Go service libraries, you probably have to utilize the event log and/or some log file output that captures the stdout/stderr differently under Windows.

@sparrc sparrc added bug unexpected problem or unintended behavior platform/windows help wanted Request for community participation, code, contribution labels Sep 19, 2016
@nhaugo nhaugo added this to the Future Milestone milestone Sep 28, 2016
@markballesteros markballesteros modified the milestones: 1.1.0, Future Milestone Sep 29, 2016
sparrc added a commit that referenced this issue Oct 3, 2016
in this commit:

- centralize logging output handler.
- set global Info/Debug/Error log levels based on config file or flags.
- remove per-plugin debug arg handling.
- add a I!, D!, or E! to every log message.
- add configuration option to specify where to send logs.

closes #1786
@sparrc sparrc mentioned this issue Oct 3, 2016
3 tasks
sparrc added a commit that referenced this issue Oct 3, 2016
in this commit:

- centralize logging output handler.
- set global Info/Debug/Error log levels based on config file or flags.
- remove per-plugin debug arg handling.
- add a I!, D!, or E! to every log message.
- add configuration option to specify where to send logs.

closes #1786
sparrc added a commit that referenced this issue Oct 3, 2016
in this commit:

- centralize logging output handler.
- set global Info/Debug/Error log levels based on config file or flags.
- remove per-plugin debug arg handling.
- add a I!, D!, or E! to every log message.
- add configuration option to specify where to send logs.

closes #1786
@sparrc
Copy link
Contributor

sparrc commented Oct 3, 2016

#1838 added the ability to specify the logfile as a configuration option.

I've created a separate issue for sending to the Windows event log: #1840

jackzampolin pushed a commit that referenced this issue Oct 7, 2016
in this commit:

- centralize logging output handler.
- set global Info/Debug/Error log levels based on config file or flags.
- remove per-plugin debug arg handling.
- add a I!, D!, or E! to every log message.
- add configuration option to specify where to send logs.

closes #1786
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior help wanted Request for community participation, code, contribution platform/windows
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants