datadog_flutter_plugin 2.4.0 copy "datadog_flutter_plugin: ^2.4.0" to clipboard
datadog_flutter_plugin: ^2.4.0 copied to clipboard

Flutter bindings and tools for utilizing Datadog Mobile SDks

Overview #

Datadog Real User Monitoring (RUM) enables you to visualize and analyze the real-time performance and user journeys of your Flutter application’s individual users.

Datadog RUM SDK versions < 1.4 support monitoring for Flutter 2.8+. Datadog RUM SDK versions >= 1.4 support monitoring for Flutter 3.0+.

For complete documentation, see the official Datadog documentation.

Current Datadog SDK Versions #

iOS SDK Android SDK Browser SDK
2.8.1 2.7.0 5.x.x

iOS #

Your iOS Podfile must have use_frameworks! (which is true by default in Flutter) and target iOS version >= 11.0.

Android #

On Android, your minSdkVersion must be >= 21, and if you are using Kotlin, it should be version >= 1.8.0.

Web #

On Web, add the following to your index.html under your head tag:

<script type="text/javascript" src=""></script> 
<script type="text/javascript" src=""></script> 

This loads the CDN-delivered Datadog Browser SDKs for Logs and RUM. The synchronous CDN-delivered version of the Datadog Browser SDK is the only version currently supported by the Flutter plugin.

Note that Datadog provides one CDN bundle per site. See the Browser SDK README for a list of all site URLs.

See Flutter Web Support for information on current support for Flutter Web

Setup #

Use the Datadog Flutter Plugin to set up Log Management or Real User Monitoring (RUM). The setup instructions may vary based on your decision to use Logs, RUM, or both, but most of the setup steps are consistent.

For instructions on how to set up the Datadog Flutter Plugin, see the official Datadog documentation.

Create configuration object #

Create a configuration object for each Datadog feature (such as Logs and RUM) with the following snippet. By not passing a configuration for a given feature, it is disabled.

// Determine the user's consent to be tracked
final trackingConsent = ...
final configuration = DatadogConfiguration(
  clientToken: '<CLIENT_TOKEN>',
  env: '<ENV_NAME>',
  site: DatadogSite.us1,
  nativeCrashReportEnabled: true,
  loggingConfiguration: DatadogLoggingConfiguration(),
  rumConfiguration: DatadogRumConfiguration(
    applicationId: '<RUM_APPLICATION_ID>',

For more information on available configuration options, see the DatadogConfiguration object documentation.

Initialize the library #

You can initialize RUM using one of two methods in the main.dart file.

  1. Use DatadogSdk.runApp, which automatically sets up error reporting.

    await DatadogSdk.runApp(configuration, () async {
      runApp(const MyApp());
  2. Alternatively, you can manually set up error tracking and resource tracking. Because DatadogSdk.runApp calls WidgetsFlutterBinding.ensureInitialized, if you are not using DatadogSdk.runApp, you need to call this method prior to calling DatadogSdk.instance.initialize.

final originalOnError = FlutterError.onError;
FlutterError.onError = (details) {
final platformOriginalOnError = PlatformDispatcher.instance.onError;
PlatformDispatcher.instance.onError = (e, st) {
    stackTrace: st,
  return platformOriginalOnError?.call(e, st) ?? false;
await DatadogSdk.instance.initialize(configuration);

runApp(const MyApp());

Send Logs #

After initializing Datadog with a DatadogLoggingConfiguration, you can create an instance of a DatadogLogger to send logs to Datadog.

final logger = DatadogSdk.instance.logs?.createLogger(
    remoteLogThreshold: LogLevel.warning,
logger?.debug("A debug message.");
logger?.info("Some relevant information?");
logger?.warn("An important warning…");
logger?.error("An error was met!");

You can name loggers or customize their service:

final secondLogger = DatadogSdk.instance.createLogger(
    service: 'my_app.additional_logger',
    name: 'Additional logger'
);'Info from my additional logger.');

Tags and attributes set on loggers are local to each logger.

Track RUM views #

The Datadog Flutter Plugin can automatically track named routes using the DatadogNavigationObserver on your MaterialApp.

  home: HomeScreen(),
  navigatorObservers: [

This works if you are using named routes or if you have supplied a name to the settings parameter of your PageRoute.

Alternately, you can use the DatadogRouteAwareMixin property in conjunction with the DatadogNavigationObserverProvider property to start and stop your RUM views automatically. With DatadogRouteAwareMixin, move any logic from initState to didPush.

Note that, by default, DatadogRouteAwareMixin uses the name of the widget as the name of the View. However, this does not work with obfuscated code as the name of the Widget class is lost during obfuscation. To keep the correct view name, override rumViewInfo:

To rename your views or supply custom paths, provide a viewInfoExtractor callback. This function can fall back to the default behavior of the observer by calling defaultViewInfoExtractor. For example:

RumViewInfo? infoExtractor(Route<dynamic> route) {
  var name =;
  if (name == 'my_named_route') {
    return RumViewInfo(
      name: 'MyDifferentName',
      attributes: {'extra_attribute': 'attribute_value'},

  return defaultViewInfoExtractor(route);

var observer = DatadogNavigationObserver(
  datadogSdk: DatadogSdk.instance,
  viewInfoExtractor: infoExtractor,
class _MyHomeScreenState extends State<MyHomeScreen>
    with RouteAware, DatadogRouteAwareMixin {

  RumViewInfo get rumViewInfo => RumViewInfo(name: 'MyHomeScreen');

Automatic Resource Tracking #

You can enable automatic tracking of resources and HTTP calls from your RUM views using the Datadog Tracking HTTP Client package. Add the package to your pubspec.yaml, and add the following to your initialization:

final configuration = DatadogConfiguration(
  // configuration
  firstPartyHosts: [''],

In order to enable Datadog Distributed Tracing, the DatadogConfiguration.firstPartyHosts property in your configuration object must be set to a domain that supports distributed tracing. You can also modify the sampling rate for Datadog distributed tracing by setting the traceSampleRate on your DatadogRumConfiguration.

Contributing #

Pull requests are welcome. First, open an issue to discuss what you would like to change.

For more information, read the Contributing guidelines.

License #

For more information, see Apache License, v2.0.