56
Observability Stack? (lemmy.ca)
submitted 1 day ago* by to c/selfhosted@lemmy.world
37 comments fedilink hide all child comments
 

I'm curious as to which tools and technologies you all are using to keep track of all those services you are deploying, whether it be resource tracking, network traffic, logs, traces, or uptime.

As a bonus question, how have you organized your network or your services to reduce the overhead of implementing observability?

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 1 day ago (3 children)

I recently switched to Dockhand from Portainer and I like it a lot more, it's much cleaner and straightforward. It also auto-updates so you might be able to ditch whats up docker too.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 1 day ago (2 children)

    No auto updates thanks. 😅 I've just reset all my compose files to pin versions today after an unintended mariadb update cost me hours to repair. I'll look into dockhand though. Was unimpressed at portainer's announcement that new version wont have a community edition. Portainer is really just an 'at a glance' view for me since i try to do all the compose and troubleshooting stuff in terminal. Wud will probably become a thing i just review every few weeks to make sure i dont get too adrift from latest.

    I ought to look into a unified dashboard as i dont have easy visibility or things like disk usage, sheduled backup success etc that id like to see alongside the container status and beszel activity graphs.

    Im still quite new to it all though.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •