You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason being that even though silence_polling silences log statements, it does not silence instrumentation. That means that if the Rails app is hooked up to (for example) OpenTelemetry, the monitoring system receives thousands of BEGIN / COMMIT statements signifying nothing more than the polling is being checked. Can you tell when SQ was deployed? :P
Currently, I have a monkey patch to support ignoring this:
Hello! I was wondering if you'd accept a PR that implements instrumentation around polling. Something pretty much like this:
The reason being that even though
silence_polling
silences log statements, it does not silence instrumentation. That means that if the Rails app is hooked up to (for example) OpenTelemetry, the monitoring system receives thousands ofBEGIN
/COMMIT
statements signifying nothing more than the polling is being checked. Can you tell when SQ was deployed? :PCurrently, I have a monkey patch to support ignoring this:
I can then instruct my collector to just filter out any
polling.solid_queue
events. This works, but it would be nice to remove my hack. 😆The text was updated successfully, but these errors were encountered: