⚠ Monitoring data is stale — last update was
The monitoring agent on the GCP VM may not be running. Check cron on cypator-monitor.
Summary
Connecting to monitoring data...
Busted trades (not critical):
Tradingitrade count and gross USD notional value from executed trades. uses the usd_value field from maker_orders (pre-calculated USD equivalent). deduplicated by maker_child_order_id. desk split (AWR / DLT / RenGen) uses maker_orders.taker_id.
Today (UTC)
—
trades
—
gross USD
Yesterday (UTC)
—
trades
—
gross USD
Last 24 Hours
—
trades
—
gross USD
Last 7 Days
—
trades
—
gross USD
Last 30 Days
—
trades
—
gross USD
Trading — Date Rangeisums pre-computed daily aggregates for the selected UTC date range. same trade semantics as the Trading card (deduplicated maker orders), split by desk and by maker/LP. closed days are fixed; today's row refreshes with every monitor run.
Pipeline verificationiverifies the last trade was persisted end-to-end: trade-persistor wrote it to DB, post-trade reported it to the PB, and the Kafka consumer is active.
Market Datailiquidity-provider (maker) adapters and taker connections on gcp-prod, from Kubernetes deployment replica status (ready/desired). Adapters parked at 0 replicas are expected during the migration. Per-adapter quoting detail (FIX 35=W snapshots) is a planned enhancement.
Liquidity Providers (makers)
Takers
No market-data topology reported
Log Reviewiscans stdout and application logs from all trading components for errors. known noise patterns (stale Kafka groups, CMC rate errors, etc.) are filtered automatically. only actionable findings are shown.
Recent Config Changesichanges to static database tables in the last 7 days: organizations, instruments, users, and maker connections. helps track onboarding activity and configuration updates.
No changes in the last 7 days
Recent checks
| Time | Status | Pods | Kafka | Trades | Failed | Missing | |
| Loading... |