Getnet DocsGetnet Docs

Record Telemetry

View as MarkdownView this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in PerplexityAsk questions about this page
Connect to CursorUse these docs in CursorConnect to VS CodeUse these docs in VS Code

This guide shows how to record your own telemetry entries in the SDK’s telemetry channel with Apolo.logger, keeping your diagnostic trail in the same place as the SDK’s own events.

How it works

Each call records a telemetry entry in the SDK channel — it does not write to Logcat. The calls are always safe: when the telemetry channel is not active in the current session, the call becomes a silent no-op. It never throws and never blocks the caller.

val Apolo.logger: ApoloLogger

interface ApoloLogger {
    fun d(tag: String, message: String)
    fun i(tag: String, message: String)
    fun w(tag: String, message: String)
    fun e(tag: String, message: String, throwable: Throwable? = null)
}

Only the e (error) level accepts an optional Throwable, since stack traces are meaningful for failures.

Record an entry

val apolo = ApoloSdk.getClient()

apolo.logger.i(tag = "Checkout", message = "starting a credit sale")

runCatching { /* ... */ }.onFailure { err ->
    apolo.logger.e(tag = "Checkout", message = "failed to prepare cart", throwable = err)
}

Best practices

  • Standardize tag by functional area of your application, to correlate with the SDK’s own telemetry.
  • Do not send sensitive data (card number, tax ID, credentials) through logger — telemetry is for diagnostic tracing, not transactional payload.

Next steps