Configuring Monitoring for Mobile Applications with GermainUX

Configure Monitoring for Mobile

Configure GermainUX mobile monitoring to control application identity, user context, monitoring frequency, application and system events, transactions, device telemetry, privacy, KPIs, and alerts.

The available configuration depends on whether you are monitoring:

• A mobile web application

• A native Android application

• An Android device

📱 Native Android Application Configuration

Native Android application monitoring is configured through GermainAPMConfiguration.

⚙️ Configure Initialization

Initialize GermainUX from the Android application's Application class.

Create a GermainAPMConfiguration using the GermainUX ingestion endpoint and pass the configuration to:

GermainAPM.init()

For example, initialization can be used to configure application identity and enable or disable automatic monitoring capabilities.

The Mobile Library automatically configures standard monitoring behavior when no additional customization is required.

🏷️ Configure Application Identity

Configure the application name so mobile telemetry can be associated with the correct application in GermainUX.

Application identity should be consistent across environments and application versions.

Where appropriate, distinguish:

• Production

• Test

• Development

• Other application environments

⏱️ Configure Data Distribution Frequency

By default, the GermainUX Mobile Library sends collected monitoring data to the GermainUX Server every 30 seconds.

Crashes and application-closure events are sent sooner when possible.

The distribution interval can be customized using:

setDistributionFrequency()

Choose a frequency appropriate for the required detection speed, network usage, battery consumption, and mobile environment.

👤 Configure Application User Context

Associate monitored application activity with the appropriate user context when required.

User information can be configured during initialization or updated at runtime.

Supported context includes:

• User name

• Department — optional

• Role — optional

At runtime, user context can be updated using:

GermainAPM.setUser()

Only collect identifiable user information when required and approved by your organization's privacy and security policies.

💥 Configure Crash & Exception Monitoring

GermainUX can automatically monitor unhandled exceptions in the Android application.

Automatic exception monitoring can be enabled or disabled through GermainAPMConfiguration.

Handled exceptions and other application errors can also be reported where required.

Use crash and exception monitoring to analyze application stability by dimensions such as:

• Application version

• Android version

• Device model

• User population

• Transaction

• Device conditions

📲 Configure Application Event Monitoring

Monitor important application lifecycle events.

GermainUX can track application activity such as:

• Application launch

• Foreground/background transitions

• Application termination

• Other supported application events

Application-exit events can also be explicitly collected when required.

⚡ Configure System Event Monitoring

System event monitoring can be enabled or disabled through:

GermainAPMConfiguration.setSystemEventsMonitoring()

Available events depend on Android version and application permissions.

Examples include:

• Battery low / recovered

• Network changes

• Device boot

• Configuration changes

• Power connected / disconnected

• Power-saving state

• Storage conditions

• Time-zone changes

Do not enable or request access to sensitive event categories unless they are specifically required, supported, and approved.

🧩 Configure Fragment & View Monitoring

Configure monitoring for application fragments, screens, and views that are important to the user experience.

Use these measurements to understand:

• Application navigation

• Screen usage

• Fragment lifecycle

• View performance

• Time spent within application areas

Focus detailed monitoring on application areas relevant to critical workflows and user experience.

⏱️ Configure Transaction Monitoring

Define important Android application transactions that GermainUX should monitor.

Transactions can represent:

• Network requests

• Database operations

• Application operations

• User actions

• Business-critical processing

Use meaningful transaction names so the resulting telemetry is easy to analyze through dashboards, reports, SLAs, and alerts.

🔄 Configure Workflow Monitoring

Identify the mobile workflows that are critical to users or the business.

For example:

Login → Search → Select → Submit → Confirmation

Monitor workflow steps to identify:

• Performance degradation

• Overruns

• Drop-offs

• Errors

• Failed transactions

• Inefficient steps

📝 Configure Mobile Library Logging

The GermainUX Mobile Library enables Logcat output at INFO level by default when initialized.

Logging can be disabled through the configuration when it is not required.

For production deployments, review diagnostic logging to ensure unnecessary information is not written to the device log.

📲 Android Device Configuration

🏷️ Configure Device Context

Use consistent attributes to identify monitored devices and their operational purpose.

Useful dimensions can include:

• Environment

• Device group

• Device model

• Android version

• Business unit

• Region

• Application or workflow

• Ownership type

• Support group

Prefer a pseudonymous device identifier rather than personal or sensitive identifiers whenever possible.

🔋 Configure Device Monitoring Scope

Enable only the telemetry required for your use case.

Depending on the Android environment, this can include:

• Battery

• CPU-related measurements

• Memory

• Storage

• Network

• Application usage

• Process or service status

• Supported device events

Not every measurement is available on every Android device.

📊 Configure Application Usage Monitoring

When application usage information is required, enable Android Usage Access.

Permitted telemetry may include:

• Application foreground activity

• Usage duration

• Last-used time

• Usage frequency

Usage Access must be explicitly granted through Android settings or an approved managed-device process.

Restrict application-usage monitoring to approved devices, applications, and purposes.

🔒 Configure Data Exclusions & Anonymization

The GermainUX Mobile Library can exclude or anonymize collected fields using configuration rules.

Use exclusions for information that should not be collected.

Use anonymization when a value is operationally useful but its original identifiable value should not be retained.

Configuration can specify:

• Field

• Fact type

• Pattern

• Whether the original length is preserved

• Whether whitespace is preserved

• Whether the value is anonymized

Examples of information that may require protection include:

• User name

• Device identifier

• Application-specific personal information

Review all collection before production deployment.

🎯 Configure KPIs

Configure KPIs appropriate for the mobile application or device.

Examples for Android device monitoring include:

• Mobile Battery Level

• Mobile CPU Usage

• Mobile Disk Usage

• Mobile Memory Usage

• Mobile Process Memory

• Mobile Network Bandwidth

• Mobile Network Usage

• Mobile App Usage

• Mobile Service

• Mobile App Event

Not every KPI is available on every Android version or device.

📊 Configure Dashboards & Reports

Create dashboards and reports using the mobile telemetry relevant to your environment.

Examples include:

• Application performance

• Mobile crashes

• Transaction performance

• Workflow performance

• Application versions

• Android versions

• Device models

• Battery

• Memory

• Storage

• Network connectivity

• Application usage

• Device events

Segment application experience by device conditions to identify patterns.

For example:

Crashes → Device Model

Slow Transactions → Android Version

Failed Synchronization → Network Type

Application Interruption → Low Memory

🔔 Configure Alerts & SLAs

Configure alerts for actionable mobile conditions.

Examples include:

• Application crash

• Critical transaction failure

• Application performance degradation

• Device no longer reporting

• Sustained high resource usage

• Low available storage

• Repeated low-memory conditions

• Critical service unavailable

• Connectivity loss affecting an important workflow

Focus alerts on conditions requiring action rather than every mobile event.

🧪 Validate the Configuration

After changing mobile monitoring configuration, test representative application and device scenarios.

Validate:

• Application sessions

• Application identity

• User context where enabled

• Application events

• Crashes and exceptions

• Transactions

• Device telemetry

• Network changes

• Battery changes

• Privacy exclusions

• Anonymization

• KPIs

• Alerts

For Android devices, test representative Android versions and manufacturers because background behavior and available telemetry can vary significantly.

ℹ️ Advanced Configuration

The GermainUX Mobile Library supports additional configuration through GermainAPMConfiguration.

Use custom configuration when the default automatic monitoring behavior does not meet the requirements of the application.

When configuring device-level monitoring, remember that Android version, permissions, manufacturer restrictions, management profile, and background-execution rules can affect the telemetry available to GermainUX.

Please contact us for any help.