Option to write experiments and results back to a SQL data source

[jdorn]

Add an option to persist experiments and results back to a SQL data source automatically.

New data source settings

• sync_results (boolean, default false)
• table_prefix (can include a dot to write to another schema in postgres/redshift e.g. growthbook.)

New cronjob:

• Gather all the data from MongoDB
• Connect to data source
• Run DELETE TABLE IF EXISTS... queries
• Run CREATE TABLE ... queries
• Run INSERT INTO ... queries

Proposed schema:

• metrics
  • metric_id
  • name
  • type
• metrics_tags
  • metric_id
  • tag
• experiments
  • experiment_id
  • name
  • tracking_key
  • project
  • owner
  • hypothesis
  • num_variations
  • status (draft, running, stopped)
  • archived (boolean)
  • result (win, lose, dnf, inconclusive)
  • winner
  • created_at
  • started_at
  • ended_at
  • synced_at
  • latest_phase_id
• experiments_tags
  • experiment_id
  • tag
• experiments_metrics
  • experiment_id
  • metric_id
  • type (goal or guardrail)
• phases
  • phase_id
  • experiment_id
  • type (ramp, main, or holdout)
  • coverage
  • traffic_split (e.g. 50/50 or 40/40/20)
  • status (finished, running)
  • started_at
  • ended_at
• results
  • phase_id
  • metric_id
  • variation
  • users
  • count
  • mean
  • stddev
  • conversion_rate
  • percent_improvement
  • risk_of_choosing
  • chance_to_beat_control

[itsgrimetime]

I know this has been around for a while now, but just wanted to toss a +1 here, my team would love to have this

[jdorn]

Now that we have Data Pipeline mode, we plan to focus on this soon