systemd service that runs on your devices, handling the deployment lifecycle of configurations. Visit the Miru Agent documentation for more information.
Properties
string
A human-readable display name that can contain most characters, such as spaces, special characters, and punctuation. Must contain between 1 and 48 characters.Examples:
Robot 11, ArcticBlaze, Warehouse Roverdatetime
The timestamp of when the device last connected to Miru’s servers.Examples:
2026-05-25T12:00:00Zdatetime
The timestamp of when the device last disconnected from Miru’s servers.Examples:
2026-05-25T12:00:00Zstring
The version of the Miru Agent running on the device.The agent version exists only if the device has a status of
online or offline. If the device is inactive or activating, the agent version is null.Examples: v0.6.0Release
The release to which the device’s current deployment belongs.If the device is
inactive or activating, the current release id is null. If the device is online or offline, the current release may still be null if the device has no deployed config instances.Examples: rls_123Group
The group to which the device belongs. If the device’s group is not set, the group id is
null.Examples: grp_123Status
Devices leverage several states to track their registration and connectivity with the Miru control plane.
Devices begin in the inactive state. During the Miru Agent install process, devices briefly enter the activating state before transitioning to online.
Once the Miru Agent has been provisioned on a device, the device remains online or offline for the remainder of its existence—devices don’t transition back to inactive or activating.
The only exception to this is when a device is reprovisioned. During reprovisioning, devices briefly enter the activating state before transitioning back to online.
A device enters the archived state when it is archived, and
leaves it when it is restored.
To view a device’s status, hover over its name on the Devices page.
