Back to OP5 Monitor FAQ

Internal documentation only

This page has been marked as draft.

How to Handle UI Failover in OP5 Master-Peer Setup

Related to: Copied

High availability and UI access in an OP5 cluster with multiple masters.

Problem: Copied

When Master01 is inactive, users accessing the UI via FQDN pointing only to Master01 see all hosts and services reporting 0/0, even though Master02 is active. Current setup treats Master01 as the primary UI access point and Master02 as a peer with additional integrations (Grafana, Kafka).

Possible cause(s): Copied

• FQDN resolves only to Master01.
• OP5 does not support automatic UI failover between masters.
• Secondary master may differ in dashboards, user permissions, and configuration; mirroring the full UI is not supported.

Possible solution(s): Copied

• Designate one master as Primary Master for all configuration changes, API requests, and normal UI access.
• The secondary master can continue running checks and host limited dashboards to monitor continuity.
• Users should not access both masters simultaneously for full UI operations, as this can cause incompatible changes.
• Optional: Set up a simple secondary dashboard on Master02 for basic UI functionality during Primary Master downtime.
• Ensure all peers can run as standalone masters if needed, but accept that full UI mirroring is unsupported.