We’ve been trying to make troubleshooting a bit faster in our environment.
Whenever something goes wrong with device management, the first thing our admins usually check is the Hexnode App Logs. They show what the Hexnode app was doing on the device when the issue occurred.
Recently we started experimenting with Automations, so the logs are collected automatically instead of someone triggering the action manually each time.
Curious to know how others are using this.
7 Views
We ended up exploring this after noticing how often our team was manually running that action.
During policy testing, devices sometimes behave slightly differently depending on the configuration sequence. So, we made a small change to our workflow. We set up an automation that collects the Hexnode App Logs whenever a device appears in our internal testing group. It uses a scheduled trigger (for example, daily or hourly) and targets the group. Devices are added to the group through Dynamic Group criteria. Once a device is in the group, the next scheduled run of the automation automatically collects the logs.
It’s been useful a few times when we were trying to understand why one test device behaved differently from others.
Don't have an account? Sign up
