A client-side Android library to interact with Datadog.
See the dedicated Datadog Android Log Collection documentation to learn how to forward logs from your Android application to Datadog.
See the dedicated Datadog Android RUM Collection documentation to learn how to send RUM data from your Android application to Datadog.
If your existing codebase is using Timber, you can forward all those logs to Datadog automatically by using the dedicated library.
If you use Coil to load images in your application, take a look at Datadog's dedicated library.
If you use Fresco to load images in your application, take a look at Datadog's dedicated library.
If you use Glide to load images in your application, take a look at our dedicated library.
If you use Picasso, let it use your OkHttpClient, and you'll get RUM and APM information about network requests made by Picasso.
val picasso = Picasso.Builder(context)
.downloader(OkHttp3Downloader(okHttpClient))
// …
.build()
Picasso.setSingletonInstance(picasso)If you use Retrofit, let it use your OkHttpClient, and you'll get RUM and APM information about network requests made with Retrofit.
val retrofitClient = Retrofit.Builder()
.client(okHttpClient)
// …
.build()When you open your console in Datadog, navigate to the Logs section. In the search bar, type source:android. This filters your logs to only show the ones coming from mobile applications (Android and iOS).
When you open your console in Datadog, navigate to the Logs section. In the search bar, type source:android. This filters your logs to only show the ones coming from mobile applications (Android and iOS).
If you encounter any issue when using the Datadog SDK for Android, please take a look at the troubleshooting checklist, or at the existing issues.
Pull requests are welcome. First, open an issue to discuss what you would like to change. For more information, read the Contributing Guide.