SYSTEM
CRITICAL
GATEWAY
:8080 Proxy0.8ms ovh
SERVICES
4 Nodes(2 UP, 1 SLOW, 1 DOWN)
TRAFFIC
31,460~40 req/s
ERRORS
4.14%(1304 errs)
LATENCY
292msrolling avg
Total Services
4Nodes
2 UP1 SLOW1 DOWN
Health Ratio
2/4(50%)
Total Requests
31,460reqs
~35-50 req/s live rate
Errors & Rate
4.14%(1,304 errs)
Elevated (outage active)
Average Latency
292msrolling
p50: ~30ms • p95: ~820ms

Microservices Status & Health

Upstream service nodes, health states, live activity sparklines, and fault triggers

User Service

:3001v1.4.2
UP
Latency24ms
Requests4,120
Errors12
Uptime99.98%
Activity TrendOPTIMAL
Endpoints (4):
GET/usersGET/users/:idPOST/users/authPUT/users/profile

Event Service

:3002v2.1.0
SLOW
Latency820ms
Requests18,450
Errors384
Uptime97.4%
Activity TrendDEGRADED
Endpoints (4):
GET/eventsPOST/events/publishGET/events/streamGET/events/analytics

Order Service

:3003v1.0.8
DOWN
LatencyTIMEOUT
Requests3,200
Errors890
Uptime78.1%
Activity TrendOUTAGE
Endpoints (4):
GET/ordersPOST/orders/checkoutPOST/orders/createGET/orders/:id

Payment Service

:3004v1.8.0
UP
Latency31ms
Requests5,690
Errors18
Uptime99.85%
Activity TrendOPTIMAL
Endpoints (4):
POST/payments/chargePOST/payments/intentGET/payments/webhookPOST/payments/refund

Service Dependency Topology

Real-time architectural flow from client edge through MiniEdge proxy to upstream microservices

Healthy Degraded Down Traffic Pulse Dropped
24ms820msDROP31msClientHTTP InboundExternal TrafficMiniEdge:8080 Core ProxyLocal Dev GatewayCritical Outage DetectedUser Service:30014 routes • 24msUPEvent Service:30024 routes • 820msSLOWOrder Service:30034 routes • TIMEOUTDOWNPayment Service:30044 routes • 31msUP

Telemetry & Metrics

Zero-dependency Canvas visualizers for gateway throughput, error spikes, and upstream latency distribution

Live 24-Point Buffer
Request ThroughputGateway requests per second
-- req/speak: --
Error Spikes & Incidents4xx / 5xx frequency • Live timeline
-- err/sRate: --
Latency Trendsp50 median & p95 tail response times
p50 p95

Request Explorer

Live stream of incoming client HTTP traffic routed through MiniEdge gateway

Showing 15 of 15 requests
MethodPath & Request IDStatusLatencyTarget ServiceTimestampInspect
GET/usersreq_z60xqjl20021msUser Service17:35:08.175
GET/events/analyticsreq_h96ik90200830msEvent Service17:35:06.375
POST/payments/refundreq_aio3rny20035msPayment Service17:35:04.575
POST/orders/createreq_cy8jsmj5008msOrder Service17:35:02.775
PUT/users/profilereq_4sft54a20025msUser Service17:35:00.975
GET/events/streamreq_lauxuu0200805msEvent Service17:34:59.175
GET/ordersreq_86zig0q5032msOrder Service17:34:57.375
POST/payments/intentreq_ur5q9q920030msPayment Service17:34:55.575
POST/users/authreq_oq4qtdb20028msUser Service17:34:53.775
POST/orders/checkoutreq_kbj432q5005msOrder Service17:34:51.975
POST/payments/chargereq_jams12620032msPayment Service17:34:50.175
POST/events/publishreq_1xlbq2n200845msEvent Service17:34:48.375
GET/eventsreq_91ag7nw200810msEvent Service17:34:46.575
GET/users/usr_981req_bkt09or20026msUser Service17:34:44.775
GET/usersreq_058fltx20022msUser Service17:34:42.975

Developer Log Console

Monospace stdout stream of gateway routing decisions, circuit break events, and proxy errors

LIVE ARCHITECTURAL EVENTS:
17:34:47.976[INFO]MiniEdge Gateway v1.0.0 listening on http://127.0.0.1:8080
17:34:50.176[INFO]Dispatched proxy upstream -> :3001 completed in 22ms
17:34:52.376[WARN]High upstream response latency detected (>500ms threshold)
17:34:54.576[ERROR]Upstream connection reset by peer on port :3003
17:34:56.776[INFO]Payment intent created successfully via :3004
miniedge-gateway-stdout.log10 lines
17:34:47.976[INFO][req_4vomx][gateway]SYSTEM/bootHTTP 200(1ms)MiniEdge Gateway v1.0.0 listening on http://127.0.0.1:8080
17:34:50.176[INFO][req_5844f][users]GET/usersHTTP 200(22ms)Dispatched proxy upstream -> :3001 completed in 22ms
17:34:52.376[WARN][req_0i1c0][events]GET/eventsHTTP 200(810ms)High upstream response latency detected (>500ms threshold)
17:34:54.576[ERROR][req_4khj0][orders]POST/orders/checkoutHTTP 500(5ms)Upstream connection reset by peer on port :3003
17:34:56.776[INFO][req_ig6hw][payments]POST/payments/chargeHTTP 200(32ms)Payment intent created successfully via :3004
17:34:58.976[ERROR][req_a3g4v][orders]GET/ordersHTTP 503(2ms)Circuit Breaker OPEN: Order Service unreachable
17:35:01.176[INFO][req_3o7b8][users]POST/users/authHTTP 200(28ms)Token authenticated successfully
17:35:03.376[WARN][req_ziul8][events]POST/events/publishHTTP 200(845ms)Kafka event broker ack delayed in upstream cluster
17:35:05.576[INFO][req_pphtg][payments]POST/payments/intentHTTP 200(30ms)Webhook registered for stripe charge session
17:35:07.776[ERROR][req_n7668][orders]POST/orders/createHTTP 500(8ms)Dial tcp 127.0.0.1:3003: connect: connection refused

Fault Injection & Chaos Studio

Test circuit breakers, timeout resiliency, and alert triggers under simulated upstream degradation

LOCAL SIMULATION / INTENTIONAL FAILURE

1. Target Upstream Service

2. Inject Fault Scenario

Inject Artificial Latency:
Simulate Failure / Error:

Active Fault Overrides

User Service (:3001)UP
Healthy
Event Service (:3002)SLOW
+750ms LatencyForced SLOW
Order Service (:3003)DOWN
Forced DOWN
Payment Service (:3004)UP
Healthy

Demo Presets: