Fabric
The Fabric page is the single place to see and manage every remote component that makes up your deployment — Cores, Workers, Sensors, and Proxies — with live status. It has two tabs:
- Estate — a unified table of every component, where you register, edit, re-token, and retire Workers, Sensors, and Proxies.
- Topology — a live graph of how your Cores are meshed across regions and what is attached to each.
Which tabs and component types you see depends on your permissions and licensed features. With none available, the page reads “No Fabric surfaces available.”
Estate tab
One row per component, across all four types. A Live badge shows that status and counters stream in real time.
| Column | Notes |
|---|---|
| Name | Component name. Disabled workers carry a small disabled chip. |
| Type | Core, Worker, Sensor, or Proxy. |
| Status | pending, online, offline, or error (Cores may show no_telemetry until their first sample arrives). |
| Location | The location the component serves (Cores show their region). |
| Version | The software version the component reports. |
| Activity | Per type: Workers show active / max tasks; Sensors show packet drop %; Proxies show live sessions; Cores show connected clients. |
| Extra | Per type: Workers show a compatibility badge — green RDK compatible, red RDK incompatible, grey until the worker first reports; a worker marked incompatible is running a software version too far from the core’s and is not assigned any work until upgraded. Sensors show the applied ruleset with a drift warning when behind; Cores show leader · epoch. |
| Last Heartbeat | Most recent check-in, or Never. |
| Actions | View details / Edit / Regenerate Token / Delete. |
Controls: a component-type toggle (All / Cores / Workers / Sensors / Proxies) filters the table. A Create button registers a new Worker, Sensor, or Proxy.
Row actions:
- View details (all types, including Cores) — opens a read-only detail panel. For a Core it shows identity, leadership, connections and stream throughput; for a Worker its capacity and recent tasks; for a Sensor its traffic, engine, applied-vs-active ruleset, and stored alerts; for a Proxy its live sessions.
- Edit — change a component’s configuration (Cores are view-only).
- Regenerate Token — issue a new deployment token; the old one stops working immediately.
- Delete — retire a component.
The built-in default worker is system-managed: it can be edited (configuration only) but has no regenerable token and cannot be deleted.
For the per-type fields and step-by-step registration, see Workers, Sensors, and Proxies. Enabling a per-worker syslog collector is part of the Worker form.
Register a component
- On the Estate tab, click Create and choose Worker, Sensor, or Proxy.
- Fill the form (see the per-type page for its fields) and click Create.
- A token dialog appears — “This token will only be shown once.” Copy it and set it in the component’s configuration on its host. Regenerating a token later shows the same dialog.
Topology tab
The Topology tab draws your deployment as a live graph: regions grouping the meshed Cores, the Workers / Sensors / Proxies attached to each Core, and the connected clients. A strip of counters across the top summarizes the mesh — number of peers, routes, streams, and connected clients, plus live inbound and outbound message rates and a combined data rate.
Click any component node to open the same read-only detail panel as the Estate tab. The graph refreshes on a short interval; if it can’t be reached, a banner reports it and the last graph stays on screen.
Licensing
Creating or deploying remote Workers requires the Pro edition. Below it those actions stay visible but disabled, with a padlock explaining what is missing; the default worker remains system-managed and keeps working. Sensors and Proxies need their own add-on and follow its licensed capacity.
Permissions
- View the Estate and Topology:
app.fabric.read. - Register, edit, or re-token a Worker, Sensor, or Proxy:
app.fabric.write. - Delete a remote component registration:
app.fabric.delete.
The separate app.sensors.* and app.collector.* permissions govern IDS evidence/policy and collected-log evidence/policy respectively; they do not govern remote-component lifecycle.