17

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
[-] just_another_person@lemmy.world -1 points 2 days ago

https://docs.datalust.co/docs/collecting-docker-container-logs

You have a formatting issue. Solve for that instead of just switching to something else hoping it will get better.

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

I've done that. I don't have a formatting issue. The containers I'm trying to get logs from have a formatting issue. They don't stream their logs in GELF. I am getting the logs but I can't change the formatting that they send me unless I mess with the code itself.

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS