Back to websiteSample workspace with illustrative data. Start a free trial to see your own.Sign in
Sample data

Overview

A payments platform for modern businesses.

2 services need attention

kyc-verify is failing (6.5% of requests) and fx-gateway is degraded (3.19%). Four services are healthy, one has too little traffic to judge, one sent no data.

Updated 14:07:12 GMT, 14 s ago A request is an entry span (server, consumer, or a root span) with health probes excluded. A failed request is a distinct trace with an error span in that service, never more than the requests. Dashboards, Services, Query Studio and AIOps all use this rule.
Edge requests
9,737
4.1%vs previous hour
Failed requests
3.19%
2.3 pts311 of 9,737
p95 latency
468ms
61 msvs previous hour
Open alerts
2
from alert rules
1 declared incident, listed separately

Trend, fx-gateway

Last 60 minutes, local time (GMT)
Entry spans, per minute

Services

View all
ServiceStatusRequestsFailedp95Trend

Needs attention

Alert Rules
From alert rules2 open

kyc-verify: failed requests above 5%

Since 13:55 GMT, 12 min. Rule "Failed requests, 5 min".

fx-gateway: p95 above 450 ms

Since 14:04 GMT, 3 min. Rule "Latency p95".

Declared incidents, not from rules1

INC-0007 Paystack payout delay

Declared by ops at 13:20 GMT. Severity 3.

SLO error budgets

30 days
Quote success, 99.5%
Attainment 99.62%, budget left 24%
Settlement completes, 99.0%
Attainment 99.71%, budget left 71%
KYC check under 2 s, 95%
Low confidence: only 1,471 requests in the window

Changes near the failure

kyc-verify config change

13:52 GMT, three minutes before the rule fired.

rate-engine v2.14.1 deployed

13:41 GMT. No error change since.

Payment operations

Open payment workspace

Ask Onyx Oracle

Answers use data from this workspace only. Every step lists the evidence it read.