M
OMS-360 Enterprise Monitoring Center
Application, database, Kafka & API health — live from the running service
Backend…
Database…
Kafka…
Last Refresh–
Interval6s
Connected Since–
--
⚠ Could not reach the OMS-360 API. Showing the last data received. Retrying automatically…
🚨 One or more dependencies are DOWN

⚠ Immediate Attention Required Top Priority

Business failures (Failed Orders, Duplicate Orders, Payment Failures) are order-level problems a customer or support agent would recognize — a payment was rejected, an order didn't go through, the same order was submitted twice. Technical failures (Dead Letter Queue / DLQ) are backend messaging errors — Kafka events the system could not process after automatic retries. They are tracked separately because different teams act on them: support/ops on business failures, engineering on technical ones. A business failure is not the same thing as a DLQ entry, even when both relate to the same order.
BUSINESSFailed Orders
OrderReasonAt
Loading…
BUSINESSDuplicate Orders
MarkerIdem. KeyAt
Loading…
TECHNICALDead Letter Queue (DLQ)
OrderTxnAt
Loading…
Critical Alerts
Loading…
CHECKING…
Environment-
Build Version-
DB Response Time-
Last Checked-

🔔 Alerts & Operational Issues Sorted: Critical → High → Medium → Information

Loading…
Active Alerts (currently ongoing)
Loading…
Recent Alerts (event feed)
OPSLow Stock
ItemLeft
Loading…
OPSOut of Stock
ItemLeft
Loading…
OPSKitchen Delays
OrderOverdue By
Loading…
BUSINESSPayment Failures
OrderAmount
Loading…

⚙ Live System Health Summary — not the top priority view

Backend
…
Database
…
Kafka
…
Docker
…
Consumer
…
API Response
…
DB Response
…
Last Updated: -
Next Refresh: -

📊 Live Summaries

Inventory Summary
…
Kafka Summary
…
API Summary
…
DLQ
…

⚠ Reliability Counters

0
DLQ Messages (Technical)
0
Duplicate Orders (Business)
0
Failed Orders (Business)
0
Retry Queue
0
API Requests
0
API 4xx / 5xx

📈 Performance

CPU · Memory · Disk Usage
API Response Time by Endpoint (avg ms)