Glossary
Key terms and concepts used across the monitoring platform
Terms
Agent / Hub
A monitoring service deployed at a customer site. Runs headless (no UI) and communicates with the cloud via gRPC. Also referred to as a "hub" in the UI.
CDC
"Cyviz Device Controller" — the internal project namespace for the monitoring engine and agent codebase.
Control Plane
Cloud service that manages agent lifecycle — registration, configuration push, command dispatch, and health monitoring.
Easy Server
The core backend platform providing configuration management, user/permission system, and multi-tenant infrastructure. Shared with other Cyviz products.
Effective Configuration
The runtime configuration for a device instance, computed by merging template defaults with instance-specific overrides.
FIFO Outbox
The agent's local queue for telemetry. Events are persisted to disk and sent in strict order, guaranteeing delivery even during connectivity loss.
Instance
A specific physical device, configured by overriding a template with site-specific values (IP address, room assignment, etc.).
IPC (Inter-Process Communication)
The communication channel between the agent core and plugin host processes. Uses named pipes (Windows) or Unix domain sockets (Linux).
Monitoring Server
Cloud service responsible for telemetry analytics, alert evaluation, and historical data storage. Exposes a GraphQL API for dashboards.
MTTA / MTTR
Mean Time to Acknowledge / Mean Time to Resolve — key metrics for measuring alert response performance.
Namespace
Hierarchical path organizing resources within a tenant (e.g., England.London.HQ.Floor1.Boardroom).
Plugin Host
An isolated OS process that runs a device-type plugin. Communicates with the agent core via IPC.
Property
An observable value on a device (e.g., power state, input source, temperature). Properties can be polled or event-driven.
Template
A reusable device configuration defining properties, traits, and communication settings. Instances inherit from templates.
Tenant
An organization in the platform. All data, users, and configurations are scoped to a tenant.
Trait
A built-in device capability (e.g., power-controllable, input-switchable). Traits have locked-down configuration defined by the template.
Telemetry
Data sent from agents to the cloud — device state changes, property updates, heartbeats, and alert triggers.