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

feature-request: make log-courier logs configurable #10

Closed
sysmonk opened this issue Jul 3, 2014 · 2 comments
Closed

feature-request: make log-courier logs configurable #10

sysmonk opened this issue Jul 3, 2014 · 2 comments
Assignees
Milestone

Comments

@sysmonk
Copy link
Contributor

sysmonk commented Jul 3, 2014

Hi,

It would be nice if we could make the log-courier more configurable. Now, there's only option to log to syslog or not. I'd like to log to syslog, but be able to have different type of loggings - 'verbose' - the current logging, and 'info' or something like that - which would only log file rotations/reconnects/failures.

Use case: log-courier running on busy server, sending thousands of log events per second, and writing the 'Registrar received X events' every second/few times per second and flooding the logs with that. It'd be great to disable the registrar log lines, but still be able to see when log-courier fails/disconnects/reconnects. This probably can be achieved by configuring the syslog server, but... you know, it's nicer to just be able to toggle a switch in log-courier config :)

@driskell
Copy link
Owner

driskell commented Jul 4, 2014

Absolutely, it's something I've wanted to do for a while. Those registrar events are noisy, logging at least once every 5 seconds. My original plan was to start with this specific event and just log it once to state events are successfully being submitted to the endpoint, "Endpoint X is successfully receiving events". Then it would not log again until reconnect.

@driskell
Copy link
Owner

I've started working on this.

I'm just tweaking log levels at the moment, and making the received events message debug only.
I'll also add a "Server is ack events" message. In the future I'll expand it to say which server is receiving, so you can debug easily, but that's a fair bit of extra work in the ZMQ - but it needs it since the ZMQ is a little blind at the moment

Jason

@driskell driskell added this to the 0.11 milestone Jul 12, 2014
@driskell driskell self-assigned this Jul 12, 2014
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