StoneX monitoring
MQ connection + per-queue traffic from stonex-service-events · times in America/Curacao MQ LIVE
QM1
LIVE
up since 29 Sep 15:46:15.098
Queues
received count shown next to each queuequeue
status
received
sent
failed
last activity
QLT.BBLZ.MT.TOSWIFT
0
active
0
1
0
29 Sep 15:46:15.272
QLT.BBLZ.MX.TOSWIFT
0
active
0
13
0
29 Sep 15:46:15.439
Recent outbound to StoneX
exact message put on the TOSWIFT queue · click a row to view the body29 Sep 15:46:15.439
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
29 Sep 15:46:15.272
LOCALXXX
QLT.BBLZ.MT.TOSWIFT
MT
SENT
21 Sep 09:44:18.158
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
21 Sep 09:44:18.003
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
21 Sep 09:44:17.725
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
21 Sep 09:44:17.420
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
21 Sep 09:44:17.100
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
21 Sep 09:44:16.638
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
21 Sep 09:44:16.445
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
18 Sep 08:54:43.330
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
16 Sep 18:18:14.508
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
16 Sep 18:18:14.468
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
16 Sep 18:18:14.425
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
16 Sep 18:18:14.383
LOCALXXX
QLT.BBLZ.MX.TOSWIFT
MX
SENT
Connection state is edge-triggered — StoneX emits UP/DOWN transitions, not a heartbeat, so "up since" is the last time it came up. Counts are tallied from stonex-service-events over the stream's retention; times use the stream-id clock.