Conversion Agent connection to RabbitMQ is broken

Description

This alert is triggered when one or more RabbitMQ queues for the Conversion Agent or Conversion Complete Agent do not have any consumers.

Resolution Guidance

Impact When Active

  • Conversion jobs will not be processed, resulting in document conversion failures.
  • A backlog of unprocessed messages will accumulate in the RabbitMQ queue.
  • This may impact downstream systems or workflows that rely on conversion (e.g. document viewer).

How To Resolve

  1. Check the status of the Conversion Agent or Conversion Complete Agent by navigating to the Agents tab in Relativity:

    • Login to Relativity.
    • Go to the Agents tab.
    • Filter by the name containing 'conversion'.
    • Enable the agent if it is disabled.
    • If enabling the agent does not resolve the alert, follow the steps below.
  2. Verify RabbitMQ is running and healthy.

    • Check service status: Run rabbitmqctl status on the RabbitMQ server or use your operating system's service manager (e.g. Services MMC on Windows).
    • Check the management UI: If enabled, access the RabbitMQ management UI (typically at http://localhost:15672) and verify the node and queue health.
    • Check queue and consumer counts: In the management UI, navigate to the Queues page, add the Consumers column, and review the relevant queues for message and consumer counts.
    • Review logs: Examine RabbitMQ logs for errors or warnings (default location: %APPDATA%\RabbitMQ\log\ on Windows).
    • Test connectivity: From the agent host, use telnet <rabbitmq_host> 5672 or a similar tool to confirm network connectivity to RabbitMQ.
  3. Restart the RabbitMQ Windows Service, if needed.

  4. Ensure network connectivity between the Conversion Agent or Conversion Complete Agent and the RabbitMQ server (check firewalls, DNS, and routing).

  5. Confirm the RabbitMQ credentials and connection settings in the the Relativity Instance Settings page.

  6. After making corrections, enable the Conversion Agent or Conversion Complete Agent and monitor the queue for active consumers.

  7. Verify conversion jobs have resumed successfully:

    • Confirm Conversion Agent connection to RabbitMQ is broken Relativity alert is recovered.
    • Monitor a few documents to ensure that conversions have completed without errors.

Alert Details

Alert Condition Details

Name Value Description
Rule Type Elastic Query
Data View metrics-*
Filter Query ((labels.rabbitmq_queue_name: conversions_RP*_ConversionAgent_Priority* AND NOT labels.rabbitmq_queue_name: conversions_RP-_ConversionAgent_Priority) OR labels.rabbitmq_queue_name: conversionresponses_ConversionCompleteAgent_Priority*) AND rabbitmq.consumer.count <= 0
Group Count
Threshold <= 0 Alert is triggered when there are no consumers for one or more Conversion Queues
Time Window 5 Mins Verify data for last 5 min
Frequency 2 Min Checks for every 2 min

Alert Metric Details

Metric Name: rabbitmq.consumer.count

Metric Description: The alert is triggered when one of the conversion queues has no consumers.

Metric Attributes:

Attribute Name Description Value
rabbitmq_queue_name The name of the RabbitMQ queue
rabbitmq.consumer.count The number of consumers currently reading from the queue.