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

Deploy Uptime Kuma for synthetic checks and cert expiry (replaces Loki) #41

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

Original intent was Grafana + Loki for log aggregation. Dropped -- very few logs flow in this cluster, and it goes against the lightweight direction (see #11).

Replaced by Uptime Kuma for the alerting/availability value that monitoring still needs:

  • Synthetic HTTP(S) checks for services (is the site actually up?)
  • TLS certificate expiry monitoring (previously would have been a Prometheus rule)
  • Notifications -> ntfy

Steps

  1. Deploy Uptime Kuma via Helm chart in monitoring (or ntfy) namespace, Longhorn PVC.
  2. Add monitors for public endpoints (yukselcloud.com services behind Caddy).
  3. Configure TLS cert expiry alerts -> ntfy.
  4. Add Caddy route behind Authelia (see #27) + Homer dashboard link (see #11 step 7).
  5. Optionally make status page public.
Original intent was Grafana + Loki for log aggregation. **Dropped** -- very few logs flow in this cluster, and it goes against the lightweight direction (see #11). Replaced by **Uptime Kuma** for the alerting/availability value that monitoring still needs: - Synthetic HTTP(S) checks for services (is the site actually up?) - **TLS certificate expiry** monitoring (previously would have been a Prometheus rule) - Notifications -> ntfy ## Steps 1. Deploy Uptime Kuma via Helm chart in `monitoring` (or `ntfy`) namespace, Longhorn PVC. 2. Add monitors for public endpoints (yukselcloud.com services behind Caddy). 3. Configure TLS cert expiry alerts -> ntfy. 4. Add Caddy route behind Authelia (see #27) + Homer dashboard link (see #11 step 7). 5. Optionally make status page public.
lab changed title from Add Loki for centralized log aggregation to Deploy Uptime Kuma for synthetic checks and cert expiry (replaces Loki) 2026-08-01 19:15:48 +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#41
No description provided.