Skip to content

Dead Letter Queue (DLQ) Sensor

Overview

Subscription

This sensor is only available with Entreprise subscriptions

The Dead Letter Queue (DLQ) Sensor in Onagre allows users to monitor the number of messages in a Dead Letter Queue (DLQ) within a supported message broker. This sensor ensures that messages are not accumulating in a DLQ, which may indicate processing failures or system issues.

Configuration Options

When setting up a DLQ Sensor, the following parameters can be configured:

  • Queue Name: The name of the Dead Letter Queue to monitor.
  • Maximum Allowed Messages: Defines the threshold above which an alert is triggered.
  • Check Interval: Defines how often the DLQ should be checked (e.g., every minute, every five minutes).

Note: This sensor currently supports only RabbitMQ, with plans to expand to other message brokers in future updates.

Response Validation

The DLQ Sensor validates the queue state based on:

  • Queue Reachability: Ensures the queue is accessible and responding.
  • Message Count: Checks if the number of messages exceeds the defined threshold.

Alerts and Notifications

If the sensor detects an issue with the DLQ, such as excessive messages, it can trigger alerts via:

  • Slack, Microsoft Teams, Discord, Google Chat, Webhooks, Pushover
  • Email Notifications
  • Onagre’s Dashboard for Incident Tracking

Use Cases

  • Detecting failures in message processing systems.
  • Identifying applications that are not properly consuming messages.
  • Ensuring system health by preventing queue overflow.
  • Monitoring integration services that rely on message brokers.

Deployment

The DLQ Sensor operates within Onagre’s private agent framework, allowing checks to be performed in secure internal environments where message queues are hosted.

Summary

The DLQ Sensor is a crucial tool for maintaining the health of message-driven architectures. By detecting blocked or accumulating messages in Dead Letter Queues, it helps teams ensure reliable message processing and prevent service disruptions.