Skip to main content
To send Statsig events to Chronosphere Observability Platform, configure an outgoing webhook in Statsig and provide its signing secret to Observability Platform for signature verification. Observability Platform ingests only statsig::config_change events and silently ignores other Statsig event types, such as statsig::gate_exposure and statsig::experiment_exposure.

​
Configure a Statsig outgoing webhook

To configure Statsig to send events to Observability Platform:
  1. In Statsig, go to Project Settings and click the Integrations tab.
  2. Find Generic Webhook and click Enable.
  3. In the URL field, enter: 
    https://TENANT.chronosphere.io/api/v1/data/events/receiver/statsig
    Replace TENANT with your organization name from your Observability Platform tenant.
  4. Click Event Filtering to configure which event types Statsig sends. Observability Platform ingests only config change events and silently ignores exposure events if sent. Select only Config Changes and clear Exposures.
  5. Save the webhook configuration.
  6. From the Generic Webhook integration card, copy the Signing Secret. The secret is required to configure the integration in Observability Platform.

​
Configure the Statsig integration in Observability Platform

Contact Chronosphere Support to configure your Statsig integration and provide the signing secret you copied from Statsig.

​
Map Statsig events to Observability Platform events

After configuring the integration, Observability Platform automatically maps incoming config change events from Statsig to change events in Observability Platform. You can’t customize how the payload maps to change events in Observability Platform. To request modifications to the Statsig payload’s mapping, contact Chronosphere Support. The following table describes how Statsig event fields map to Observability Platform change events:
FieldValue
categoryfeature_flags
typeTYPE_ACTION
sourcestatsig
happened_atTIMESTAMP
titleNAME ACTION
Replace the following:
  • TYPE: The Statsig config type in lowercase, such as gate or experiment.
  • ACTION: The action that occurred, such as created or updated. Combined with TYPE, this produces values like gate_updated or experiment_created.
  • TIMESTAMP: The time the config change occurred, taken from the event’s timestamp field.
  • NAME: The name of the Statsig feature flag or experiment that changed.
Observability Platform also attaches the following labels to each event from the Statsig payload:
LabelValue
typeThe Statsig config type, such as Gate or Experiment.
nameThe name of the feature flag or experiment that changed.
actionThe action that occurred, such as updated or created.
descriptionThe description of the change, if provided by Statsig.