Baseline computation strategies for data drift detection in Fiddler. Baseline types determine how reference data is defined and used for comparison with production model behavior. Fiddler supports static and rolling baselines, each serving different monitoring needs and use cases. Static Baselines:Documentation Index
Fetch the complete documentation index at: https://handbook.fiddler.ai/llms.txt
Use this file to discover all available pages before exploring further.
- Fixed reference point that doesn’t change over time
- Can be created from pre-production data (training/test sets) or production data
- Consistent comparison point for detecting absolute drift
- Ideal for compliance, audit requirements, and stable model environments
- Pre-production static baselines created via model.publish() with PRE_PRODUCTION environment
- Production static baselines defined using specific time ranges
- Dynamic sliding window that shifts with time
- Always maintains fixed time distance from current data (e.g., 4 weeks ago)
- Automatically adapts to gradual changes in data patterns
- Excellent for detecting sudden changes or anomalies in time-sensitive data
- Requires window_bin_size and offset_delta parameters
- Use STATIC for regulatory compliance, model validation, and stable environments
- Use ROLLING for seasonal patterns, evolving data, and operational monitoring
- Static pre-production baselines are recommended for most use cases
- Rolling baselines work best with sufficient historical production data