I downloaded the data-prepper docker image (latest version): docker pull opensearchproject/data-prepper:latest
If i run the container, this works. In particular with the following logs:
data-prepper | 2022-12-12T16:51:35,428 [main] INFO org.opensearch.dataprepper.plugins.source.oteltrace.OTelTraceSource - Started otel_trace_source on port 21890.
data-prepper | 2022-12-12T16:51:35,438 [main] INFO org.opensearch.dataprepper.pipeline.server.DataPrepperServer - Data Prepper server running at :4900
If I do a GET to http://localhost:21890 I get error 404.
My problem is the health check. I took this docker to AWS to try and make some configurations, but unfortunately the health check process on AWS always fails.
I found this bug on the official GitHub page but unfortunately I couldn’t find a correct path that causes the API to go 200 OK (in order to have a valid healthcheck).
Do I need to add some Docker configuration to fix this problem?
Hi @ddpowers ,
Even editing the pipelines.yaml configuration file doesn’t solve the problem.
The problem I have is the following:
I’m working on AWS ECS and I’m trying to set up a task with data-prepper Docker image inside, but the associated AWS Target Group healthcheck is always indicated as unhealthy.
This happens because all HTTP calls to the container (which are made automatically by AWS) result in a 404 or 401.
How can I edit the files so that I can get a correct healtcheck HTTP call that results in 200 OK?