Battery Level Monitoring

🔋 Battery-Level Monitoring

GermainUX RUM JS can monitor the battery status reported by supported browsers and create an event when:

Battery events provide additional context for understanding the experience of mobile, field, and laptop users.

✨ Benefits

Battery-Level Monitoring can help teams:

⚙️ Preconfigured monitoring

Battery monitoring is preconfigured in GermainUX RUM JS with a default low-battery threshold of 15%.

When supported by the browser, GermainUX can create events for:

No customization is required when the default threshold meets the organization’s requirements.

📋 Collected information

Depending on browser support and the event type, a battery event can include:

Battery data can be analyzed alongside user activity, errors, performance, and business-process events.

🔧 Customize the battery threshold

Customize the threshold only when the default value of 15% does not meet the monitoring requirement.

The following example creates a low-battery event when the battery level reaches or falls below 30%:

const settings = germainApm.getDefaultSettings();

// Create a battery-level event at or below 30%.
settings.plugins.battery.levelThreshold = 30;

germainApm.start(settings);

The value represents a percentage and must be configured between 0 and 100.

📊 Analysis

Battery events can be analyzed using measures such as:

Results can be segmented by pivots such as:

Battery events can also be reviewed within the associated user session and correlated with other available GermainUX insights.

🔔 Notifications

A low-battery or charging-status event can be used to:

A Watch notifies users about a battery insight already detected by GermainUX; it does not create a new insight.

🌍 Browser support and limitations

Battery monitoring depends on the browser’s Battery Status API.

The documented GermainUX capability is available in supported versions of Chromium-based browsers, including:

Browser vendors can restrict or discontinue access to battery information for privacy and fingerprinting protection. Always validate availability with the browser versions used by the monitored population.

Battery-Level Monitoring does not:

Treat battery status as contextual evidence rather than proof of application battery usage.

🔒 Privacy

Battery information can contribute to device fingerprinting when combined with other attributes.

Before enabling production monitoring:

✅ Validation

Follow these validation steps:

1. Open the monitored application in a supported browser on a battery-powered device.

2. Confirm that GermainUX RUM JS is running.

3. Temporarily configure a threshold above the device’s current battery level.

4. Reload the monitored application or reproduce the relevant battery event.

5. Confirm that a battery-level fact appears in GermainUX.

6. Connect or disconnect the charger.

7. Confirm that a charging-status-change event appears.

8. Verify the application, session, browser, and battery properties.

9. Restore the intended production threshold.

🔍 Troubleshooting

If battery events are not collected:

1. Confirm that the application uses GermainUX RUM JS.

2. Verify that the browser supports and exposes the Battery Status API.

3. Test on a physical battery-powered device.

4. Confirm that battery monitoring is enabled in the UX Monitoring Profile.

5. Verify that the configured threshold is valid.

6. Check the browser console for initialization errors.

7. Confirm that the browser can send telemetry to GermainUX.

8. Review sampling, consent, and privacy settings.

9. Check whether browser or enterprise-security policies restrict battery access.

📦 Deployment and configuration

ℹ️ Get Help

The Germain Team can help you set this up. Contact GermainUX Support.