Feature Flags
Learn how to attach custom feature flag data to Sentry error events.
Currently in Beta
Feature flag change tracking and feature flag evaluation tracking is currently in open beta.
This integration only works inside a browser environment.
The Feature Flags integration allows you to manually track feature flag evaluations through an API. These evaluations are held in memory and sent to Sentry when an error occurs. At the moment, we only support boolean flag evaluations.
Import names: Sentry.featureFlagsIntegration and type Sentry.FeatureFlagsIntegration
Install your platform's Sentry SDK from npm.
Copied
import * as Sentry from '@sentry/<your browser platform, e.g. react>';
Sentry.init({
dsn: "https://examplePublicKey@o0.ingest.sentry.io/0",
integrations: [Sentry.featureFlagsIntegration()]
});
The integration is tested by calling the addFeatureFlag method before capturing an exception.
Copied
import * as Sentry from '@sentry/browser';
const flagsIntegration = Sentry.getClient()?.getIntegrationByName<Sentry.FeatureFlagsIntegration>('FeatureFlags');
if (flagsIntegration) {
flagsIntegration.addFeatureFlag('hello', false);
} else {
// check your configure step
}
Sentry.captureException(Exception('broke'));
Visit the Sentry website and confirm that your error event has recorded the feature flag "hello" and its value "false".
Next Steps
- Track feature flag evaluations in other parts of your codebase. If needed, you can set up evaluation tracking for more than one SDK. Read the docs to learn more.
- Set up your change tracking webhook. In order to take full advantage of the feature flag capabilities Sentry offers there is an additional setup step needed. Your feature flag provider needs to notify Sentry when a feature flag definition has changed. A Sentry webhook URL can be registered with your provider. Learn how.
Help improve this content
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").