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

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.

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.

Next steps​