> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application/sa-6.md). # SA 6 Support Application 6 is the BlueFletch telemetry and monitoring agent for managed Android devices. It runs as a persistent background service, collecting device health, system activity, and operational data for troubleshooting, analytics, and fleet visibility. SA6 also includes an on-device tools to inspect device state, review recent events, confirm configuration, and run diagnostics. ### What it collects * **Device health data:** battery, temperature, storage, memory, and the state of Wi-Fi, cellular, Bluetooth, and GPS. * **System and lifecycle events:** screen state changes, power connect and disconnect, app installs and removals, reboots, and low-battery warnings. * **Operational data:** information that helps teams validate device readiness, diagnose issues, and understand usage patterns. ### How it works * Runs as a persistent background service on managed devices. * Sends collected data to BlueFletch services for monitoring and analysis. * Buffers events locally when the device is offline. * Retries delivery automatically when connectivity returns. ### On-device tools Support Application 6 also includes an on-device interface for support workflows. Teams can inspect current device state, review recent events, confirm configuration, and access diagnostic tools directly on the device. #### Click here to explore what’s new in Support Application 6. {% hint style="info" %} For Support Application 5 documentation, click here. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application/sa-6.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.