[
https://issues.apache.org/jira/browse/JAMES-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659981#comment-16659981
]
Tellier Benoit commented on JAMES-2563:
---------------------------------------
https://github.com/linagora/james-project/pull/1829 This contribution proposes
JPA healthckeck.
https://github.com/linagora/james-project/pull/1824 And this one Cassandra
helthcheck
https://github.com/linagora/james-project/pull/1812 this one proposes this for
ElasticSearch
Many thanks to Jeroen Reijn (https://github.com/jreijn) & Matzepan
(https://github.com/matzepan)
> Additional guice HealthChecks for core and optional components
> --------------------------------------------------------------
>
> Key: JAMES-2563
> URL: https://issues.apache.org/jira/browse/JAMES-2563
> Project: James Server
> Issue Type: New Feature
> Components: guice
> Reporter: Tellier Benoit
> Priority: Major
> Labels: feature, newbie
>
> We recently introduced heathChecks, allowing to test the health of a
> component.
> Results are aggregated and exposed over WebAdmin.
> As of today, only 2 health checks are implemented: Guice (stop/start) and
> RabbitMQ
> We would need health checks for other components, including:
> Critical services (if they are failing the service is *unhealthy*)
> - Cassandra
> - ElasticSearch
> - JPA
> Optional services (if they are failing, the service is *degraded*)
> - Tika
> - SpamAssassin
> In order to test these services, we need to execute some sample requests.
> We would also need to bind these health-checks in guice products where
> appropriate.
> Please open a separate pull request per health check...
> We do stay at your full disposal on Gitter to answer related questions
> (https://gitter.im/apache/james-project)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
