Monitoring SDK status

The client-side .NET SDK defines "data source status" as the status of the SDK's communication with LaunchDarkly to get feature flag data. If the streaming connection to LaunchDarkly is interrupted, or, in polling mode, if a polling request fails, the SDK might not be able to receive flag updates. The data source status will indicate this, providing an overall state such as "valid" or "interrupted" and information about the last error that occurred, if any.

To check the data source status:

Alternatively, you can register an event handler that will receive a new status value whenever the status changes.

Here is an example:

To learn more, read IDataSourceStatusProvider.

The Android SDK exposes some of its internal status through APIs to let your application monitor it. This allows the application to determine how recently the internal flag cache has been updated with the most recent values, as well as diagnosing potential reasons for the flag cache to be out of date.

The SDK has seven connectivity states dependent on its configuration, application foreground state, network connectivity, and calls explicitly setting the client offline or online.

This table describes the states:

The SDK also internally stores a timestamp of the most recent successful and failed connections to LaunchDarkly, as well as information related to the most recent failed connection. The LDClient method getConnectionInformation() returns a structure allowing retrieval of these fields.

LDFailure is a LaunchDarklyException with an associated FailureType. It may include a .cause(), which is propagated from an underlying exception associated with the update's failure. The cause itself should be considered unstable because it is dependent on internal implementation, though the mechanism to retrieve it will be maintained.

The failure types are summarized below:

If matching on the FailureType, use a default case to handle any future cases provided. The UNEXPECTED_RESPONSE_CODE case indicates that you can cast the LDFailure to a LDInvalidResponseCodeFailure for more information. This more specific failure includes a response code and whether the failure is considered retryable.

Here is an example:

A callback-based interface is also provided to allow notifying the application when the ConnectionMode changes, as well as whenever the LDFailure in ConnectionStatus changes. The application must provide a class instance implementing LDStatusListener to the SDK client instance method registerStatusListener to register the listeners with the SDK.

Here is a brief example:

The C++ (client-side) SDK exposes some of its internal status to let your application monitor it.

The SDK has several data source states dependent on its configuration, network connectivity, and calls explicitly setting the client offline or online.

This table describes the states:

The SDK stores a timestamp of when the data source state most recently changed. It also stores information about the last error that the data source encountered, if any.

This table describes the possible errors:

Here's how to monitor the data source state:

If you are working in C, there are a few more steps:

1. Define a callback to receive the data source status change:

   C++ SDK v3.0 (C binding), define callback

2. Assign the callback by creating a listener connection:

   C++ SDK v3.0 (C binding), create listener connection

3. Ensure the connection is freed when you are done with it:

   C++ SDK v3.0 (C binding), free connection

Finally, if you are working in C but are still using the older v2.x SDK, the data source status interface is not available. To wait indefinitely, use a callback:

To learn more, read DataSourceStatus.

By default, the client requests feature flag values only once per user. This happens once at startup time, and then each time you call identify(). You can also use a persistent connection to receive flag updates whenever they occur.

Enable this behavior by setting streaming to true in the client options or calling client.setStreaming(true). LaunchDarkly pushes new values to the SDK, which updates the current feature flag state in the background, ensuring that variation() always returns the latest values.

If you want to be notified when a flag has changed, you can use an event listener for a specific flag.

Here's how:

Alternatively, you can listen for all feature flag changes.

Here's how:

Subscribing to change events automatically turns on streaming mode as well, unless you have explicitly set streaming to false.

The Flutter SDK exposes some of its internal status through APIs to let your application monitor it. This allows the application to determine how recently the internal flag cache has been updated with the most recent values, as well as diagnose potential reasons for the flag cache to be out of date.

The SDK stores a timestamp of the most recent successful and failed connections to LaunchDarkly, as well as information related to the most recent failed connection. The dataSourceStatus returns a structure that lets you retrieve these fields.

To learn more about the connection status fields, read DataSourceStatus.

The iOS SDK exposes some of its internal status through the Connection Status API to let your application monitor it. This allows the application to determine how recently the internal flag cache has been updated with the most recent values, as well as diagnosing potential reasons for the flag cache to be out of date.

The SDK has four connectivity states dependent on its configuration, application foreground state, network connectivity, and calls explicitly setting the client offline or online.

This table describes the states:

The SDK also stores a timestamp of the most recent successful and failed connections to LaunchDarkly, as well as information related to the most recent failed connection. lastKnownFlagValidity is nil if either no connection has ever been made successfully or if the SDK has an active streaming connection. It has a value if it is in polling mode and at least one poll has completed successfully, or if it is in streaming mode whenever the streaming connection closes. The LDClient.shared method getConnectionInformation() returns a structure that lets you retrieve these fields.

The ConnectionInformation class can return four different values for lastFailureReason.

This table describes the values:

You can listen to changes in ConnectionInformation.ConnectionMode in a similar manner to flag observers.

Here is an example of the API:

Starting with version 10 of the React Native SDK, the SDK uses an emitter pattern for errors. You can subscribe to error and change events.

Here's how:

To learn more, read on and off.

You can use Roku's observeField method on your node to respond to changes in status.

Here's how:

To check the data source status:

Alternatively, you can register an event handler that will receive a new status value whenever the status changes.

Here is an example:

The C++ (server-side) SDK exposes some of its internal status to let your application monitor it.

The SDK has several data source states dependent on its configuration, network connectivity, and calls explicitly setting the client offline or online.

This table describes the states:

The SDK stores a timestamp of when the data source state most recently changed. It also stores information about the last error that the data source encountered, if any.

This table describes the possible errors:

Here's how to monitor the data source state:

If you are working in C, there are a few more steps:

1. Define a callback to receive the data source status change:

   C++ SDK v3.0 (C binding), define callback

2. Assign the callback by creating a listener connection:

   C++ SDK v3.0 (C binding), create listener connection

3. Ensure the connection is freed when you are done with it:

   C++ SDK v3.0 (C binding), free connection

To learn more, read DataSourceStatus() in Client.

To check the data source status:

Alternatively, you can monitor a channel that provides a new status value whenever the status changes:

To learn more, read GetDataSourceStatusProvider and GetDataStoreStatusProvider.

To check the data source status:

Alternatively, you can register an event listener that receives a new status value whenever the status changes:

To learn more, read DataSourceStatusProvider and DataStoreStatusProvider.

To check the data source status:

Alternatively, you can register an event listener that receives a new status value whenever the status changes:

To learn more, read DataSourceStatusProvider and DataStoreStatusProvider.

To check the data source status:

Alternatively, you can register an event listener that receives a new status value whenever the status changes:

To learn more, read DataSource::StatusProvider and DataStore::StatusProvider.