[GH-ISSUE #24] Implement or Document ability to capture unstructured logs #5

New issue

Open

opened 2026-03-03 00:06:04 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 00:06:04 +03:00

Owner

Originally created by @arthuratplayableworlds on GitHub (Oct 9, 2024).
Original GitHub issue: https://github.com/aurc/loggo/issues/24

Originally assigned to: @arthuratplayableworlds on GitHub.

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.

Originally created by @arthuratplayableworlds on GitHub (Oct 9, 2024). Original GitHub issue: https://github.com/aurc/loggo/issues/24 Originally assigned to: @arthuratplayableworlds on GitHub. 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.

kerem added the

need more info

label

2026-03-03 00:06:04 +03:00

kerem commented

2026-03-03 00:06:05 +03:00

Author

Owner

@aurc commented on GitHub (Oct 9, 2024):

Please send me a sample of your log and the template you created. I will
give it a think and get back to you!

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
https://github.com/aurc/loggo/issues/24, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANCU24HC6J6JC7YDPPKQDE3Z2V4LVAVCNFSM6AAAAABPVFZUIWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TMNZRGM4DIOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@aurc commented on GitHub (Oct 9, 2024): Please send me a sample of your log and the template you created. I will give it a think and get back to you! 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 > <https://github.com/aurc/loggo/issues/24>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ANCU24HC6J6JC7YDPPKQDE3Z2V4LVAVCNFSM6AAAAABPVFZUIWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TMNZRGM4DIOA> > . > You are receiving this because you are subscribed to this thread.Message > ID: ***@***.***> >

kerem referenced this issue

2026-03-03 00:06:08 +03:00

[PR #5] [MERGED] Feature/test tagging 3 #14

No labels

need more info

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/loggo#5

No description provided.

Rows
Columns