Overview

The Monitoring area gives you a real-time view of your servers and the gateway tunnels that connect them — plus the alerting to tell you when something needs attention.

Two views: across your fleet vs. one server

Monitoring is split across two surfaces, and it helps to know which one you’re looking at:

• The fleet view is a cross-server overview, part of the Contact System app. It rolls up connectivity, health, and active alerts for every server you operate, so you can spot problems at a glance and drill into any one server. See the Fleet dashboard.
• The per-server monitoring pages cover a single Mirth server — the one you’re signed into. This is where you create alert rules, configure notification destinations, and explore that server’s metric history. The pages below describe these per-server tools.

A server’s metric history and alert configuration are stored locally on the server itself, and optionally synced up so the fleet view can summarize them.

What you can do here

• See connectivity and health across all your servers in the fleet dashboard.
• Track per-channel throughput and server vitals (heap, threads, load) for a server.
• Define alert rules that fire on thresholds, rate-of-change, absence, or state change.
• Route alerts to destinations — webhook, email, or messaging.
• Review historical events and analytics.

Navigation

Area	Scope	Purpose
Fleet dashboard	All servers	Cross-server connectivity and health (in the Contact System app).
Alert rules	One server	Create and manage alerting conditions.
Destinations	One server	Where alerts are delivered.
Analytics & events	One server	Trends and the historical event timeline.

A note on patient data

Monitoring is built to be PHI-safe: it collects numeric metrics and operational state, never message content. You can monitor freely without worrying about exposing protected health information.