Overlock vs. Cloud Logging
State and context
What was happening on the device when it went wrong? What about on related devices?
With classic logging tools you have to piece together information about device state from logs which could be spread over hundreds or thousands of lines. And because these tools don’t make that data accessible or useful, most developers just don’t bother to add it.
Overlock gives developers a valuable tool for these situations: state updates, which let you keep track of anything from program variables, device modes, user settings and more. This gives you an immediate insight into what you might need to do to reproduce the issue and makes it much easier to identify what might have caused the problem.
When someone gets in touch to say their device isn’t working, what’s the first thing you do?
With cloud logging tools, only a developer can make any sense of the logs - and even then it’s hard to pick out the crucial information. Overlock, on the other hand, gives you a high-level overview of the events that have affected a device recently. For example, was it restarted recently? Or has it not been restarted for three years? Does the network keep dropping out, or was the firmware just updated? Are there any recorded issues or exceptions on the device?
This information is clearly presented and accessible to developers and support staff alike. It helps you understand quickly and clearly what’s been happening on the device and why it might be going wrong.
Bandwidth usage and storage costs
To effectively use a cloud logging tool, you have to send all logs from your devices to the cloud.
That’s wasteful. The majority of logs will never be looked at - and rightly so. They’re not useful if they don’t document errors, lifecycle events or the state of a device in the run-up to an error. But these tools don’t understand what’s useful and what isn’t, so you have no choice but to send up everything.
Overlock’s unique agent architecture keeps a rolling cache of logs and only sends them up to the cloud when there’s a problem, or when they’re specifically requested. This saves around 90% of data transfer and storage costs, crucial for devices with limited bandwidth available.