From cec9d71da167842b75e85c70ac6c477a7252718c Mon Sep 17 00:00:00 2001 From: Romuald Lemesle Date: Thu, 2 Jul 2026 09:27:59 +0200 Subject: [PATCH] fix(openaev): align healthcheck on application-level /api/health endpoint Replaces the generic Spring Boot Actuator liveness ping (`/actuator/health/ping`) with OpenAEV's own application health endpoint (`/api/health?health_access_key=`), consistent with: - OpenAEV-Platform/docker's docker-compose.yml - The pattern already used for OpenCTI in this same file (`/health?health_access_key=${OPENCTI_HEALTHCHECK_ACCESS_KEY}`) The actuator ping only proves the JVM process is alive; it does not check that OpenAEV's dependencies (DB, MinIO, RabbitMQ, ES) are actually reachable, which is what `depends_on: condition: service_healthy` consumers (xtm-composer, collectors, injectors) actually need. `OPENAEV_HEALTHCHECK_KEY` is already defined and injected into the `openaev` service environment, so no new secret is introduced. `retries` aligned to 20 to match OpenAEV-Platform/docker; `start_period: 120s` kept since this is now a real app-level readiness check (DB/ES/MinIO init) rather than a JVM liveness ping, which needs more warm-up time than actuator did. --- docker-compose.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 266220f..cb8068b 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -446,10 +446,10 @@ services: condition: service_healthy restart: always healthcheck: - test: [ "CMD", "wget", "-qO-", "http://openaev:8080/actuator/health/ping" ] + test: [ "CMD", "wget", "-qO-", "http://openaev:8080/api/health?health_access_key=${OPENAEV_HEALTHCHECK_KEY}" ] interval: 10s timeout: 5s - retries: 30 + retries: 20 start_period: 120s ###########################