Ability to disable ActionCable MonkeyPatch

[jwhitcraft]

We are using this gem currently, but we want to migrate away from ActionCable in-favor of AnyCable, but when this gem it doesn't allow us to since AnyCable uses a custom ActionCable::Connection::Base class found here which has a custom handle_open and handle_close. Would it be possible to provide a way to disable ActionCable Logging?

Thanks.

[georgepalmer]

As another use case for the ability to disable action cable integration we run a separate cable server and the default Rails logs are much more verbose. For example we get "unauthorized connection attempt" events which don't seem to come through with this. I know this isn't your fault and the logging in ActionCable is a mess, but it'd be great if we could use lograge on our main app and keep the Rails default on the ActionCable server.

Additionally IP address isn't available in the ActionCable logs which is a critical one for us as we want to know IPs when there are bad actors

[uhrohraggy]

FYI - this is still an issue today. #304 appears to address this fully (not splitting up log handlers but allowing lograge to work with both main app and action cable/anycable)

[rromanchuk]

@georgepalmer have you successfully monkey patched the monkey patch out of your system? I need to isolate and reduce complexity because i'm spending too much time on this.

After updating to latest anycable, sentry, lograge, rails 7 i'm now imploding here

wrong number of arguments (given 1, expected 0)
lograge (bf6954566607) lib/lograge/rails_ext/action_cable/channel/base.rb in subscribe_to_channel at line 6

[iloveitaly]

@rromanchuk have you tried the master version? This should be fixed on master.

[rromanchuk]

@iloveitaly reverting back to palkan/lograge fixed it, I probably only had roidrage/lograge thinking it was already tagged. I'll try again later

[iloveitaly]

@rromanchuk roidrage/lograge should contain the fix for this (2fd03f7). Is roidrage/lograge master not working for you? What error are you running into?