jaeger_detect_anomalies
Detect latency and error-rate anomalies in a service by comparing recent traces against a historical baseline to identify performance issues.
Instructions
Detect latency and error-rate anomalies for a service by comparing recent behavior to historical baseline.
Fetches traces from a historical baseline window and a recent observation window, computes per-operation statistics for both, then identifies statistically significant deviations that may indicate performance issues or reliability problems.
Examples:
- Use when: "Are there any new performance issues in order-service?"
→ service='order-service' (uses default 60-minute baseline, 5-minute current).
- Use when: "Be more sensitive to subtle changes"
→ set sensitivity=1.5 (lower threshold).
- Use when: "Check for issues over the last 24 hours against previous week"
→ baseline_duration_minutes=10080, current_duration_minutes=1440.
- Don't use when: You want to compare two specific time periods
(use jaeger_compare_windows instead).
- Don't use when: You want full span detail for a single trace
(use jaeger_get_trace instead).
Returns: AnomalyDetectionOutput with flagged operations and severity scores.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes | Service name to detect anomalies for. | |
| sensitivity | No | Anomaly sensitivity threshold (1.0-5.0, default 2.0). Lower = more sensitive. | |
| current_duration_minutes | No | Current observation window in minutes (1-60, default 5). | |
| baseline_duration_minutes | No | Historical baseline duration in minutes (5-1440, default 60). |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes | ||
| anomalies | Yes | ||
| current_end | Yes | ||
| sensitivity | Yes | ||
| baseline_end | Yes | ||
| current_start | Yes | ||
| baseline_start | Yes | ||
| total_anomalies | Yes | ||
| latency_anomalies | Yes | ||
| error_rate_anomalies | Yes |