Skip to content

[8.19] Clarify endpoints for checking EPR health/readiness in air-gapped environments #1889

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vishaangelova merged 1 commit into from
Feb 16, 2026
Merged

[8.19] Clarify endpoints for checking EPR health/readiness in air-gapped environments #1889

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/en/ingest-management/fleet/air-gapped.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,9 @@ docker run -it -p 8080:8080 \
--health-cmd "curl -f -L http://127.0.0.1:8080/health" \
docker.elastic.co/package-registry/distribution:{version}
----
+
You can use the `/health` or `/health?ready=true` API endpoints to check if EPR is ready to serve requests.
When either endpoint returns a `200` HTTP status code, the service is ready to handle requests.

[discrete]
[[air-gapped-diy-epr-kibana]]
Expand Down