pub struct Report {Show 13 fields
pub request_count: usize,
pub p50_latency_us: Option<u64>,
pub p95_latency_us: Option<u64>,
pub p99_latency_us: Option<u64>,
pub p95_queue_share_permille: Option<u64>,
pub p95_service_share_permille: Option<u64>,
pub inflight_trend: Option<InflightTrend>,
pub warnings: Vec<String>,
pub evidence_quality: EvidenceQuality,
pub primary_suspect: Suspect,
pub secondary_suspects: Vec<Suspect>,
pub route_breakdowns: Vec<RouteBreakdown>,
pub temporal_segments: Vec<TemporalSegment>,
}Expand description
Rule-based triage report for one completed Run snapshot.
The report ranks evidence-backed suspects and suggests next checks. It does not prove root cause and should be used as triage guidance.
Fields§
§request_count: usizeNumber of request events considered in analysis.
p50_latency_us: Option<u64>p50 request latency in microseconds.
p95_latency_us: Option<u64>p95 request latency in microseconds.
p99_latency_us: Option<u64>p99 request latency in microseconds.
p95 queue-time share per request in permille (0..=1000).
p95 non-queue service-time share per request in permille (0..=1000).
inflight_trend: Option<InflightTrend>Dominant in-flight trend signal, when at least one in-flight gauge has samples.
warnings: Vec<String>Non-fatal analysis warnings (for example, capture truncation notices).
evidence_quality: EvidenceQualityStructured evidence coverage and interpretation quality summary.
primary_suspect: SuspectHighest-ranked suspect from this run.
secondary_suspects: Vec<Suspect>Lower-ranked suspects retained for follow-up triage.
route_breakdowns: Vec<RouteBreakdown>Supporting per-route triage summaries when route-level signal adds value.
temporal_segments: Vec<TemporalSegment>Supporting early/late temporal triage summaries when within-run shifts add value.