Agent Orchestrator

What is it for?

Every device running ConHive needs one place to register it with the cloud, keep track of what's installed on it, and check whether it's actually healthy — that's what the Agent Orchestrator does. It manages device configuration, installs and configures modules, and keeps hardware health data like CPU, memory, and disk usage available so you can monitor a device without connecting to it directly. It also manages local user accounts, so you can still get into a device and recover access even if it's temporarily cut off from the cloud.

What makes it special?

• The foundation every other module runs on — modules on a device register themselves through it, so it's the one place that ties everything running on that device together.
• Install and manage modules remotely — set up, configure, and manage modules on a device without SSH access or manual scripting.
• Both live and historical health data — real-time hardware metrics (CPU, memory, disk) and historical status records, so you can catch problems as they happen or look back at what happened earlier.
• Keeps itself up to date — checks whether a newer version is available and can trigger an in-place update, so you don't need to log into each device by hand to keep it current.

The Agent Orchestrator is the central management module of every ConHive agent. It handles device configuration, module lifecycle, cloud connectivity, and user authentication — giving operators a single control surface for the hardware and software running on each device.

From registering a new agent with the ConHive cloud to installing and reconfiguring individual modules, all core agent operations are exposed through this module. Real-time hardware metrics and historical status data are also available here, so you can monitor device health without leaving the platform.

What you can do

• Inspect device information — retrieve the device record, its technical details, and current operational status.
• Monitor hardware health — read real-time CPU, memory, and disk usage and query historical status records.
• Manage module lifecycle — list all modules on a device, view their configuration and status, update settings, and execute module-specific commands.
• Update the agent — check the running build metadata, compare it against the latest CDN release, and trigger an in-place self-update or a container update.
• Stream agent events — open a bidirectional stream between the agent and the ConHive cloud to send and receive messages.

Typical use cases

• Register a ConHive agent with the cloud in a single step and manage its connection credentials from the central UI.
• Install, configure, and start individual modules on a device without SSH access or manual scripting.
• Monitor real-time hardware metrics such as CPU, memory, and disk usage across all managed agents.
• Manage local user accounts and recover access when a device is offline from the cloud.
• Update module settings and restart services remotely through the module lifecycle API.

Works with

Agent Orchestrator is the foundation layer every other module runs on top of. Module-specific modules such as Automation Manager, Command Management, and sensor modules register their capabilities through the module lifecycle API exposed here. Updates to module configuration and status are reflected across the agent in real time.

For the full gRPC/HTTP surface, see the API Reference.