This article explains the possible statuses of the Blumira Agent and the host, and how those statuses impact logging to Blumira.
Blumira Agent's daily bandwidth usage is significantly smaller (about four times less) compared to server-hosted sensors. An agent that has been offline for some time but still collecting logs will immediately begin sending those backlogged logs to Blumira upon reconnecting. However, no more than 60 MB of data is queued while the agent is offline, so the amount of logs and the time it takes to send those pending logs to Blumira depends on the resources available to the device and how much activity occurred on the device while the agent was offline.
The table below describes what logging activity occurs for a remote device in various statuses:
| Agent status | Host isolation status | Cloud logging | Network connection | Logging behavior |
|
Online |
Not isolated |
Constant |
Full |
The agent has full connectivity and transmission of logs to Blumira is constant. |
|
Online |
Isolated |
Constant |
None |
The device cannot be used for any network activity, but the agent on the device can communicate exclusively with Blumira to continuously send logs. The agent is online, so it can also release the device from isolation. |
|
🚫 Offline |
Not isolated |
Backlogging with limit |
None |
When the agent is offline but the device is not asleep, the agent continues to collect logs locally (up to 60 MB) and will transmit the backlogged data to Blumira when it is online again. |
| 🚫 Offline | Isolated | Backlogging with limit | None |