Most device management platforms tell you whether a device is online or offline. That is a useful starting point, but it answers only the most basic question about device health. By the time a device shows as offline in a dashboard, a problem has already occurred. The device has already failed to serve a customer, process a transaction, or display the correct content.
Moki’s Application Environment Monitoring goes further. It provides real-time visibility into the data points that indicate how a device is performing before problems become failures, including network status, battery level, memory usage, and application performance. Understanding what each of these data points tells you and when they warrant action is the difference between proactive fleet management and reactive incident response.
What Application Environment Monitoring Covers
Application Environment Monitoring in Moki tracks five categories of device health data in real time for every enrolled device in the fleet.
Network status reflects the device’s current connectivity state, including whether it is connected to the expected Wi-Fi network, what the signal strength is, and how long the current connection has been active. This goes beyond the binary online or offline status that most dashboards provide.
Battery level shows the current charge percentage for each device and, over time, reveals patterns in battery behavior that indicate hardware health. A device that consistently drops to low battery despite being connected to power has a degraded battery. A device that reports low battery repeatedly at predictable times may have a power management issue rather than a hardware failure.
Memory usage indicates how much of the device’s available RAM is currently in use. Elevated memory usage often precedes app crashes and performance degradation. A device trending toward maximum memory utilization is a device that is likely to experience application instability in the near future.
Application performance data, particularly when surfaced through the Moki SDK integrated into the managed application, includes custom events and performance metrics that the application reports to the Moki platform. This allows organizations to monitor not just whether the app is running but whether it is running correctly, reaching expected performance benchmarks, and completing key workflows as intended.
Device location is available for fleets where GPS tracking is enabled, providing the physical location of each device which is particularly useful for handheld or mobile device categories in distribution and field service deployments.
Reading Network Status Data
Network status data is most actionable when it reveals patterns rather than isolated events. A device that briefly drops connectivity and reconnects is experiencing normal network behavior that does not require intervention. A device that drops connectivity repeatedly within a short window is signaling a network instability issue at the location or a device-level Wi-Fi problem that warrants investigation.
When reviewing network status across a fleet, the most important pattern to identify is simultaneous connectivity loss across multiple devices at the same location. If five devices at a specific site all lose connectivity within minutes of each other, the cause is almost certainly a network infrastructure issue at that location rather than individual device failures. This context changes the response: the call goes to the network or facilities team at that location rather than to individual device troubleshooting.
Network status data also helps distinguish device problems from network problems in single-device incidents. A device that shows degraded connectivity alongside reports of app performance issues is more likely experiencing a network-driven problem than an application bug. Routing the investigation correctly from the start reduces total resolution time significantly.
Reading Battery Level Data
Battery level data serves two distinct operational purposes depending on the device type.
For devices on continuous power like mounted kiosks and POS terminals, a device showing low battery despite being connected to power is signaling a hardware problem. Either the charging cable or adapter has failed, the device’s charging port is damaged, or the battery itself has degraded to the point where it no longer holds a charge effectively. Any of these conditions will result in the device powering off unexpectedly unless addressed.
For handheld devices that operate on battery between charging cycles, battery level data provides the operational visibility needed to prevent devices from dying during active use. Alert thresholds configured in Moki can notify the team or the device operator when battery reaches a level that requires charging before the next operational period.
The most actionable battery insight comes from trend analysis rather than point-in-time readings. A device whose battery regularly depletes faster than comparable devices in the same use case is a device that needs hardware attention before it fails in the field. Moki’s device health history makes these trends visible without requiring manual tracking.
Reading Memory Usage Data
Memory usage data is the leading indicator that most organizations are least familiar with interpreting but that provides some of the most actionable advance warning of device instability.
Modern mobile applications consume significant memory, and devices running complex kiosk or POS applications over extended periods often experience memory accumulation that is not fully released between sessions. A device that starts its operational day at 40 percent memory utilization and ends it at 85 percent is trending toward the threshold where the OS will begin forcibly terminating background processes, which manifests as application instability and eventually crashes.
The appropriate response to elevated memory trends varies by device and application. For devices showing consistent memory growth over the operational day, a scheduled overnight reboot through Moki’s automated reboot capability resets memory state and prevents the accumulation from reaching critical levels. For devices where memory reaches concerning levels faster than expected, the application may have a memory leak that should be reported to the application developer.
Alert thresholds configured in Moki for memory utilization provide advance warning before a device reaches the instability threshold, allowing a proactive reboot rather than a reactive response to an application crash.
Using the Moki SDK for Application-Level Monitoring
The device-level monitoring Moki provides natively covers network, battery, memory, and connectivity. For organizations that want visibility into application-specific performance, the Moki SDK extends monitoring into the application layer.
When the Moki SDK is integrated into the managed application, the application can report custom events and performance metrics to the Moki platform. These custom events might include transaction completion rates, session length data, specific workflow completion or failure events, or any other application-specific condition the development team defines. The events appear in the Moki dashboard alongside device-level health data, giving operations teams a unified view of both the device and the application’s behavior.
For POS environments where transaction throughput is the key performance metric, SDK-based monitoring can surface declining transaction rates before they are noticed through revenue reports. For kiosk deployments where session completion is the goal, SDK monitoring can identify abandonment patterns or workflow failures that device-level monitoring alone would not surface.
Building a Monitoring Review Cadence
Application Environment Monitoring data is most valuable when it is reviewed on a defined cadence rather than only checked reactively when an alert fires. A brief daily review of the Moki dashboard covering battery levels, memory trends, and connectivity status for the fleet surfaces patterns that individual alerts do not capture.
Weekly review of device health trends across groups identifies devices showing deteriorating patterns before they trigger critical alerts. A device whose battery trend, memory trend, and connectivity reliability are all slowly declining is a device that is heading toward failure, even if no individual alert threshold has been crossed yet.
The combination of real-time alerts for immediate issues and periodic trend review for emerging patterns gives the operations team both the reactivity to respond to failures quickly and the foresight to prevent failures before they occur.
Schedule a Moki demo to see Application Environment Monitoring in action across a sample fleet, or start a free trial to begin monitoring your own devices with Moki’s real-time health tracking. Moki’s support team can help configure alert thresholds and monitoring settings appropriate to your specific device types and operational requirements.