tonym/NastyNAS
1
0
Fork 0
Code Issues 70 Pull Requests Actions Packages Projects Releases Wiki Activity

Configure Uptime Kuma Monitoring #40

New Issue
Open
opened 2025-09-14 08:10:48 +00:00 by tonym · 0 comments
tonym commented 2025-09-14 08:10:48 +00:00
Owner
Copy Link

Uptime Kuma Monitoring Configuration

Initial Setup

Critical Service Monitors

Database Monitors

  • MariaDB:
    • Type: MySQL/MariaDB
    • Connection string
    • Test query
  • PostgreSQL:
    • Type: PostgreSQL
    • Connection string
    • Test query

Docker Container Monitors

  • Type: Docker Container
  • Monitor container health status
  • Check restart counts

Notification Channels

  • Configure Discord:
    • Webhook URL
    • Custom message format
    • Test notification
  • Configure Email:
    • SMTP settings
    • Recipients
    • Test email
  • Configure Pushover:
    • User key
    • App token
    • Test push

Status Page

  • Create public status page
  • Group monitors by category
  • Custom domain (via NPM)
  • Custom branding

Testing

  • Simulate service failure
  • Verify notifications trigger
  • Check status page updates
  • Test from external network
## Uptime Kuma Monitoring Configuration ### Initial Setup - [ ] Access at http://[server-ip]:3001 - [ ] Create admin account - [ ] Set up 2FA authentication - [ ] Configure general settings ### Critical Service Monitors - [ ] Add Plex: - Type: HTTP(s) - URL: http://[plex-ip]:32400/web - Interval: 60 seconds - [ ] Configure notification - [ ] Add Sonarr: - URL: http://[sonarr-ip]:8989 - [ ] Add API health check - [ ] Add Radarr: - URL: http://[radarr-ip]:7878 - [ ] Add API health check - [ ] Add Prowlarr: - URL: http://[prowlarr-ip]:9696 - [ ] Check indexer status - [ ] Add SABnzbd: - URL: http://[sab-ip]:8080 - [ ] Monitor queue status ### Database Monitors - [ ] MariaDB: - Type: MySQL/MariaDB - Connection string - [ ] Test query - [ ] PostgreSQL: - Type: PostgreSQL - Connection string - [ ] Test query ### Docker Container Monitors - [ ] Type: Docker Container - [ ] Monitor container health status - [ ] Check restart counts ### Notification Channels - [ ] Configure Discord: - Webhook URL - Custom message format - [ ] Test notification - [ ] Configure Email: - SMTP settings - Recipients - [ ] Test email - [ ] Configure Pushover: - User key - App token - [ ] Test push ### Status Page - [ ] Create public status page - [ ] Group monitors by category - [ ] Custom domain (via NPM) - [ ] Custom branding ### Testing - [ ] Simulate service failure - [ ] Verify notifications trigger - [ ] Check status page updates - [ ] Test from external network
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
tonym
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: tonym/NastyNAS#40
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?