29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
---
|
|
title: Payment Service Latency Alert
|
|
keywords: [HighLatency, payment-service, p95 latency, downstream dependency]
|
|
summary: Diagnose payment-service p95 latency alerts and identify downstream dependency bottlenecks.
|
|
category: aiops
|
|
source: payment-service-latency
|
|
breadcrumb: AIOps > Service Alerts > Payment Latency
|
|
kb_scope: rag-eval
|
|
covers: [payment-service, latency, downstream dependency]
|
|
when_to_retrieve: Use when an alert mentions payment-service, HighLatency, or elevated p95 latency.
|
|
---
|
|
|
|
# AIOps
|
|
|
|
## Service Alerts
|
|
|
|
### Payment Latency
|
|
|
|
For `HighLatency` alerts on `payment-service`, treat p95 latency as the primary symptom.
|
|
|
|
Diagnosis steps:
|
|
|
|
1. Confirm whether p95 latency is isolated to payment-service or shared across upstream callers.
|
|
2. Compare payment-service latency with downstream dependency latency for gateway, risk, and order services.
|
|
3. Check connection pool wait time, retry spikes, and timeout rates.
|
|
4. If downstream dependency latency increased first, classify payment-service as affected rather than root cause.
|
|
|
|
The expected evidence terms are p95 latency, payment-service, and downstream dependency.
|