Suppressing ActionCable noise in development logs

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Suppressing ActionCable noise in development logs

Dave Tapley
For reasons I will reveal at my Railsconf talk I am sending Data URIs through ActionCable.

These are rather large strings, which leads to a lot of noise in development, because ActionCable logs the entire message payload.

I have monkey patched around it, but I wanted to gauge whether this is something worth submitting a pull request against Rails for?
Does anyone know of any existing precedent for suppressing log output to avoid spamming it?

Thanks.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/50c01557-f555-448d-8757-bb937f834e40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Suppressing ActionCable noise in development logs

Walter Lee Davis
Have you tried simply adding that column to the filtered attributes? Passwords and such are already replaced with FILTERED in the logs, you could probably add these attributes and get the same effect.

Walter

> On Apr 10, 2017, at 2:05 PM, Dave Tapley <[hidden email]> wrote:
>
> For reasons I will reveal at my Railsconf talk I am sending Data URIs through ActionCable.
>
> These are rather large strings, which leads to a lot of noise in development, because ActionCable logs the entire message payload.
>
> I have monkey patched around it, but I wanted to gauge whether this is something worth submitting a pull request against Rails for?
> Does anyone know of any existing precedent for suppressing log output to avoid spamming it?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To post to this group, send email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/50c01557-f555-448d-8757-bb937f834e40%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/73C4064D-12E6-4C48-B480-CE72F2C6AF7A%40wdstudio.com.
For more options, visit https://groups.google.com/d/optout.
Loading...