Health check endpoint
A health check endpoint is a network-accessible API endpoint that reports a service’s health, availability, or readiness to handle requests.
Microservices Patterns, Second Edition
An endpoint that can be invoked to determine whether a service instance is healthy and available to handle requests.
- How it is used
- Supports service observability and lets a service registry verify instance health during service discovery.
- How deep it goes
- Defines the endpoint's purpose and registry invocation, but gives no implementation, response format, or health criteria.
- Examples
- Uses a service instance URL that a registry periodically invokes to verify health and request availability.
- What you can do after
- Operate service registration by exposing a URL that the registry can invoke periodically to check instance health and availability.
Read how Microservices Patterns, Second Edition explains health check endpoint →
Shipping Go: Develop, deliver, discuss, design, and go again
A health check endpoint is a network-accessible API endpoint that reports whether a service or deployed application is operating normally.
- How it is used
- Signals a long-running service’s status to its deployment platform so it can assess readiness, failures, and replacement.
- How deep it goes
- Works through a Go handler and deployment probe settings, while leaving dependency-aware checks as a design consideration.
- Examples
- Shows a JSON /health handler, App Engine check settings, and Kubernetes HTTP probes; contrasts a running API with an unwarmed cache.
- What you can do after
- Operate/configure it by registering /health and pointing liveness and readiness checks at an appropriate service signal.
GitHub Actions in Action: Continuous integration and delivery for DevOps
A health endpoint is an application endpoint that reports whether the application or a component is operational and ready to serve requests.
- How it is used
- Gates deployment progression until an installed application reports readiness, then supports monitored traffic shifts.
- How deep it goes
- Explains readiness and liveness roles and demonstrates polling JSON status, but defers application-side endpoint implementation.
- Examples
- Uses a curl-and-jq readiness loop and an Azure Web App staging-slot deployment validated with Playwright tests.
- What you can do after
- Operate/configure it as a deployment gate by polling readiness before tests or traffic routing and monitoring liveness during rollout.
Building Distributed Applications that Work
A health-check endpoint is an application endpoint that reports health or readiness information about the application.
- How it is used
- Lets Aspire monitor service health and delay dependent service startup until the API service is healthy.
- How deep it goes
- Works through host registration, HTTP mapping, aliveness filtering, and production caveats; leaves production endpoint protections scenario-specific.
- Examples
- Uses an API service’s `/health` registration, a live-tagged `/alive` mapping, and a startup exception visible in the dashboard.
- What you can do after
- Operate/configure it by exposing application endpoints, registering the health path in Aspire, and gating dependent service startup.
Read how Building Distributed Applications that Work explains health check endpoint →
Spring in Action, Sixth Edition
A health endpoint is an Actuator HTTP endpoint that returns the health status of an application and optionally its health-indicator details.
- How it is used
- Provides a quick HTTP-based check of application health and supports operational monitoring through Spring Boot Admin.
- How deep it goes
- Explains requests, JSON status, indicator details, path configuration, exposure, and security, but not custom health-indicator implementation.
- Examples
- Uses curl responses, YAML path and exposure settings, and MongoDB and disk-space health details.
- What you can do after
- Operate and configure the endpoint, inspect health JSON, change its base path, expose details, and control related endpoint exposure.
Read how Spring in Action, Sixth Edition explains health check endpoint →
Logs and Telemetry
A health endpoint is an HTTP endpoint that reports whether an application or service is operating normally.
- How it is used
- Connects application monitoring to Docker and Kubernetes container management through an HTTP health signal.
- How deep it goes
- Defines status semantics and Fluent Bit configuration, but does not detail response bodies beyond an optional ok value.
- Examples
- Uses the conventional /health path, a localhost health URL, Fluent Bit configuration, and curl requests.
- What you can do after
- Operate/configure Fluent Bit to expose and query an HTTP health endpoint for container or Pod checks.
Read how Logs and Telemetry explains health check endpoint →
Designing AI Systems
A health endpoint is an API endpoint that reports whether a service process is running or ready to receive traffic.
- How it is used
- Coordinates container startup, traffic routing, graceful shutdown, and last-resort restart recovery.
- How deep it goes
- Defines liveness and readiness behavior with HTTP statuses and lifecycle rationale, but stops short of implementation code.
- Examples
- Uses /health/live and /health/ready during initialization, request draining, failure recovery, and container removal.
- What you can do after
- Operate/configure service lifecycle checks that distinguish process failure from temporary unavailability.
Read how Designing AI Systems explains health check endpoint →
Also covered in
- Claude at WorkIn early access (MEAP)
- Kubernetes in Action, Second Edition
- Code Like a Pro in Rust
- Kubernetes for Developers
- Spring Microservices in Action
- Build and Orchestrator in Go (From Scratch)
What to know first
- HTTP status codeAn HTTP status code is a standardized three-digit code in an HTTP response that indicates the outcome of processing a request.
- serverA server is a computer system or software process that provides data, resources, or services to other systems, typically by responding to requests.
- productionProduction is the live operational setting in which a deployed software system serves its intended users or processes real workloads.
- RESTREST is an architectural style for distributed systems that organizes interactions around identifiable resources and their representations, using a uniform interface and constraints such as statelessness and cacheability.
Related concepts
- endpointkind of · An endpoint is an addressable interface of a service through which clients access a resource or invoke an operation, typically via a network request.
- Actuator endpointkind of · An Actuator endpoint is a Spring Boot Actuator management interface that exposes operational data or operations through supported communication mechanisms.
- liveness checkused by · A liveness check is an automated health test that determines whether a running workload remains functional or should be restarted.
Questions about health check endpoint
What is health check endpoint?
A health check endpoint is a network-accessible API endpoint that reports a service’s health, availability, or readiness to handle requests.
Which Manning books explain health check endpoint?
Microservices Patterns, Second Edition, Shipping Go: Develop, deliver, discuss, design, and go again, GitHub Actions in Action: Continuous integration and delivery for DevOps, Building Distributed Applications that Work, Spring in Action, Sixth Edition, Logs and Telemetry and Designing AI Systems.
What should I know before learning health check endpoint?
Manning books that teach health check endpoint usually introduce HTTP status code, server, production and REST first.
What kinds of health check endpoint are there?
Kinds of health check endpoint include liveness endpoint.
What is health check endpoint a kind of?
Health check endpoint is a kind of endpoint. An endpoint is an addressable interface of a service through which clients access a resource or invoke an operation, typically via a network request.
What is health check endpoint also called?
Health check endpoint is also called health endpoint.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.






