Following our announcement earlier this year, where we unveiled the new experimental
diagnostics features, today we are happy to announce that on-device diagnostics are now also open-source. In addition to helping us solicit feedback more effectively, one of the main reasons for doing this is to offer our users even more transparency in terms of what occurs on-device.
Based on the feedback we have received since launching the new diagnostics feature, we have expanded the scope of these tools and improved the interfaces for understanding the data you can collect. We have split out the checks we run on-device to their own dedicated view and added many additional diagnostics commands. These improvements to how the checks are displayed make it easier to understand and fix the issue on-device, due to the accompanying documentation.
These tools are meant to explore and preserve the state of a device at a given time (when the tool is run). We have found this diagnostics process useful for continued debugging after the device has been returned to proper working order, and since we have a snapshot of the state, we can continue investigating the issue without fear of losing data.
Get in touch
We are excited about the future of our diagnostics tooling and the way we see it evolving with the help of Fleet Owners. We’d love to know what you think, is there something we have missed, or something that would make your life easier? Suggest an improvement to our diagnostics today in the repository!