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
[-] catloaf@lemm.ee 0 points 2 days ago

Generally no, there is no one piece of software that can magically handle the quirks of each other piece of software. If there is, someone is making a lot of money by selling it.

If you want to handle your uncommon output formats, you'll need to define them in your log processor.

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

Well I can get the logs in Seq. I don't know how to process the logs that come in so they are at the right level, timestamp, message, etc. Guess I look into it tomorrow...

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