[jira] [Created] (JAMES-3607) Healthcheck for Email reception

["Benoit Tellier (Jira)" <se...@james.apache.org>]

Benoit Tellier created JAMES-3607:
-------------------------------------

             Summary: Healthcheck for Email reception
                 Key: JAMES-3607
                 URL: https://issues.apache.org/jira/browse/JAMES-3607
             Project: James Server
          Issue Type: New Feature
          Components: guice, rabbitmq
    Affects Versions: master
            Reporter: Benoit Tellier
             Fix For: 3.7.0


h3. Why?

As described in JAMES-3605, RabbitMQ consumers can end up being stuck.

In such a scenario we are not able to detect the failure and end up relying on cunsumer reports to restart James.

We would like to have a health-check, allowing automatic testing about mail reception. (Both periodical logs and also a HTTP endpoint for integration with a monitoring system)...

So a healthcheck no longer for a technical component but for a feature.


h3. How?

In `healthcheck.properties` on could configure a user to run reception checks:

{code:java}
reception.checks.user=test@domain.tld
{code}

If configured, the healthcheck would then send a mail to the user, await the email via the eventbus, then retrieve its content.

To be placed in a new `server/container/feature-checks` maven project.

h3. Definition of done

 - Given a paused RabbitMQ the check fails for the distributed server
 - Given a working James the check passes.

h3. Disclaimer

The idea had been first expressed by [~matthieu] years ago...



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org