[
https://issues.apache.org/jira/browse/JAMES-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140102#comment-17140102
]
Benoit Tellier commented on JAMES-3243:
---------------------------------------
> I was not able to find any existing documentation about this configuration.
> The link provided in the file
> (https://james.apache.org/server/config-healthcheck.html) leads to a 404.
https://github.com/apache/james-project/blob/master/src/site/xdoc/server/config-healthcheck.xml
is the related source code. Current latest Website is not deployed yet, I will
redeploy it as part of JAMES-3207 JAMES 3.5.0 release.
The healthchecks could be queried as part of WebAdmin REST api, even outside
docker.
The idea of course is to offer some liveness probes for running James in
Kubernetes. This file "just" controls the frequency at wich helthchecks logs
are emmitted.
> However, we could simply *tell* the Operator how it works without providing a
> configuration option. We could therefore eliminate the configuration for this
> feature for the Basic Server.
+1
In the context of the Basic server we can safely not specify this file. (And
the classic WARN will be emitted but let's fix that in another issue).
> Clarify HealthCheck Configuration (healthcheck.properties)
> ----------------------------------------------------------
>
> Key: JAMES-3243
> URL: https://issues.apache.org/jira/browse/JAMES-3243
> Project: James Server
> Issue Type: Sub-task
> Reporter: David Leangen
> Priority: Major
>
> In the context of the *Basic Server*, determine if (1) this configuration is
> necessary, and if so (2) how can we minimize it and (3) document it better.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
