Looking for a logging solution (sh.itjust.works)

submitted 2 days ago by Eezyville@sh.itjust.works to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

Ok so I've been having a problem with logging for a while now. I use a centralized logging platform (Seq) to try and aggregate the logs of the containers I run but most of the log messages come through as errors. This is because the containers would stream their output to stderr and even though it's formatted it comes as one big error message.

Example:

[2025-01-06 18:17:23] INFO Registering with TVA backend, encode Job status: available

That's all one big error message I receive even though it's an INFO message. And every container is different. Their error message is formatted differently, some goes to stdout instead of stderr, some actually work.

Is there a piece of software that I can run that will intercept these messages and convert them to GELF?

Thanks

you are viewing a single comment's thread
view the rest of the comments

[-] rumba@lemmy.zip 4 points 2 days ago

No I get what you're asking for I'm just mentioning that sometimes it's easier to use an application that can read multiple formats than it is to try to finagle everything back into one format.

[-] Eezyville@sh.itjust.works 1 points 2 days ago

Yeah but the thing is I have it set up to read the logs being sent out from my Docker containers. Even though I've set the containers to output using the GELF driver they don't really do that. The log messages my container send are not in GELF format so I have to find a way to fix that.

[-] rumba@lemmy.zip 1 points 2 days ago

Best of luck with it, logging's always a severe pain in the ass.

this post was submitted on 07 Jan 2025

17 points (87.0% liked)

Selfhosted

40956 readers

862 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz