Uploaded image for project: 'James Server'
  1. James Server
  2. JAMES-2563

Additional guice HealthChecks for core and optional components

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • guice

    Description

      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)

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            btellier Benoit Tellier

            Dates

              Created:
              Updated:

              Issue deployment