Android Remote Logging: Debug Production Apps Without USB

1. The Logcat Problem in Production

Android developers rely on Log.d(), Log.e(), and Logcat during development. But Logcat has a fundamental limitation: it only works when the device is connected via USB (or ADB over Wi-Fi on the same network).

The moment your app ships to the Play Store, you go blind. A user in Germany crashes at checkout on a Pixel 7, a user in Brazil gets an ANR on a Samsung Galaxy A14, and a user in Japan sees a blank screen after login — and you see nothing.

Remote logging solves this by transmitting log events over the network to a cloud dashboard — giving you Logcat-like visibility across your entire user base, in real time.

2. Local vs Remote Logging Compared

3. Setup: Add Logtrics to Your Android App

Logtrics integrates via a Gradle dependency. Add it to your build.gradle and initialize in your Application class.

Step 1 — Add the dependency

// app/build.gradle
dependencies {
    implementation 'io.logtrics:android-sdk:1.0.0'
}

Step 2 — Initialize in Application class (Kotlin)

import io.logtrics.android.Logtrics
import io.logtrics.android.LogtricsConfig

class MyApplication : Application() {

    override fun onCreate() {
        super.onCreate()

        Logtrics.init(
            context = this,
            config = LogtricsConfig(
                apiKey = "YOUR_API_KEY",
                appVersion = BuildConfig.VERSION_NAME,
                environment = if (BuildConfig.DEBUG) "development" else "production",
                enableCrashReporting = true,
                enableAnrDetection = true,
                minLogLevel = if (BuildConfig.DEBUG) LogLevel.DEBUG else LogLevel.WARN
            )
        )
    }
}

Step 3 — Register your Application class

<!-- AndroidManifest.xml -->
<application
    android:name=".MyApplication"
    ... >

That's all it takes. Every WARN and ERROR log — plus all crashes and ANRs — now flows to your Logtrics dashboard.

4. Log Levels: What to Log in Release Builds

The biggest mistake Android developers make is logging everything in production. This generates noise, wastes bandwidth, and makes important events hard to find. Use log levels deliberately:

// Use the Logtrics logger instead of Log.e()
val logger = Logtrics.getLogger("CheckoutActivity")

fun processPayment(amount: Double) {
    logger.info("Payment initiated", mapOf(
        "amount" to amount,
        "currency" to "USD",
        "screen" to "CheckoutActivity"
    ))

    try {
        // ... payment logic
    } catch (e: PaymentException) {
        logger.error("Payment failed", e, mapOf(
            "amount" to amount,
            "errorCode" to e.code,
            "gateway" to "stripe"
        ))
    }
}

5. Automatic Crash & ANR Capture

When enableCrashReporting = true, Logtrics installs a global Thread.UncaughtExceptionHandler that captures all unhandled exceptions before the system terminates the app. When enableAnrDetection = true, it monitors the main thread watchdog for ANR conditions.

Each crash report includes:

# Upload ProGuard mapping after release build
curl -X POST https://api.logtrics.io/v1/symbols/android \
  -H "Authorization: Bearer $LOGTRICS_API_KEY" \
  -F "mapping=@app/build/outputs/mapping/release/mapping.txt" \
  -F "appVersion=$VERSION_NAME" \
  -F "buildId=$BUILD_ID"

6. Structured Logging with Context

Plain string logs are hard to filter. Structured logs — with typed key-value pairs — let you query by any dimension in the dashboard.

// ❌ Hard to filter — just a string
Log.e("TAG", "API call failed after 3 retries for user 12345 on endpoint /orders")

// ✅ Filterable by userId, endpoint, retries
logger.error("API call failed", mapOf(
    "endpoint" to "/orders",
    "retries" to 3,
    "httpStatus" to 503,
    "latencyMs" to 4200,
    "userId" to currentUser.id
))

In the Logtrics dashboard, you can now filter for all users who hit a 503 on /orders with more than 2 retries — in seconds.

7. User & Session Correlation

Attach user identity to all log events so you can see exactly what a specific user experienced.

// After login
Logtrics.setUser(
    userId = user.id.toString(),
    email = user.email,
    attributes = mapOf(
        "plan" to user.plan,
        "region" to user.region,
        "appVersion" to BuildConfig.VERSION_NAME
    )
)

// Track screen navigation for session context
override fun onResume() {
    super.onResume()
    Logtrics.setScreen(this::class.simpleName ?: "Unknown")
}

// After logout — stop associating events with user
Logtrics.clearUser()

8. Best Practices for Android Logging

FAQ

Related Articles