Uptime Kuma - Configuration & Integrations#

What Was Established#

• Aruba Instant On Switch Monitoring: Confirmed that Aruba Instant On switches (specifically 1930 and 1960 series) support SNMP monitoring when configured via their local web interface, despite being primarily cloud-managed.
• Microsoft Teams Webhook Integration: Established the correct method for routing Uptime Kuma alerts to Microsoft Teams using Power Automate Workflows, noting the deprecation of legacy webhook.office.com connectors.

Key Decisions#

• SNMP over Ping: While basic ping monitoring is viable for switch reachability, SNMP is preferred for detailed port status and traffic metrics on supported Aruba models.
• Power Automate for Teams Alerts: Migrated away from deprecated Office 365 Connectors (webhook.office.com) to Power Automate Workflows to ensure long-term compatibility with Uptime Kuma webhooks.

Current Configuration#

Aruba Instant On Switches (1930/1960 Series)#

1. Network Setup: Assign a static IP address to the switch via the Aruba Instant On cloud portal or local interface.
2. SNMP Enablement:
   • Access the switch’s local web interface.
   • Navigate to SNMP settings (typically under “Switching” or “Management”).
   • Enable the SNMP agent.
   • Configure SNMPv2c (read-only community string) or SNMPv3 (username/password with optional encryption). Restrict access by IP for security.
   • Reboot the switch if required for settings to apply.
3. Uptime Kuma Monitor:
   • Add a new monitor of type SNMP.
   • Input the switch’s static IP, selected SNMP version, and credentials.
   • Customize OIDs if monitoring specific interface traffic or port status beyond system uptime.

Microsoft Teams Webhook Notifications#

• Notification Type: Webhook (Generic Webhook).
• Post URL: Power Automate Workflow endpoint URL (e.g., https://prod-05.westus.logic.azure.com/...).
• Content Type: application/json.
• Testing: Use the “Test” button in Uptime Kuma notification settings to verify connectivity. A 400 error typically indicates a malformed payload or deprecated connector URL.

Historical Notes#

• Legacy Connector Deprecation: Microsoft retired the old “Office 365 Connectors” on October 1, 2024. Any Uptime Kuma setups using webhook.office.com URLs will fail and require migration to Power Automate.
• SNMP Availability: Early guidance incorrectly stated Aruba Instant On switches lack SNMP support. It was later confirmed that local management interfaces on 1930/1960 models fully support SNMPv2c/v3.

Open Questions#

• Are there specific OIDs recommended for Aruba Instant On 1930/1960 switches to monitor port-level errors or traffic thresholds?
• Has the Uptime Kuma version been verified against known bugs with Power Automate JSON payloads?

Related Pages#

• Homelab Dashboard
• Network Infrastructure & VLANs
• Poe Switch Alerts

UniFi Express VPN & Network Management

AI-Driven Monitoring Pipeline#

What Was Established#

The monitoring pipeline is fully operational and running hourly. It collects rich structured data from four sources (Prometheus — 7 metrics, Uptime Kuma, UniFi, Synology), runs 4 parallel Ollama summarization calls, synthesises a final status report, and writes everything to Postgres. Hourly snapshots of raw UniFi and Prometheus data are stored in dedicated tables for delta computation. End-to-end runtime is ~13 minutes using gemma4:e4b CPU-only on the Pavilion — accepted as-is pending Mac Studio.