Accessing Sensitivity Settings
Navigate to Settings → Anomaly Settings in the main navigation to configure how sensitive the detection system should be. Proper configuration helps balance catching real issues versus generating false positives.
Using Presets
For quick configuration, choose from our recommended presets based on your monitoring needs:
Sensitivity Presets
Quiet
Only critical issues. Best for stable environments.
Balanced
Good mix of coverage and noise. Recommended.
Sensitive
Catch subtle issues. Good for critical systems.
Custom
Fine-tune each setting individually.
Custom Configuration
Select the "Custom" preset to fine-tune individual settings for your specific needs.
Detection Thresholds
Detection Features
Time-of-Day Awareness
Use separate baselines for each hour of the day to account for normal daily usage patterns
Seasonality Detection
Detect and account for weekly patterns (weekday vs weekend)
Correlate Related Events
Group related anomalies that occur together to help identify root causes
Maintenance Window Awareness
Suppress anomaly alerts during scheduled maintenance windows
Understanding Standard Deviation (σ)
The sensitivity thresholds are measured in standard deviations (σ) from the learned baseline:
- 1.0σ: ~32% of normal values fall outside this range (very sensitive)
- 2.0σ: ~5% of normal values fall outside this range (balanced)
- 3.0σ: ~0.3% of normal values fall outside this range (quiet)
Best Practices
- Start with Balanced: Use the balanced preset initially, then adjust based on your experience
- Give it Time: Wait at least 2 weeks before adjusting settings to let the baseline stabilize
- Use Feedback: Marking anomalies as "Expected" helps the system learn your patterns
- Consider Criticality: Use lower thresholds for business-critical systems
- Review Regularly: Check your anomaly detection effectiveness monthly