observability-and-instrumentation

Use Timber and plant a DebugTree only when BuildConfig.DEBUG is true, with a custom release tree routing warnings and errors to Crashlytics. Timber.d calls are then stripped in release while Timber.e still reports errors.

Initialize TalkerFlutter.init with safeMode set to !kDebugMode before runApp, attach TalkerDioLogger to your Dio instance, and set Bloc.observer to TalkerBlocObserver. Forward errors to Crashlytics or Sentry in FlutterError.onError and PlatformDispatcher.instance.onError.

Custom keys are key-value pairs attached to a recorded exception, such as payment provider or retry count, making reports searchable. Breadcrumbs are sequential log messages recorded via Crashlytics log() that reconstruct the user's path leading up to the error.

No. Logging full request or response bodies can leak tokens, passwords, and other PII into Crashlytics or analytics servers, violating privacy policies. Log only metadata like status codes and never Authorization headers.

Analytics tools aggregate events by parameter values, so unbounded values like user IDs or timestamps explode cardinality and break reporting. Group values into discrete categories such as network type or retry count ranges.

Do not use it for local CPU or memory profiling during development, which belongs to profiler tools and Macrobenchmark, or for Play Store launch checklists and rollout rules. It covers runtime telemetry, not local benchmarking or release management.