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
In #20 and the README indicating there might be issues with logging the params hash, I'm a bit concerned, as most of the problems I encounter have needed the params hash to discover the source of the errors. I don't want to explode my logs OR lose log records, neither is useful.
Is there an alternative I can use that let's me still view the params hash, but doesn't cause either of those problems to show up? For example, could I somehow have them logged simply as a custom value converted to a string?
The text was updated successfully, but these errors were encountered:
That should give you a json string instead of nested fields. But I'm not 100% sure if logstash won't try to parse that JSON, but my guess is that it shouldn't, because the second layer of JSON encoding should entity-ify the params JSON.
In #20 and the README indicating there might be issues with logging the params hash, I'm a bit concerned, as most of the problems I encounter have needed the params hash to discover the source of the errors. I don't want to explode my logs OR lose log records, neither is useful.
Is there an alternative I can use that let's me still view the params hash, but doesn't cause either of those problems to show up? For example, could I somehow have them logged simply as a custom value converted to a string?
The text was updated successfully, but these errors were encountered: