Skip to main content

EmberCORE Overview

EmberCORE is the single web console for operating your fleet, covering every edge site, device, app, network policy, and alert in one place. It runs in any modern browser, with no client to install.

EmberCORE is an operations console rather than a charting tool. It is a curated set of tools, each opening a focused workspace for a real task: deploying an app, wiring up a site's zero-trust network, checking storage health, acknowledging an alert. For custom time-series charting, EmberNet ships Grafana in the App Store.

Accessing EmberCORE​

Sign-in is handled by your identity provider through single sign-on, so there is no separate EmberCORE password. Your identity determines which view you land on and what you can see and do. See SSO Integration.

Role-based views​

EmberCORE renders a different view for each role. You don't switch views to change your permissions; you're placed in the right one, scoped to the right data, when you sign in.

ViewForScope
Global CommandPlatform staffEvery tenant, cross-fleet. The only place aggregate, cross-tenant data is ever shown
AdminTenant administratorsTheir own tenant: users, sites, devices, apps, network, storage, alerts
EngineerTenant engineersTheir own tenant: day-to-day monitoring and diagnostics, read-mostly configuration
OperatorFloor operatorsTheir own tenant: live status, device health, and alert acknowledgement

Those are the views. The full list of tenant roles (Admin, Manager, Engineer, Plant Supervisor, Maintenance, Operator, Auditor, and Viewer) and what each one does is on Multi-Tenancy.

Tenant isolation is enforced by the platform, not by hiding buttons: an Admin, Engineer, or Operator only ever sees their own tenant's data. See Multi-Tenancy.

What each role sees on Home​

Home is the page the console opens on, and it is built from what your role may do. These are the Home views for six of the roles below Global Command.

Home for an Admin: counters, the Needs attention panel, and the Live plant panel, with the full navigation down the left

An Admin sees the whole console: Home, App Store, Workspaces, Fleet, Network, Sites, Plant, Data, Monitoring, and Access.

Home for an Engineer: the same counters and panels, with the navigation without Plant

An Engineer sees the same Home and the same plant values, and the navigation leaves out Plant.

Home for Maintenance: the counters, Needs attention, and Live plant, with a short navigation of Home, Workspaces, Network, Sites, Monitoring, and Access

Maintenance has a shorter list: Home, Workspaces, Network, Sites, Monitoring, and Access.

Home for a Viewer: the counters, Needs attention, Live plant, and the Nodes list, with a navigation of Home, Workspaces, Sites, and Monitoring

A Viewer reads: Home, Workspaces, Sites, and Monitoring, with the Nodes list on Home.

The Plant area for a Plant Supervisor, with the Operators and Metrics tabs and the roster of operators

A Plant Supervisor lands on Plant, which is the only area in their navigation: the operator roster and the plant's metrics.

The message an Operator sees instead of the console: your operator console is EmberEdge, which runs on your tester's screen

An Operator has no console. EmberCORE tells them their operator console is EmberEdge, which runs on the tester's screen, and that EmberCORE is for the people who manage the site.

The workspace​

Every view shares the same layout.

  • Client Switcher (Global Command only): pick a client to scope the whole console to one tenant, or leave it on All Clients for the aggregate, cross-fleet view. Selecting a client drills every tool and metric down to that tenant; "All" is the platform-wide view.
  • View Switcher: jump between the views your role permits.
  • Alerts bell: a live count of active alerts with a quick-look dropdown.

The three blocks​

The body of the console is three stacked blocks, top to bottom.

Metrics is a strip of live metric cards. The metrics shown follow the category you have selected, so picking Industrial Automation shows PLC drivers, broker tags, and industrial alerts, while Edge Infrastructure shows nodes, pods, and storage. You choose which metrics appear and how each is drawn. See Metrics & Monitoring.

Tools is the grid of EmberNet's own tool cards, filtered by the category carousel above it:

CategoryTools it surfaces
Zero Trust NetworkFlux Console: mesh identities, services, routers, and policies
Industrial AutomationAnvilMQ broker and its protocol drivers
App DeploymentApp Store, running-app management
Edge InfrastructureOps, Clusters, Cinder storage, Cloud Storage, edge provisioning
Device ManagementDevice Monitor, Network Devices: registry, configuration, and health
Monitoring & DiagnosticsSite Topology, Live Diagnostics, Alerts
SitesSite hierarchy: plants, buildings, zones, and assets
Compliance & ReportingAudit log, scheduled reports, activity timeline
PlatformSettings, documentation, manifest

Subscribed Tools holds the third-party products your tenant subscribes to, which today means Ignition and Ignition Edge. The block hides itself entirely when neither applies.

Cards can be dragged into the order you prefer, and both the arrangement and the category you last used are remembered between visits.

The toolset​

Every card opens a focused workspace. Tools Reference documents all of them: what each one is for, what you can do once it is open, and which roles see it.

The ones with guides of their own:

  • App Store: browse and deploy curated industrial apps to your edge nodes.
  • Device Monitor: the device registry and hardware health.
  • Network Devices: inventory, remote configuration, and topology for network equipment.
  • Flux Console: the zero-trust mesh, covering identities, services, edge routers, and policies.
  • AnvilMQ: the platform's MQTT broker.
  • Ops & Clusters: fleet and cluster operations.
  • Cinder: capacity, volume health, and backups.
  • Alerts: active alerts, history, and rules.

Multi-tenant operation​

Platform staff operate the whole fleet from Global Command. The Client Switcher in the header is the single control for scope:

  • All Clients shows the aggregate, cross-fleet picture: total nodes, alerts, and health across every tenant.
  • Selecting a client drills the entire console, every tool card, metric, and table, into that one tenant, as if you were their administrator.

Everyone else works entirely within their own tenant; there is no cross-tenant data to switch to.

Home​

The Home page with the tenant name, counters for nodes ready, active alarms, and tenants, and the Needs attention panel

EmberCORE: Home. Start where the console starts.

Home is the page the console opens on. It names your tenant and your role, then shows three counters: Nodes ready, Active alarms, and Tenants. The Needs attention panel lists any active alert or node that is not ready, and says "Nothing needs you right now" when there is none. Below them, Nodes lists your nodes with their status, CPU, and memory, and Recent activity shows the latest changes in your tenant, with Full record opening the audit log. The screenshot stops above those two lists, because the activity list names the people who made changes.

When the tenant has a plant source, a Live plant panel shows the plant's latest values, read from the tenant's own HotLoop as you, so what you see is what HotLoop lets your role read. A tenant that has no HotLoop but runs a Store TimescaleDB is read from that database instead, with a read-only login. A site that stops answering keeps its last reading on screen, marked with its age. Platform staff with no tenant picked see Plants, a table of every plant they may see, one row each, saying ok, stale, unreachable, error, or no source, with no numbers for a plant that did not answer.

The console by area​

The left menu groups the console into areas. Each has its own page, with screenshots of every tab:

  • Fleet: nodes, running apps, the App Store, and provisioning.
  • Network: the Flux mesh and the services on it.
  • Sites: plants, buildings, devices, and probes.
  • Plant: the operators who work on your plant's floor.
  • Data: Cinder volumes, cloud sync, and the AnvilMQ broker.
  • Monitoring: alerts, diagnostics, metrics, and reports.
  • EmberSecurity: alerts, PLC activity, blocked traffic, and box health.
  • Access: users and roles, billing, and Ignition access.
  • Workspaces: gateways, open sessions, and support.
  • Platform staff tools: the tabs only platform staff see.

Next steps​