DatadogFlutter class

Constructors

DatadogFlutter()

Properties

hashCode → int

The hash code for this object.

no setter, inherited

runtimeType → Type

A representation of the runtime type of the object.

no setter, inherited

Methods

noSuchMethod(Invocation invocation) → dynamic

Invoked when a nonexistent method or property is accessed.

inherited

toString() → String

A string representation of this object.

inherited

Operators

operator ==(Object other) → bool

The equality operator.

inherited

Static Methods

initialize({required String clientToken, required String serviceName, required TrackingConsent trackingConsent, String? androidRumApplicationId, String environment = 'development', String flavorName = '', String? iosRumApplicationId, bool useEUEndpoints = false, String? webRumApplicationId}) → Future<void>

By default, events will not be sent to Datadog. This is a requirement of the SDK to maintain GDPR compliance. To maintain backwards functionality, use trackingConsent: TrackingConsent.granted. For more, see TrackingConsent.

setUserInfo({String? id, String? email, Map<String, dynamic> extraInfo = const <String, dynamic>{}, String? name}) → Future<void>

Sets current user information. Those will be added to logs, traces and RUM events automatically.

updateTrackingConsent(TrackingConsent trackingConsent) → Future<void>

The SDK changes its behavior according to the new trackingConsent value. For example, if the current tracking consent is .pending: and it is changed to .granted, the SDK will send all current and future data to Datadog; if changed to .notGranted, the SDK will wipe all current data and will not collect any future data.