[
https://issues.apache.org/jira/browse/JAMES-3849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17628155#comment-17628155
]
ouvtam commented on JAMES-3849:
-------------------------------
I don't think it's a critical issue since WebAdmin should not be exposed
publicly. Otherwise, put a reverse proxy in front with some kind of rate
limiting.
However, if you use some other services to monitor (e.g. Monit, Prometheus
etc.) or external services that are out of your control this could lead to
potential side effects.
>From the perspective of a James operator this might not be obvious.
> WebAdmin: Cache health checks
> -----------------------------
>
> Key: JAMES-3849
> URL: https://issues.apache.org/jira/browse/JAMES-3849
> Project: James Server
> Issue Type: Improvement
> Components: webadmin
> Reporter: ouvtam
> Priority: Major
>
> While working on JAMES-3841 I noticed that a health check (e.g. ActiveMQ) is
> called periodically and for each WebAdmin request (i.e.
> [http://localhost/healthcheck).] This assumes that a health check call should
> be cheap, but might not be.
> So calling /healthcheck too regularly can produce pressure for the underlying
> service (e.g. ActiveMQ) that could lead to resource waste or loss of
> reliability.
> I propose to cache the healthcheck results for WebAdmin (e.g. 5 seconds).
> What do you think?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
