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
I have logs that are mostly json, but some logs come from system calls that can't be structured. It would be nice if I could set a rule that allowed me to capture the whole log and put it for example in the "message" column. Otherwise , I end up with logs that look empty until I drill into them.
I tried setting the template Key to be empty or *, but neither of those worked.
The text was updated successfully, but these errors were encountered:
On Thu, 10 Oct 2024 at 6:00 am, Arthur ***@***.***> wrote:
I have logs that are mostly json, but some logs come from system calls
that can't be structured. It would be nice if I could set a rule that
allowed me to capture the whole log and put it for example in the "message"
column. Otherwise , I end up with logs that look empty until I drill into
them.
I tried setting the template Key to be empty or *, but neither of those
worked.
—
Reply to this email directly, view it on GitHub
<#24>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANCU24HC6J6JC7YDPPKQDE3Z2V4LVAVCNFSM6AAAAABPVFZUIWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TMNZRGM4DIOA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
I have logs that are mostly json, but some logs come from system calls that can't be structured. It would be nice if I could set a rule that allowed me to capture the whole log and put it for example in the "message" column. Otherwise , I end up with logs that look empty until I drill into them.
I tried setting the template Key to be empty or
*
, but neither of those worked.The text was updated successfully, but these errors were encountered: