Skip to main content

Metrics & Monitoring

The dashboard keeps the numbers that matter for what you're doing right now in front of you at all times, through the context-metrics strip, a row of live metric cards that sits above the tool grid and changes with the category you're working in.

This is operational, at-a-glance monitoring: "are my nodes ready, is anything alerting, how full is storage." For deep historical analysis and custom charting, EmberNet ships Grafana in the App Store. See Custom dashboards below.

The context-metrics strip

The strip shows a set of live cards, refreshed continuously. Which cards appear follows the category you've selected in the tool carousel:

CategoryWhat the strip shows
AllA situational overview: devices, running workloads, storage volumes, system status, network up/down, active alerts
Zero Trust NetworkMesh peers online, Flux services and identities online, edge routers, network alerts
Industrial AutomationPLC drivers up, broker tag count and throughput, Ignition gateway status, OT devices
App DeploymentFleet bundles and clusters ready, reconciled services, App Store catalog size, running services
Edge InfrastructureNodes ready, running pods, scheduling pressure, storage used, volumes, healthy deployments
Device ManagementTotal and offline devices, device alerts, endpoints online
Monitoring & DiagnosticsCritical and warning alerts, alerts in the last 24h, probes
SitesSites online and alerting, site device and building counts
Compliance & ReportingAudit events in the last 24h, permission denials, scheduled reports
PlatformRunning workloads, AI service status, broker connections, active tenants, namespaces

Selecting a category swaps the whole strip to that category's metrics. Everything is scoped to your current tenant. For platform staff, that's whatever the Client Switcher is set to.

Customizing the strip

Each category's strip is yours to tailor.

Choosing metrics

Open the gear on the metrics strip to choose which metrics appear for the current category. Pick anywhere from 3 to 12 metrics from the full catalog; the layout expands to fit. Your selection is saved per category and remembered between visits, so each category can show exactly what you care about. Use Reset to defaults to return a category to its standard set.

Choosing how each metric is drawn

Every metric card can be drawn several ways, so pick the one that reads best for that value from the card's visualization picker:

VisualizationBest for
StatA single current value with a trend arrow
SparklineA value plus its recent shape over time
GaugeA bounded value against warning/critical thresholds (e.g. storage %)
DonutA part-of-whole reading
Status pillAn up/down or online/offline state
Heat stripSeverity or intensity at a glance
BarA small set of counts side by side

Your choice per card is remembered, and colors follow the value, so a metric with thresholds turns amber as it approaches warning and red at critical.

Metrics you can't see

Some metrics are platform-wide and only meaningful to platform staff. If your role can't see a given metric, its card shows a dash rather than another tenant's number. The strip never leaks data across tenants.

What's measured

The catalog spans the whole platform: edge infrastructure (nodes, pods, scheduling, deployments), storage (volumes, capacity, health), the zero-trust mesh (peers, services, identities, routers), industrial systems (PLC drivers, broker tags and throughput, Ignition), devices and endpoints, sites, alerts, and compliance (audit events, permission denials). Every value is read live from the platform and scoped to your tenant.

Custom dashboards and historical analysis

The context-metrics strip is for live operational awareness, not ad-hoc charting. When you need to build your own dashboards, whether that's historical trends, correlated signals, OEE, or custom queries, deploy Grafana from the App Store. Point it at the time-series data your apps write to:

This keeps the operations console fast and focused while giving you a full-featured analytics surface when you need one.

Next steps