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.
95 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.
In our case it came up while trying to keep an eye on a few monitoring devices.
These are machines our IT team keeps around specifically to observe how policies and commands behave over time. Instead of checking them manually, we added a scheduled automation that collects the Hexnode App Logs periodically so our admins can review them if something looks unusual.
We started using it during device rollout preparation.
Newly enrolled laptops stay in a temporary onboarding group before they move to their final device groups. While they are in that initial stage, the automation automatically collects the Hexnode App Logs. It gives our team a quick way to review what happened on the device side if something doesn’t behave as expected during the setup phase.
For us, the idea came from a few cases where devices behaved differently after they were reassigned between groups. To handle this, we use Dynamic Groups with specific criteria. When a device meets the criteria and ‘moves’ into that group, a time-based automation targeting that dynamic group triggers the Hexnode App Logs action. It helped us understand what was happening on the device during those transitions.
Interesting. Sounds like the common theme is collecting the logs closer to the moment when something changes on the device instead of running the action later during troubleshooting.
That’s a good direction for us to explore.
Don't have an account? Sign up
