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

Cockpit is a web-based graphical interface for servers. - cockpit-project/cockpitGitHubGitHub - cockpit-project/cockpit: Cockpit is a web-based graphical interface for servers.Cockpit is a web-based graphical interface for servers. - cockpit-project/cockpit

Replying to @⁨nosuchanon@lemmy.world⁩

So I actually just went to make a guide on this, demonstrating on my ubuntu 26.04 lab vps, and it appears the connect option is not there.

However on my 24.04 lab vps, it’s there. Same with my local 22.04 systems (yes I know I have to upgrade lmao)

I went to cockpit docks and sure enough, the feature is deprecated :( Dang.

docs.cockpit-project.org/…/feature-machines.html

It was really cool though while it worked.

Replying to @⁨WeirdGoesPro@lemmy.dbzer0.com⁩

Sure! In Uptime Kuma, add a monitor with type Push. It gives you a URL with a unique token, and the monitor goes into “down” state if nothing calls that URL within the heartbeat interval. Then have a cron (or a systemd timer or whatever) run this on the machine with the drive every 5 or 10 minutes:

use=$(df --output=pcent /mnt/yourdrive | tail -1 | tr -dc ‘0-9’)
curl -fsS -G “http://your-kuma:3001/api/push/TOKEN --data-urlencode “status=up” --data-urlencode “msg=${use}% used” --data-urlencode “ping=${use}”

Ping is of course meant to be response time, but Kuma will graph any number you toss in, so you get a “filled” chart for the drive. I also send status=down once usage passes a threshold. And if the box itself should fall over for some reason, the missing check-ins trigger the alert too.

(I typed this quick on my phone, so please double-check and probably don’t blindly copy-paste)

Replying to @⁨apex@mastodon.uno⁩

With Uptime Kuma, I just used ping and http sensors so that I knew my stuff was up. When I switched to CheckMK, I installed the agent on all servers and that brought quite a bit more info in, then I added the Proxmox integration and that gave me the snapshot info (as well as more info). I think it automatically pulled in my ZFS info, like zpool status. Then added smart monitoring to my storage so that I can see that my hard drives have been spinning for 13 years and 266 days 😅

Replying to @⁨user224@lemmy.sdf.org⁩

SNMP.

The old engine was nagios. The new engine will be telegraf -> mqtt -> brokerfest -> timescale -> Prometheus.

I guess. Not sure yet. The brokerfest is a series of broker pubsub between sites to both split out data from the stream for off-site CC, or pull its own subscriptions in. Data could go host <- telegraf -> broker -> remote broker -> remote timescale -> remote Prometheus

Replying to @⁨user224@lemmy.sdf.org⁩

I vibe coded a monitor that shows me all the logs and other stuff. And im using netbird cloud (free version) to setup dns so all my services have url “servicexyz.home.internal”.

So i just connect to netbird vpn on my phone and go to that url.

You can pretty much use any of the other tools mentioned in this thread with this kind of setup, heck you can write a simple fastapi server that just runs “top” and return it (it would be like 20-30 lines of python) over a url that you can from anywhere as long as you are connected to your vpn

Replying to an earlier post

When logged in locally, I use btop to see an overview of what’s happening.

Other than that, I have relevant Prometheus exporters in every machine (node exporter in all machines, specific exporters by the workload), hooked up over Wireguard to my monitoring solution offsite.

The phone I actually carry around has a ntfy client talking to ntfy server on the aforementioned monitoring solution, so I get buzzes when something goes down.

Btw, does anybody happen to know where I could get a comprehensive

Replying to @⁨dimjim@sh.itjust.works⁩

I am also using Beszel after using checkmk. For me checkmk was way too complicated (but is also way more powerfull) to setup and maintain propperly. So I switcheed to beszel because it is much easier and good enough for my use case which is:

  • Is the thing running at all?
  • Disk full?
  • CPU, network, etc. on full throttle for some strange reason?
  • send me a mail if somethings wrong

Besides that I don’t need anything. The only thing missing is SNMP support to check switches, routers and AP’s.

Replying to @⁨Alfredolin@lemmy.zip⁩

If you run Proxmox and Proxmox Backup Server, I actually JUST found a better product for my needs, Pulse

My only problem with Beszel is that it doesn’t know about LXCs within Proxmox, so I can’t see if there are CPU/memory issues happening within them. Pulse integrates directly and can see all of it!

If you don’t run LXCs within Proxmox, I’d say stick with Beszel.

Replying to @⁨user224@lemmy.sdf.org⁩

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

Fewer Letters More Letters AP WiFi Access Point DNS Domain Name Service/System ISP Internet Service Provider LXC Linux Containers NAS Network-Attached Storage NFS Network File System, a Unix-based file-sharing protocol known for performance and efficiency RAID Redundant Array of Independent Disks for mass storage SSH Secure Shell for remote terminal access TLS Transport Layer Security, supersedes SSL ZFS Solaris/Linux filesystem focusing on data integrity

[Thread #122 for this comm, first seen 9th Oct 2026, 13:00] [FAQ] [Full list] [Contact] [Source code]

Hachyderm.ioImran Nazar ~ عمران نزر (@Two9A@hachyderm.io)3.05K Posts, 306 Following, 284 Followers · Front-end #typescript developer and general keyboard tapper; author of Internet RFC 7168 (Hypertext Coffeepot Control Protocol for teapots); occasional plumber, more than occasional #c64 #retrocomputing enthusiast, terrible at classical #piano. Header photo is a verdant scene looking over the landscape near Buxton, England, taken from a single-track country road.

Replying to @⁨user224@lemmy.sdf.org⁩

Well, it’s a good learning experience. But…… don’t. Good luck getting around the major email providers’ smart screen shit. It’s probably not gonna happen. I tried a few years ago, and even microslop couldn’t figure out why their shit screen crap wouldn’t allow my emails. It’s not in their best interest to fix it. So they don’t. But it’s worth doing it in the short term to learn how to do it. Teaches you about email, spf, dkim etc. which actually does translate to real world skills. I used what I learnt setting it up in my real life job.

Replying to @⁨bertlewirth@lemmy.world⁩

Yeah, email is one of the more annoying things to self host. Google rejects mine because my ISP has all their non static IPs on block lists (even though my IP hasn’t changed once since I’ve been with them it’s still not “static”, can’t change the reverse DNS) and I’m not paying 150% more a month for a business account to get a static IP. I ended up just using a free email relay. Still had to setup SPF, DKIM, DMARC, and all that jazz still.

Replying to @⁨user224@lemmy.sdf.org⁩

I self-host my own email, have done so for years. I’ve not gotten pwned. Use an SSH key and a firewall, only expose the ports that should be public, have reasonable access controls, etc, just practise general cybersecurity—it applies to servers too.

I know everyone complains about hosting email. But I’ve not run into major problems. My emails get through spam filters and I have good uptime. It’s also a fun learning experience.

Replying to @⁨communism@lemmy.ml⁩

I think that you have to do quite a bit more setup on email than most other services. There’s SPF and DKIM and DMARC and so on. Plus spam filtering, setting up accounts and authentication, …

Plus email is arguably more important than anything else, since it’s kind of the lowest common denominator of the Internet; your dentist will probably send you an email to remind you of appointments, job offers will arrive via email, password resets arrive via email, and so on.

So it is a bit scary.

Having said that, as long as you’re not hosting from a residential IP addresses it is definitely achievable. You can start with one domain and use it for low-value purposes (or for accounts that allow multiple email addresses, like GitHub).

Replying to @⁨NotEasyBeingGreen@slrpnk.net⁩

Yes, it can be a bit involved. I’d say I can spin up a mail server in 1–2 days though provided the OS is already installed and I have a domain name and port 25 isn’t blocked (that’s the main one that tends to be blocked). It may take longer for people who aren’t familiar with mail servers but it’s not some huge operation.

You can just try spinning up a mail server for fun. If it goes badly then just don’t move over your dentist appointments to it. It’s only critical infra if you use it for critical things, which you probably shouldn’t till it’s stable.

Replying to @⁨user224@lemmy.sdf.org⁩

I use Signoz and OTel collectors to bring in everything from Kubernetes (and also SNMP-to-OTel for the network and NAS stats.)

That covers dashboards and basic alerting. Then on top of that I have an n8n workflow that runs every morning - it pulls all the main stats out of Signoz, as well as issues and their status from my infrastructure repo in Gitlab, and feeds it all into a local LLM (Qwen-3.8-Flash-Next at the moment), which emails me a report on overall cluster health. It also automatically opens a ticket in Gitlab for anything that might need fixing.

It works really nicely, gotta say.