Anomaly Detection

Configure Anomaly Detection settings for Harden-Runner to identify unusual workflow behavior by comparing new runs against established baselines. These settings determine when anomaly detection becomes active across all workflows.

Configuration

You can enable anomaly detection based on workflow run count or elapsed time since the first run.

Run-Based Detection

Specify the minimum number of workflow runs required before anomaly detection is enabled. By default, this value is 100, but you can adjust it to suit your organization’s workflow frequency.

Example: Increase the threshold for high-frequency workflows to ensure more accurate baselines.

Time-Based Detection

Enable time-based anomaly detection to activate monitoring after a defined number of days since the first workflow run. This is useful for workflows that run infrequently but still need anomaly monitoring.

Example: If set to 30 days, detection begins 30 days after the first run, even if the workflow hasn’t reached the minimum run count.