Console logs

This page documents the Bugsee Android SDK 7.0.0. For the previous major version, see the 6.x Logging page.

Automatic Logcat capture

Bugsee automatically captures android.util.Log.* calls made by your app and includes them in reports. Capture is enabled by default and is controlled by the CaptureLogs option (together with CaptureLogsLevel and CaptureLogsUseAllSources). See the Configuration page for the full option reference.

No special setup is required — as long as the Bugsee Gradle plugin's log instrumentation is enabled (it is by default), every android.util.Log.* call is rewritten to flow through the capture pipeline before delegating to the original method.

Pushing log entries manually

Bugsee.log(...) pushes a message into the capture buffer without printing it to Logcat. Useful when you want information to appear in the Bugsee report but not in your app's Logcat stream.

Java

import com.bugsee.library.Bugsee;
import com.bugsee.library.contracts.options.LogLevel;

// Default level (Info)
Bugsee.log("User tapped Checkout");

// Explicit level
Bugsee.log("Payment succeeded", LogLevel.Info);
Bugsee.log("Retrying request", LogLevel.Warning);
Bugsee.log("Upload failed", LogLevel.Error);

Kotlin

import com.bugsee.library.Bugsee
import com.bugsee.library.contracts.options.LogLevel

// Default level (Info)
Bugsee.log("User tapped Checkout")

// Explicit level
Bugsee.log("Payment succeeded", LogLevel.Info)
Bugsee.log("Retrying request", LogLevel.Warning)
Bugsee.log("Upload failed", LogLevel.Error)

Both overloads are no-ops if message is null or the SDK is not launched. If level is null, the SDK defaults to LogLevel.Info.

LogLevel values

Value
LogLevel.Error
LogLevel.Warning
LogLevel.Info
LogLevel.Debug
LogLevel.Verbose

Filtering log entries

7.0.0 unifies filtering around the generic EventFilter<LogEvent> interface. Its single filter(log, callback) method hands you the event and a Callback1 to invoke with the result: call callback.run(log) to keep the (possibly mutated) entry, or callback.run(null) to drop it entirely.

Java

import com.bugsee.library.Bugsee;
import com.bugsee.library.contracts.exchange.LogEvent;

Bugsee.setLogEventFilter((log, callback) -> {
    String message = log.getMessage();

    // Drop noisy entries entirely
    if (message != null && message.startsWith("[heartbeat]")) {
        callback.run(null);
        return;
    }

    // Redact sensitive tokens
    if (message != null && message.contains("token=")) {
        log.setMessage(message.replaceAll("token=[^&\\s]+", "token=<redacted>"));
    }

    callback.run(log);
});

Kotlin

import com.bugsee.library.Bugsee

Bugsee.setLogEventFilter { log, callback ->
    val message = log.message

    when {
        // Drop noisy entries entirely
        message?.startsWith("[heartbeat]") == true -> callback.run(null)
        // Redact sensitive tokens
        else -> {
            if (message?.contains("token=") == true) {
                log.message = message.replace(Regex("token=[^&\\s]+"), "token=<redacted>")
            }
            callback.run(log)
        }
    }
}

LogEvent exposes getMessage() / setMessage(String) and getLevel() / setLevel(LogLevel); mutate in place, then pass the event to callback.run(...) (or callback.run(null) to drop it).

setLogFilter(EventFilter<LogEvent>) is a deprecated alias for setLogEventFilter(...); both resolve to the same registration.

Privacy

For redaction of sensitive information captured in logs, refer to the Privacy → Logs page.