Internal Documentation
Status
  • πŸ‘‹Welcome
    • πŸ—‚οΈWhat is this?
    • πŸ•Quick Start
    • πŸ’ΈBilling
  • πŸ—ƒοΈExternal Links
    • πŸ—„οΈPublic Documentation
    • πŸ“‹Private GitHub
    • πŸ“‹Public GitHub
    • πŸ—»NetData
    • πŸ“ŠTrello
    • πŸ•°οΈService Monitoring
  • πŸ“Policies
    • Authentication, Access and Accounts
    • Issue and Project Tracking
    • Creation and Managment of Servers or Services
    • Monitoring and Alerting
    • External Access to Systems
    • Management of Documentation
  • πŸ“‹Processes
    • ❔Deploy new Container Stack
    • Limit Bandwidth to Container
    • ❔Create new Virtual Machine
    • Disaster Recovery
    • Port Forwarding or Tunneling a Service
    • Crowdsec Modules
    • Internal IP Range Change
    • SSH Keys
    • Increase Disk on VM
    • Add Wireguard Client
    • ❔New Domain
    • DNS Management
  • πŸ—ΊοΈService Overviews
    • Websites
    • Portainer and GitOps
      • All Compose Stacks
    • Content Creation
      • Davinci Resolve Server
    • Plex Suite
      • Monitarr
      • Declutarr
      • Tdarr
      • Maintainerr
      • Dashdot
      • Overseerr
      • Bazarr
      • Wizarr
      • Plex
      • Tautulli
      • MovieMatch
      • Prowlarr
      • Radarr
      • Sonarr
      • Lidarr
      • FlareSolverr
      • qBittorrent
      • SabNZBD
      • Huntarr
    • Pterodactyl
    • Home Automation & Physical Security
      • Google Assistant
      • Tuya Cloud
      • Home Assistant
    • Infrastructure
      • ❔Cloudflare
      • NextDNS
      • UniFi
      • Synology NAS
      • Proxmox VE
      • Vultr
      • ❔CyberPower PowerPanel & UPS
    • Maintenance & Monitoring
      • AutoHeal
      • Beszel
      • Proxmox Backup Server
      • Duplicati
      • Google Drive Sync
      • Ansible
      • UptimeKuma
      • NetbootXYZ
    • Security
      • Bitwarden
      • Google OpenID Auth
      • Wazuh
      • CrowdSec
    • Remote Access
      • Cloudflare Zero Trust
      • ❔UniFi - Wireguard
      • Kasm
    • Other Adhoc Apps
      • ISponsorBlockTV
      • Homebox
      • ❔Hosted Discord Bots
      • LibreChat
      • Imgur
      • Morphos
      • Zapier
      • EpicGames Free Games
      • GitBook
      • Trello
      • StirlingPDF
      • ❔MeTube
    • ❔OpenAI
  • πŸ–₯️Physical Hardware
    • Macaroni
    • Fettuccine
    • Linguine
    • UniFi
  • ‼️Troubleshooting
    • An Introduction...
    • UptimeKuma alerts
    • Portainer
    • Pterodactyl
  • πŸ“–-- Administration --
    • πŸ“ŽGitbook Templates
      • Guide - Root Page
      • Guide - New Docker App
      • Hardware Overview
      • App Overview - Externally Hosted
      • App Overview - Container
      • Miniguide - Compose
      • App Overview - Hosted Discord Bot
Powered by GitBook
On this page
  • Pushover
  • UptimeKuma
  • Status Pages
  • Maintenance Periods
  • Email Notifications
  • NetData

Was this helpful?

  1. Policies

Monitoring and Alerting

We are currently using Pushover and UptimeKuma for server & service monitoring

Pushover

Alert Type

Notification

-2

No notification, displays in app

-1

No notification, displays in app

0

Notification during active hours only

1

Always notify

2

Always notify

If the service can integrate with Pushover;

  • Configure 2 notifiers if possible

    • Low priority

    • High priority (if only 1 possible, configure high priority)

  • Set up alerts for notifiers

    • Low priority can be used for

      • Services that will cause minimal impact

      • Low urgency alerts

      • Alerts that are good to have, but may be common

    • High priority can be used for

      • Services with public impact

      • Services that will cause an outage (eg DNS)

      • Outages

Some services can integrate with Pushover via other methods, such as the text message API or SMTP. These should only be used for priority 0 and above.

Why?

This allows alerts to be sent to my mobile phone and categorizes them. Depending on the time, some alerts will be silent and others will make sound


UptimeKuma

All UptimeKuma monitors should be set as below. This reduces spam to Pushover as well as resource load

Setting

Value

Time in Seconds

120

Retry count before error

3

Pushover

Priority based on impact

Status Pages

We currently have 3 status pages,

Maintenance Periods

Maintenance periods should be set before the potential service outage, with the relevant monitors selected

Consistent maintenance periods, like the 4:30PM daily update schedule, can be scheduled and automated in Kuma

Why?

Consistent approach to notifications and monitoring

Display the right data on the right status page


Email Notifications

Email notifications should be set up using SMTP, please refer to the below generic config

SMTP_HOST=smtp.gmail.com
SMTP_PORT=587
EMAIL_SENDER_ADDRESS=                          #Refer to the list of emails below
EMAIL_SENDER_NAME=
SMTP_SECURE=starttls
SMTP_USERNAME=lattemediadottv@gmail.com        #generic gmail account for SMTP
SMTP_PASSWORD=                                 #creds in BW
LatteMedia Services
XFGN Services
AGG Services

noreply@lattemedia.tv

noreply@xfgn.dev

noreply@agamersgrind.com

Why?

This allows us to email users from a single account. Per the email address, it also notifies them that they will not recieve a response.


NetData

Netdata is a distributed real-time, health monitoring platform for systems, hardware, containers & applications, collecting metrics.

Netdata alerts are sent to Pushover

Why?

This is to allow us to keep ahead of issues in the network and resolve them before they affect any public facing services

PreviousCreation and Managment of Servers or ServicesNextExternal Access to Systems

Last updated 1 year ago

Was this helpful?

πŸ“
LatteMedia
A Gamers Grind
XFGN