lab/homelab
1
0
Fork 0
Code Issues 33 Projects Releases Packages Wiki Activity Actions

Beszel alerting rules for cluster health (replaces Prometheus rules) #40

New issue
Open
opened 2026-07-25 19:37:21 +00:00 by lab · 0 comments
lab commented 2026-07-25 19:37:21 +00:00
Owner
Copy link

Alertmanager is configured with ntfy receiver, but no alerting rules exist. With the shift to a lightweight stack (see #11), alerting moves from PromQL rules to Beszel threshold alerts -- configured in the hub UI, no YAML/PromQL.

Rules to configure in Beszel hub (per node)

  1. Node down -- agent status alert (system unreachable)
  2. Disk near full -- disk usage > 80% per partition
  3. CPU / memory spikes -- threshold per node
  4. Temperature -- if sensors exposed
  5. Cert expiry -- handled by Uptime Kuma monitors (see #41), not Beszel

Steps

  1. Deploy Beszel hub + agent (see #11).
  2. Add ntfy notification channel in hub settings (shoutrrr ntfy://).
  3. Set threshold alerts per system in the hub UI.
  4. Verify a test alert fires to ntfy.

Note

While the full stack still runs in parallel (before teardown), existing Alertmanager config stands as-is. No PrometheusRule resources are needed for the new stack.

Alertmanager is configured with ntfy receiver, but no alerting rules exist. With the shift to a lightweight stack (see #11), alerting moves from PromQL rules to **Beszel threshold alerts** -- configured in the hub UI, no YAML/PromQL. ## Rules to configure in Beszel hub (per node) 1. **Node down** -- agent status alert (system unreachable) 2. **Disk near full** -- disk usage > 80% per partition 3. **CPU / memory spikes** -- threshold per node 4. **Temperature** -- if sensors exposed 5. **Cert expiry** -- handled by Uptime Kuma monitors (see #41), not Beszel ## Steps 1. Deploy Beszel hub + agent (see #11). 2. Add ntfy notification channel in hub settings (shoutrrr `ntfy://`). 3. Set threshold alerts per system in the hub UI. 4. Verify a test alert fires to ntfy. ## Note While the full stack still runs in parallel (before teardown), existing Alertmanager config stands as-is. No PrometheusRule resources are needed for the new stack.
lab changed title from Add Prometheus alerting rules for cluster health to Beszel alerting rules for cluster health (replaces Prometheus rules) 2026-08-01 19:15:47 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
feature/42-ddns-automation
feature/41-uptime-kuma
feature/11-grafana-cleanup
feature/11-drop-crowdsec-beszel
feature/11-beszel-notify-fix
feature/11-beszel-workflow-dispatch
feature/11-beszel-monitoring
feature/forgejo-action
feature/monitoring
feature/metube
feature/crowdsec
feature/mysql
feature/termix
feature/forgejo-runner
feature/authelia
feature/lldap
No results found.
Labels
Clear labels   
Monitoring

Monitoring stack for environment

  
automation

Automation/CI tasks

  
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
feature

New feature

  
forgejo

Forgejo setup/config

  
help wanted

Need some help

  
invalid

Something is wrong

  
k3s

K3s related

  
keycloak

Keycloak related

  
ldap

Light LDAP implementation for authentication

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
Monitoring
automation
bug
duplicate
feature
forgejo
help wanted
invalid
k3s
keycloak
ldap
question
wontfix
Milestone
Clear milestone
No items
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lab/homelab#40
No description provided.