We've been using Silencer in production for some time now; works great, thanks! The load balancer hits a particular URL every 2 seconds to verify the node is healthy, and any non-200 response means unhealthy. Silencer keeps all that traffic out of the log.
The hitch is, when something goes wrong (and a non-200 response is returned), we'd like to log the details. What would be great is if Silencer could take a logging level option that means: Silence matching log entries at (say) WARNING or below. Then anything ERROR or higher would still make it to the log for diagnosis.
We've been using Silencer in production for some time now; works great, thanks! The load balancer hits a particular URL every 2 seconds to verify the node is healthy, and any non-200 response means unhealthy. Silencer keeps all that traffic out of the log.
The hitch is, when something goes wrong (and a non-200 response is returned), we'd like to log the details. What would be great is if Silencer could take a logging level option that means: Silence matching log entries at (say) WARNING or below. Then anything ERROR or higher would still make it to the log for diagnosis.