Docs » Supported integrations in Splunk Observability Cloud » Instrument mobile and web applications for Splunk RUM » Instrument Android applications for Splunk RUM » Troubleshoot Android instrumentation for Splunk Observability Cloud

Troubleshoot Android instrumentation for Splunk Observability Cloud 🔗

When you instrument an Android application using the Splunk OpenTelemetry Instrumentation for Android and you don’t see your data in Splunk Observability Cloud, follow these troubleshooting steps.

Steps for troubleshooting Android OpenTelemetry issues 🔗

The following steps can help you troubleshoot Android RUM agent issues:

  1. Check that desugaring is activated for your app

  2. Activate debug logging

Check that desugaring is activated for your app 🔗

If you see runtime errors related to Java 8 interfaces and classes, make sure you have activated coreLibraryDesugaring. See Activate desugaring in your application.

Activate debug logging 🔗

Activating debug logging can help you troubleshoot Android instrumentation issues.

To activate logging, add the enableDebug() method to SplunkRum.builder(). For example:

SplunkRum.builder()
   .setApplicationName("<name_of_app>")
   .setRealm("<realm>"")
   .setRumAccessToken("<rumAccessToken>")
   .enableDebug()
   .build(this);
}

Note

Activate debug logging only when needed. Debug mode requires more resources.

Background tasks are introducing noise in the data 🔗

Background tasks might introduce unwanted or noisy data to your instrumented application. To deactivate instrumentation for a background task, pass the application ID of the task to the disableBackgroundTaskReporting() method. For example:

public class SampleApplication extends Application {

   @Override
   public void onCreate() {
      super.onCreate();

      SplunkRum.builder()

         // Other Settings
         // ...

         // Turn off instrumentation of background processes
         .disableBackgroundTaskReporting(BuildConfig.<id_of_application>)
         .build(this);
      }
   }

Error: Handling gzip compressed request EOF 🔗

When including the Splunk RUM agent to your application, Android Studio might show an EOFException related to gzip compression.

Splunk RUM uses gzip encoding to reduce network bandwidth consumption. The Network Inspector in Android Studio attempts to read the body of the HTTP request, breaking the gzip encoding. This results in Splunk Observability Cloud ingest endpoints returning error 400.

As a workaround, deactivate Splunk RUM while profiling your app, or deactivate gzip compression when profiling your app.

If you are a Splunk Observability Cloud customer and are not able to see your data in Splunk Observability Cloud, you can get help in the following ways.

Available to Splunk Observability Cloud customers

Available to prospective customers and free trial users

  • Ask a question and get answers through community support at Splunk Answers .

  • Join the Splunk #observability user group Slack channel to communicate with customers, partners, and Splunk employees worldwide. To join, see Chat groups in the Get Started with Splunk Community manual.

To learn about even more support options, see Splunk Customer Success .