Flutter SDK data collection

​

Event types

​

Automatically collected context

• Application information: service, version, env, and application_id
• Device information: device model, operating system and version, screen size
• Session information: session.id, sampled by sessionSamplingRate
• Connection information: network type (when available)
• User information: usr.id / usr.name / usr.email set through setUserInfo

​

Manual instrumentation

final rum = DatadogSdk.instance.rum;

// Manually manage views
rum?.startView('checkout', 'Checkout');
rum?.stopView('checkout');

// Manually record an action
rum?.addAction(RumActionType.tap, 'pay_button');

// Manually report an error
rum?.addErrorInfo('payment failed', RumErrorSource.source);

// Attach a global attribute (written to all subsequent events)
rum?.addAttribute('tenant', 'acme');

​

Sampling and control

​

Data masking

DatadogRumConfiguration(
  applicationId: '<APPLICATION_ID>',
  resourceEventMapper: (event) {
    // Return null to drop the event, or return it after modification
    return event;
  },
);

​

Upload behavior

• The SDK batches and caches at the native layer, uploading in batches by batchSize and uploadFrequency
• When the network is unavailable, events are persisted locally and retried after recovery
• The upload endpoint defaults to the site’s endpoint (FlashcatSite.cn → browser.flashcat.cloud); on-premises deployments can override it through customEndpoint