posted in Selfhosted
How do you monitor your servers?
Running services, network usage, memory usage, bandwidth, disk I/O, successful logins, whether the thing is even alive, etc…
So far my only method has been “hope and pray”.
posted in Selfhosted
How do you monitor your servers?
Running services, network usage, memory usage, bandwidth, disk I/O, successful logins, whether the thing is even alive, etc…
So far my only method has been “hope and pray”.
Replying to @user224@lemmy.sdf.org
Cockpit. Total gamechanger for me. I don’t have to ssh to my boxes individually to see what’s going on. Instead it’s a web UI AND you can connect basically every server you want to one instance.
github.com/cockpit-project/cockpit
That said. For individual servers?
htop/nmon (Get nmon straight from the source! nmon.sourceforge.io/pmwiki.php) for a birds-eye sysmon view of things
ps -ef | grep <whatever you’re looking for> for investigating stuck/hung/zombie processes
dmseg
tail -f /var/log (or whatever log file you care about)
netstat for net statistics (i think ntop used to be a thing but idk anymore>…)
df -h to look at disk usage
those are all that come to mind right away.
EDIT: formatting and quick explanation of what each tool does
GitHubGitHub - cockpit-project/cockpit: Cockpit is a web-based graphical interface for servers.Cockpit is a web-based graphical interface for servers. - cockpit-project/cockpitLol I go to all of my server’s specific cockpit addresses, sounds like I’m doing it wrong, I’ll need to look at connecting them
Replying to @Owljfien@piefed.world
So it turns out… you can’t connect them anymore… The feature is deprecated
docs.cockpit-project.org/…/feature-machines.html
(also, I wanted to just link my response from another user who had asimilar question but for whateVER reasyon, Alx won’t let me??)