Dashboards and metrics

The metrics the platform emits, and the dashboards built on them.

Operations0DomainMonitoring and reportingStatedocumentedAPIs0

Everest emits OpenTelemetry metrics through a single meter named EverestMetrics. An OTEL collector exports them to Prometheus; Grafana draws from Prometheus. Metric groups are switched on per service in metricsOption.metrics, so a service emits only the families it declares. Metric names are prefixed everest_<service>_, so a counter carries the service that raised it rather than colliding with the same name elsewhere.

Exported series 22

Six collectors publish twenty-two series. The window each covers is part of its name, and the labels are what a panel groups by.

Executive overview 6

Series	Labels	What it counts
payments_auth_last5m_total	Channel · Scheme	Authorisations received in the last five minutes.
payments_auth_last5m_approved	Channel · Scheme	Of those, the ones approved.
payments_auth_last5m_declined	Channel · Scheme	Of those, the ones declined.
payments_auth_last5m_error	Channel · Scheme	Of those, the ones that errored rather than reaching a decision.
payments_sales_last1d_amount_minor	Scheme · Currency	Approved sales value over a day, in minor units.
payments_recon_chargeback_last30d	Scheme	Chargebacks over thirty days, counted from reconciliation results.

Real-time traffic 4

Series	Labels	What it counts
payments_auth_last1m_count	Channel · Scheme	Authorisations in the last minute.
payments_auth_last1m_error_count	Channel · Scheme	Of those, the ones that errored.
payments_latency_last1m_avg_ms	Channel · Scheme	Mean end-to-end processing time, in milliseconds.
payments_decline_last5m_by_code	DeclineCode	Declines over five minutes, split by the code returned.

Issuer and merchant performance 3

Series	Labels	What it counts
payments_issuer_last1d_stats	IssuerBin · status	Total, approved and declined per issuer BIN; `status` carries which.
payments_merchant_last1d_stats	MerchantId · status	The same three counts per merchant.
payments_merchant_last1d_amount_minor	MerchantId · Currency	Approved value per merchant, in minor units.

Fraud and risk 4

Series	Labels	What it counts
fraud_events_last1h_by_rule	RuleId	Fraud events raised, by the rule that raised them.
fraud_events_last1h_by_merchant	MerchantId	The same events, by merchant.
payments_3ds_last1h_stats	Scheme · auth_type	3-D Secure usage; `auth_type` carries which authentication path was taken.
payments_high_fraudscore_last1h	Scheme	Transactions scoring at or above eighty.

Clearing and settlement 4

Series	Labels	What it counts
clearing_batches_last7d	Scheme · Status	Clearing batches over seven days, by scheme and batch status.
clearing_batches_last7d_amount_minor	Scheme	Their total value, in minor units.
settlement_last30d_amount_minor	MerchantId · Currency	Gross settlement over thirty days.
recon_mismatches_last30d	Scheme · MismatchType · measure	Reconciliation mismatches; `measure` carries count against amount.

Error codes 1

Series	Labels	What it counts
error_codes	service · domain_id · error_code · description	Error codes currently active, one series per code.

Dashboards 10

Ten dashboards, provisioned from files rather than edited in place, all drawing from the single Prometheus datasource. The section rows are the dashboard's own, and are the fastest way to find which board answers a question.

Dashboard	Covers	Panels	Sections
Issuing Authorization — Executive, Risk & Platformissuing-auth-all	Issuing authorisation	33	Executive Overview · Risk & Fraud · Platform & Dependencies · Network & Scheme · 1. Main Metrics · 2. Root Cause & Analysis
Debit Executive Summarycms-debit-executive	Debit portfolio	45	1. Core Portfolio Metrics Histogram · 1. Core Portfolio Metrics (Counts) · 2. Usage Channels & Anomaly Tracker · 3. Card Issuance Types · 4. Segment Deep Dive · 4.1 Segment KPI Trends · 4.2 Segment Market & Support · 5. Operational SLA & Digital Segments
Clearing & Recon Command Centercms-clearing-command-center	Clearing and reconciliation	29	1. Clearing File Summary · 2. Incoming Matching & Validation · 3. Settlement & Accounting · 4. Reconciliation GAP & Aging
EOD Batch & Job Command Centercms-eod-monitor	End of day	26	1. In-Day Planned Processes · 2. Last EOD Summary · 3. Live Job Execution Status · 4. Failed & Anomaly Tracker
Dispute Dashboardcms-dispute-dashboard	Disputes	11	1. Dispute Info · 2. Case Aging Buckets · 3. Merchant & Customer Analysis
Alerts Overviewalerts-overview	Alerting	6	Health Check · System Exception · CMS Alerts
Error Codeserror-codes	Exceptions	4	—
Health Checkhttp-probes	Service health	7	—
Health Check — Domain Viewhttp-probes-domain	Service health	2	—
Health Check — Service Detailshttp-probe-service-details	Service health	6	—

Alert rules 7

Seven rules, evaluated every fifteen seconds. Severity is either warning or critical; there is no third level, and nothing pages on a warning.

Rule	Fires when	For	Severity	Dashboard
HealthCheckDownA probe target stopped answering.	probe_success == 0	10s	critical	http-probes
SystemExceptionErrorCodeAn error code is active. The code and its description are on the series.	error_codes > 0	1s	warning	error-codes
CmsEodStatusFailedEnd of day finished as something other than success.	cms_eod_status_code != 1	10s	critical	cms-eod-monitor
CmsEodFailedJobsWarningAt least one job failed. Review and retry before close.	cms_eod_failed_jobs > 0	30s	warning	cms-eod-monitor
CmsEodFailedJobsCriticalMore than three jobs failed.	cms_eod_failed_jobs > 3	30s	critical	cms-eod-monitor
IssuingApprovalRateLowApproval rate fell below ninety per cent.	issuing_mc_approval_rate_percent < 90	30s	warning	—
ClearingUnmatchedCountHighIncoming clearing records are not matching.	sum(cms_clearing_incoming_unmatched_count) > 250	30s	warning	cms-clearing-command-center