User Tools
Writing /app/www/public/data/meta/resolution_area/prometheus_resolutions/res-p1806.meta failed
resolution_area:prometheus_resolutions:res-p1806
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| resolution_area:prometheus_resolutions:res-p1806 [2021/06/24 15:00] – btobin | resolution_area:prometheus_resolutions:res-p1806 [2023/10/18 09:00] (current) – 10.91.120.100 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ===== RabbitmqTooMuchUnack ===== | ||
| + | |||
| + | **Level:** __Critical__ FIXME | ||
| + | |||
| + | |||
| + | **Purpose: | ||
| + | Alerts if a queue in RabbitMQ has too many unacknowledged messages | ||
| + | |||
| + | **Scenario: | ||
| + | |||
| + | **Resolution: | ||
| + | Each queue should have a consumer. Check whether the consumer is still running or check the RabbitMQ logs for any connection errors. | ||
| + | |||
| + | Example: | ||
| + | orchestratorInboundTask had unacknowledged messages. Restarting the rdf_orchestrator resolved this | ||
| + | |||
| + | **Manual Action Steps:** | ||
| + | Fix consumer of unacknowledged messages | ||
| + | |||
| + | **Auto Clear:** | ||
| + | When unacknowledged message fall below 1000 | ||