Detect points where the underlying data distribution changes. Canary implements this by computing the energy gradient: the rate of change of the prediction error over a sliding window. This endpoint is fully compatible with the Azure Anomaly Detector changepoint API. BothDocumentation Index
Fetch the complete documentation index at: https://docs.canaryedge.com/llms.txt
Use this file to discover all available pages before exploring further.
/anomalydetector/v1.0/timeseries/changepoint/detect and /anomalydetector/v1.1/timeseries/changepoint/detect are supported.
Array of data points, each with
timestamp (ISO 8601) and value (number). Minimum 12 points, maximum 8640 points. Timestamps must be sorted ascending with no duplicates.Time interval between points. One of:
yearly, monthly, weekly, daily, hourly, minutely, secondly, microsecond, none.Multiplier for granularity.
Seasonality period. Set to
0 for auto-detection.Maximum fraction of points flagged. Must be between 0 and 0.5 (exclusive).
Detection sensitivity (0-99).
Detected seasonality period.
Whether each point is a changepoint.
Confidence score from 0.0 to 1.0 for each point.
How Changepoint Detection Works
- The energy gradient is computed:
gradient[i] = mean(energies[i:i+k]) - mean(energies[i-k:i])wherek = max(period, 5). - A point is a changepoint if its gradient exceeds the 95th percentile of all gradients.
- The gradient must be a local maximum (greater than or equal to both neighbors).
- Minimum spacing between changepoints equals the detected period.