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

Specify logfile output for log-courier #15

Closed
shoenig opened this issue Jul 14, 2014 · 3 comments
Closed

Specify logfile output for log-courier #15

shoenig opened this issue Jul 14, 2014 · 3 comments
Assignees
Milestone

Comments

@shoenig
Copy link
Contributor

shoenig commented Jul 14, 2014

Right now it seems log-courier can only send its own log output to stdout. It would be nice if you could specify a file to send its log output to instead.

@driskell
Copy link
Owner

What's your thoughts on syslog?

I suppose I'm on the fence with the debate,but you can log to syslog and it goes to messages usually. Then you can configure syslog to send to a different file if necessary.

At the moment it's stdout always and syslog optional. It will soon be one or the other though, and I could add file output fairly easily now it's using go-logging package. :-)

Jason

@shoenig
Copy link
Contributor Author

shoenig commented Jul 15, 2014

Unfortunately I don't think syslog is an option in our environment (thought it would be nice!). If you don't want to add support for file based logging I'll probably do it on my own branch anyway

@driskell driskell added this to the 0.12 milestone Jul 15, 2014
@driskell driskell self-assigned this Jul 15, 2014
@driskell
Copy link
Owner

It's an option I don't mind having. It's probably total of 10-15 extra lines which is fine.

I've penned it in since I've been fixing syslog and adding option to disable stdout logging anyway and it can sit amongst those settings.

Likely means moving from cmdline to config file to keep config bits from getting disparate.

driskell added a commit that referenced this issue Feb 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants