Skip to main content

Precomputed Metrics

Importing Precomputed Metrics​

Importing Precomputing Metrics from your Data Warehouse​

Statsig integrates natively with cloud data warehouses such as Snowflake, BigQuery, Redshift to ingest any of your existing metrics for computing experiment results. See Data Warehouse Ingestion to get started.

Debugging Precomputed Metrics​

Statsig creates a metric detail page for all precomputed metrics that you import from your data warehouse. These metric detail pages take a few hours to generate post-import or ingestion. The fastest way to start seeing and debugging your precomputed metrics is via the Metrics Logstream in the Metrics Catalog tab within Metrics.

Screen Shot 2022-07-13 at 4 22 46 PM

The Metrics Stream will surface all ingested, precomputed metrics in real-time as they are ingested, enabling you to check metric name, metric value, unit identifier, ID type, and ingestion date.

Tip

Customers can trip up on ensuring that their precomputed metrics have the right ID type. Pay extra attention to this column!

Statsig also offers the ability to include test metrics, tagged with isTest. You can toggle these on/ off while debugging in the Metrics Stream. The isTest flag is currently available for precomputed metrics ingested via Statsig's APIs. Support for this flag via our integrations with Snowflake, BigQuery, and Redshift is coming soon.

To mark a batch of metrics as test metrics the isTest parameter needs to be set to true as part of the data for the request as seen below.

curl \
  “https://events.statsigapi.net/v1/log_custom_metric” \
  --header “statsig-api-key: <YOUR-SDK-KEY>” \
  --header “Content-Type: application/json” \
  --request POST \
  --data “{"isTest": true, “metrics": [{"user_id": "1237", "metric_name": "test_metric", "id_type": "user_id", "metric_value": 90}, {"user_id": "4568", "metric_name": "ratio", "id_type": "stable_id", "numerator": 3, "denominator": 15}]}”

292825183_585502089655173_8192569048240569580_n

Finally, the Metrics Stream only appears if you're actively ingesting precomputed metrics. If you're not seeing it appear at the bottom of your Metrics Catalog, Statsig likely is not receiving your precomputed metrics due to a connection issue or an invalid schema.