Feature journal

Monitoring that moves like mercury.

The product is organized around the work a monitoring team actually does: define a signal, decide who should hear it, and keep enough history to understand what happened.

01 · Surface

Dashboards that explain the signal.

The dashboard keeps the primary health timeline visible without forcing every metric into the same visual weight. Uptime events can sit beside latency context, certificate dates, and a regional overview.

Every example chart on the marketing site is labeled Sample data because these illustrations are not live telemetry. In a deployed product, the endpoints you configure populate the actual monitoring timeline.

The interface is useful during deployments, incident review, and routine checks because the operator can move from symptom to scope without reconstructing the story from separate tools.

02 · Response

Alerts that carry their context.

A useful alert tells the responder what changed, which monitor noticed it, and where the event belongs. MeshMetrics groups those details with the chosen notification route.

Teams can select channels available on their plan and map different services to different response paths. Webhook support on higher plans can hand an event into an existing workflow instead of creating a manual copy step.

Outside an incident, the console stays quiet while the system records the event until a responder or reviewer needs to inspect the timeline again.

03 · History

Status and history without the archaeology.

Monitoring becomes more useful when an older incident can still be inspected. Retention differs by plan, giving smaller setups a focused window and larger coverage levels more room for comparison.

Status pages can present a service-level picture while the private console keeps deeper configuration and event context. That separation makes outward communication clearer without exposing internal structure.

Higher plans add multi-region probes and API access so selected signals can travel into operational systems you already use.

◌

Cloud-based, nothing to install

Checks run remotely, so standard web monitors do not require a local agent.

⌁

Any modern browser

The console is designed for current desktop and mobile browsers.

↗

API & webhooks

Selected plans can hand monitoring events into existing systems.

◍

Unlimited team notifications

Use available alert routes across the surfaces your team owns.