Make the Machine Cry Before You Get the Call
Monitoring's endgame is alerts that get handled, not pretty dashboards. Security's endgame is actions you can replay, not a thick hardening binder. Here we write: how Prometheus Alertmanager translates "CPU high" into "which machine, which process, next step"; how SSH hardening avoids locking yourself out; how to TCO bastion choices.
Contents (7 posts)
| Slug | Value | Keyword |
|---|---|---|
| [prometheus-deploy](prometheus-deploy.md | Docker + systemd side-by-side, 5-min run ⭐ | Prometheus deploy |
| [prometheus-query](prometheus-query.md | 10 PromQL recipes, copy-paste | PromQL recipes |
| [prometheus-alerting](prometheus-alerting.md | Alertmanager routing + Silence vs Inhibit | Prometheus alerting |
| [grafana-dashboard](grafana-dashboard.md | Data sources / variables / panels | Grafana dashboards |
| [zabbix-setup](zabbix-setup.md | Active vs passive Agent, one config | Zabbix Agent |
| [ssh-hardening](ssh-hardening.md | Hardening Top 8, incl. "don't lock yourself out" | SSH hardening |
| [bastion-jumpserver](bastion-jumpserver.md | Self-hosted vs commercial, JumpServer | Bastion selection |
Launch Flagship
[Prometheus Deploy: Docker + systemd](prometheus-deploy.md ⭐ W2 flagship
Docker Compose to systemd, Prometheus + node_exporter + a minimal Alertmanager chain. Includes measured memory and retention numbers.
Tags
prometheuspromqlgrafanazabbixsshhardeningjumpserveralertmanager