this post was submitted on 01 Aug 2023
22 points (92.3% liked)

Selfhosted

39435 readers
4 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 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
22
Docker logging solution? (sh.itjust.works)
submitted 1 year ago by [email protected] to c/[email protected]
10 comments fedilink hide all child comments
 

What is everyone using for their logging solution? So far I’ve not really done anything and just tail the container log when something is going wrong but a more long term, robust log aggregator would be great.

At work I’ve used things like data dog and sumo logic for logs and would love a small self hosted version of that. I don’t think I need long log retention (more than a day or two) but retention + search and maybe the option to create custom aggregations based on those logs would be awesome.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 1 year ago (1 children)

At work we use the syslog log driver for docker. Essentially any container stdout gets pushed in to the system syslog that then gets ingested into splunk through one of their forwarders. We needed more than just container logs so that's the reason for that. For a home setup I'd probably do the same but use the ELK stack instead of splunk.