What happens if SYSTEM.BROKER.MONITORING.EVENTS MQ queue fills up?
Monitoring Events are rejected when queue hits MAXDEPTH limit—events lost, audit trail incomplete. Prevention: Increase MAXDEPTH to 500,000 messages (~10GB) for 12-24 hour buffering during network outages/maintenance. Configure [Non-Events Monitoring][Non Events Agent] to alert if queue depth exceeds 80% threshold (e.g., ">400,000 messages = Nodinite agent likely stopped consuming"). Operations team investigates before queue fills.
Recovery: If queue fills, increase MAXDEPTH immediately, restart Nodinite agent to consume backlog. For prevented event loss: Configure IBM ACE Dead Letter Queue (DLQ) as backup (complex setup, not recommended for first implementation).
Related Questions
See all FAQs: [Troubleshooting Overview][]