[
https://issues.apache.org/jira/browse/JAMES-3817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3817.
---------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
> Health Check for rabbitMQ dead letter queues
> --------------------------------------------
>
> Key: JAMES-3817
> URL: https://issues.apache.org/jira/browse/JAMES-3817
> Project: James Server
> Issue Type: Improvement
> Components: rabbitmq
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.8.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> h3. The philosophy
> If my data is stuck somewhere, I need alerting in place to "unstuck" it.
> Health checks is a good way to do this:
> - logs as WARN/ERROR
> - HTTP calls from eg zabbix
> - And hopefully that will be the first page of a webadmin UI!
> h3. RabbitMQ deadletter
> Data can end up in rabbitMQ errors if:
> - Mail processing situation is desperate, cassandra mail repository keeps
> failing, we requeued too many time / can't requeue
> - Idem for event processing if saving to dead letter fails
> - deserialisation errors
> h3. Definition of Done
> Write a health check that fails as degraded if james dead letter queues are
> not empty.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
