- Monitor sender, receiver, server, and cluster channels—visibilit
🔌 Monitor Channel Status & Connectivity
- Track channel state (running/stopped/retrying/inactive)—detects partner disconnections, firewall changes, network failures
- Monitor sender, receiver, server, and cluster channels—visibility across all MQ connectivity types
- Alert on retrying channels—indicates transient connection issues before they escalate to full failure
- View channel message counts and last message time—validates channel actively processing vs. idle
Real-World Example: Logistics company partner EDI channel PARTNER.EDI.SVRCONN normally maintains state RUNNING 24/7 (shipping partner submits 850 EDI purchase orders daily via MQ, average 35 orders/hour during business hours, 12 orders/hour overnight). Friday 3:42 PM, partner IT implements "routine security patch" to their firewall (Palo Alto Networks device protecting partner datacenter perimeter). Patch deployment accidentally enables "strict SPI [Stateful Packet Inspection]" for outbound TCP connections, blocks all outbound traffic on port 1414 (IBM MQ default listener port). Partner's MQ sender channel PARTNER.EDI.SENDER attempts connection to company's receiver channel, connection refused (firewall blocks TCP SYN packet). Channel state changes RUNNING → RETRYING (automatic retry every 60 seconds per MQ channel retry configuration). No monitoring alerts fire on either side (partner assumes "our channel is fine, receiver must be down", company has no visibility into channel state). Friday 3:42 PM-Monday 9:15 AM = 65.5 hours failure unnoticed. Monday 9:15 AM partner escalates: "EDI feed down all weekend, 2,040 purchase orders stuck in our queue, cannot transmit". Emergency response: 4 engineers (company network team + partner network team + MQ admins) on conference bridge, 3 hours troubleshooting firewall rules + packet captures × $145/hour = $52,800 labor cost + $78,000 expedited air freight (weekend POs not processed, raw materials shortage Monday morning, charter freight from backup supplier to keep production line running) + $54,200 production line disruption (Monday 6 AM-2 PM partial shutdown waiting for materials, 35 workers × 8 hours × $98/hour fully-loaded) = $185,000 total incident cost. Root cause discovered: partner firewall strict SPI enabled, blocking MQ port 1414 outbound (firewall logs show 3,780 blocked connection attempts Friday 3:42 PM-Monday 9:15 AM). Fix: disable strict SPI for MQ traffic, channel returns RUNNING Monday 12:14 PM. With Nodinite monitoring: Alert fires Friday 3:43 PM ("Channel PARTNER.EDI.SVRCONN state RETRYING, connection refused from partner host 198.51.100.88:1414, retry count 1"). Company network team investigates immediately, contacts partner IT within 5 minutes ("your connection attempts failing, firewall blocking port 1414?"). Partner reviews firewall change log, identifies strict SPI patch deployment 3:42 PM, disables strict SPI for MQ traffic by 3:56 PM. Channel returns RUNNING 3:58 PM. Zero 65-hour outage, zero Monday crisis, $185,000 incident cost eliminated.