schema_version: 1 case_id: tail-latency-surge-during-incident-window ground_truth: root_cause: High-frequency point updates on t_merchant_online caused pessimistic lock contention and a single-TiKV hotspot during the incident window judge: semantic_strategy: undecided contract: checks: - id: time_window_match required: true description: Actual diagnosis time window matches one allowed case window. match: all_of rules: - source: trace_fact matcher: bool_true path: time_window_match - id: cluster_scope_match required: true description: Actual diagnosis cluster scope matches expected cluster id. match: all_of rules: - source: trace_fact matcher: bool_true path: cluster_scope_match workflow: checks: - id: architecture_context_loaded weight: 5 required: true description: Architecture context is loaded. match: all_of rules: - source: workflow_fact matcher: bool_true path: architecture_context_loaded - id: misdiagnosis_guardrails_loaded weight: 5 required: true description: Misdiagnosis guardrails are loaded. match: all_of rules: - source: workflow_fact matcher: bool_true path: misdiagnosis_guardrails_loaded - id: diagnosis_run_initialized weight: 5 required: true description: Diagnosis run is initialized. match: all_of rules: - source: workflow_fact matcher: bool_true path: diagnosis_run_initialized - id: evidence_collection_completed weight: 10 required: true description: Evidence collection completes. match: all_of rules: - source: workflow_fact matcher: bool_true path: evidence_collection_completed - id: summary_read_completed weight: 5 required: false description: Summary artifact is read when available. match: all_of rules: - source: workflow_fact matcher: bool_true path: summary_read_completed - id: final_answer_emitted weight: 0 required: false description: Final answer is emitted. match: all_of rules: - source: workflow_fact matcher: bool_true path: final_answer_emitted execution_contract: checks: - id: required_workflow_present required: true description: Required workflow milestones are present. match: all_of rules: - source: workflow_check matcher: subset_observed paths: - architecture_context_loaded - misdiagnosis_guardrails_loaded - diagnosis_run_initialized - evidence_collection_completed - id: required_artifacts_present required: true description: Required evidence artifacts are present. match: all_of rules: - source: artifact_fact matcher: subset_observed paths: - core_evidence_bundle_present - id: preferred_channels_minimum_observed required: true description: At least one preferred evidence channel is observed. match: all_of rules: - source: channel_fact matcher: count_gte paths: - query_or_metric threshold: 1 - id: preferred_channels_all_observed required: false description: Preferred evidence channels are all observed. match: all_of rules: - source: channel_fact matcher: subset_observed paths: - query_or_metric evidence_collection: weight: 5 checks: - id: required_artifacts_present weight: 4 required: true description: Required evidence artifacts are present and readable. match: all_of rules: - source: artifact_fact matcher: subset_observed paths: - core_evidence_bundle_present - id: preferred_channels_minimum_observed weight: 0 required: true description: At least the minimum number of preferred evidence channels are observed. match: all_of rules: - source: channel_fact matcher: count_gte paths: - query_or_metric threshold: 1 - id: preferred_channels_all_observed weight: 6 required: false description: Preferred evidence channels are all observed. match: all_of rules: - source: channel_fact matcher: subset_observed paths: - query_or_metric critical_evidence: weight: 30 checks: - id: lock_contention_signal_present weight: 8 description: Direct lock-contention evidence is present for the incident window. match: any_of rules: - source: artifact_json artifacts: - queries matcher: json_text_contains_any keywords: - 'lock_keys: {time:8.8s' - source: artifact_json artifacts: - metrics matcher: json_text_contains_any keywords: - tikv_lock_manager_waiter_lifetime_duration - acquire_pessimistic_lock - grpc_msg_duration_seconds - source: artifact_json artifacts: - summary_json matcher: json_text_contains_any keywords: - lock contention - pessimistic lock - lock manager - id: hotspot_instance_evidence_present weight: 8 description: Evidence isolates the hotspot to a single TiKV instance. match: any_of rules: - source: artifact_json artifacts: - queries matcher: json_text_contains_any keywords: - 'store: db-a924bb0f-tikv-29grsn.db-cluster.tidb2028998946604449792.svc.cluster.local:20160' - source: artifact_json artifacts: - metrics matcher: json_text_contains_any keywords: - tikv_grpc_msg_duration_seconds - tikv_lock_manager_waiter_lifetime_duration - acquire_pessimistic_lock - source: artifact_json artifacts: - summary_json matcher: json_text_contains_any keywords: - single TiKV instance - hotspot instance - one TiKV hotspot - id: primary_write_path_evidence_present weight: 9 description: Query evidence points to the dominant write path rather than a generic infrastructure issue. match: any_of rules: - source: artifact_json artifacts: - queries matcher: json_text_contains_any keywords: - UPDATE t_merchant_online SET amount_by_day - UPDATE t_merchant_online JOIN - t_merchant_online - source: artifact_json artifacts: - summary_json matcher: json_text_contains_any keywords: - high-frequency point update - repeated update workload - secondary join update evidence_routing: weight: 5 checks: - id: analysis_patch_valid_json weight: 1 required: true description: Analysis patch is valid JSON whenever the patch exists. match: any_of rules: - source: routing_fact matcher: bool_false path: analysis_patch_present - source: routing_fact matcher: bool_true path: analysis_patch_valid_json - id: analysis_items_shape_valid weight: 2 required: true description: Analysis patch items are structurally valid whenever the patch exists. match: any_of rules: - source: routing_fact matcher: bool_false path: analysis_patch_present - source: routing_fact matcher: bool_true path: analysis_items_shape_valid - id: analysis_key_evidence_present weight: 2 required: true description: Analysis patch includes key evidence whenever the patch exists. match: any_of rules: - source: routing_fact matcher: bool_false path: analysis_patch_present - source: routing_fact matcher: bool_true path: analysis_has_key_evidence - id: metric_refs_resolvable weight: 1 required: true description: Metric references resolve whenever the patch requires them. match: any_of rules: - source: routing_fact matcher: bool_false path: analysis_patch_present - source: routing_fact matcher: bool_true path: analysis_metric_refs_resolvable - id: query_refs_resolvable weight: 1 required: true description: Query references resolve whenever the patch requires them. match: any_of rules: - source: routing_fact matcher: bool_false path: analysis_patch_present - source: routing_fact matcher: bool_true path: analysis_query_refs_resolvable - id: supporting_evidence_present weight: 0 required: false description: Analysis patch includes supporting evidence whenever the patch exists. match: any_of rules: - source: routing_fact matcher: bool_false path: analysis_patch_present - source: routing_fact matcher: bool_true path: analysis_has_supporting_evidence - id: analysis_log_or_event_channel_resolvable weight: 0 required: false description: Routed log or event items stay resolvable against observed channels. match: all_of rules: - source: routing_fact matcher: bool_true path: analysis_log_or_event_channel_resolvable diagnosis: checks: - id: identify_lock_contention_as_primary_path mode: blended weight: 3 required: true description: Identifies lock contention on the primary write path as the main incident path. deterministic: match: all_of rules: - source: output_text matcher: keyword_any keywords: - lock contention - pessimistic lock - lock wait - write contention - concurrent write contention - hotspot key serialization - 锁冲突 - 锁竞争 - 锁等待 - 并发写争用 - 热点键串行化 - source: output_text matcher: keyword_any keywords: - write path - point update - update workload - 写路径 - 点更新 semantic: id: 1 title: 主路径判断 description: | 判断回答是否把主路径识别为 write contention hotspot，而不是 generic infrastructure explanation。 - id: identify_single_tikv_hotspot mode: blended weight: 3 required: false description: Identifies that the pressure was concentrated on one TiKV instance rather than cluster-wide. deterministic: match: any_of rules: - source: output_text matcher: keyword_any keywords: - single TiKV instance - hotspot TiKV - one TiKV hotspot - 单个 TiKV 实例 - 热点 TiKV semantic: id: 2 title: 热点范围识别 description: | 判断回答是否识别热点集中在单个 TiKV 实例，并将 lock contention、commit abort pressure 或 hot key 之类机制与该范围对应起来。 - id: recommend_write_path_mitigation mode: blended weight: 3 required: false description: Recommends mitigation targeted at the write-contention path. deterministic: match: any_of rules: - source: output_text matcher: keyword_any keywords: - batch update - batch aggregation - async aggregation - periodic flush - SHARD_ROW_ID_BITS - reduce update frequency - 批量更新 - 异步聚合 - 降低更新频率 semantic: id: 4 title: 修复建议对齐 description: | 判断回答是否给出 write-path mitigation、batching、async aggregation 或 reduce update frequency 等对齐 remediation。