---
name: network-or-connectivity
description: Diagnose independent network, connectivity, gRPC, and cross-component communication root causes.
---

# Use When

Use this family subskill when an independent network/connectivity failure or communication
bottleneck starts earlier than query/component pressure and best explains the incident.

# Required Evidence

- Network-lag alerts, connection reset bursts, gRPC errors/latency not explained by TiKV load,
  packet loss, cross-zone degradation, DNS/TLS/connectivity errors, or client-side transport
  failures.
- Timeline evidence showing network/connectivity started before downstream SQL/TiKV symptoms.

# Classification

- `standard_root_cause_class`: `network_or_connectivity`
- compatible `primary_class`: `service_unavailability_or_worker_failure` until schema is extended
- common symptom tags: `network_latency`, `slow_query`, `tikv_hotspot`
- specialist skills: component-specific skill plus Loki/metrics

# Decision Rules

- Do not classify gRPC P99 as network root cause when TiKV CPU, coprocessor, IO, or query
  pressure explains the same latency.
- Treat related network alerts as correlation unless they are independent, earlier, and
  component-wide enough to explain impact.

# Final Response Anchors

- Say `related alert correlation` when related alerts explain the impact chain.
- Name the independent transport/connectivity evidence and rule out workload-driven gRPC latency.