Q: What is the local backlog limit?
A: 1GB (1024MB)
Q: What happens when the backlog limit is reached?
A: Oldest data is removed until we’re below the local backlog limit
Q: When backlog exists, what order is the data uploaded?
A: The data is uploaded in order, from oldest to newest
Q: What is the maximum size of a payload sent to Red Canary?
A: The total size of 5000 discrete events
Q: What is the maximum time until a telemetry payload upload attempt occurs?
A: 5 minutes (endpoint telemetry is recorded continuously)
Q: What is the maximum time until a health payload upload attempt occurs?
A: 5 minutes (health is recorded every 30s)
Q: What determines when a payload upload attempt occurs?
A: Whichever occurs first, the maximum time duration of 5 minutes, or the maximum size of 5000 discrete events buffered in memory. This is not currently configurable.
Q: If network connectivity does not exist, what is the retry logic algorithm?
A: The first time a payload fails to offload, the agent enters offline mode. For each payload file ready to offload:
- The agent will first check if there’s internet connectivity.
- If there is internet connectivity, it will re-enter online mode and begin uploading again.
- If there is no internet connectivity, the agent will return prematurely from any attempt to offload.
The time between offload attempts is 100ms.
Retry is indefinite but only one payload attempt per 100ms interval. If you fail once with "offline mode" then it bails on attempting any other payloads.
Q: What compression is used for local storage?
Q: What compression is used when sending data to Red Canary?
Q: Do we support multi-CPU or multi-core?
A: Yes - the agent is multi-threaded by default. There is no option for single-threaded operation.