我的书签
添加书签
移除书签14.2.3 The Health Endpoint
The health endpoint returns information about the “health” of the application. The application health is determined by any number of “health indicators”.
To execute the health endpoint, send a GET request to /health.
14.2.3 The Health Endpoint
- 1 Introduction
- 2 Quick Start
- 3 Inversion of Control
- 3.1 Defining Beans
- 3.2 How Does it Work?
- 3.3 The BeanContext
- 3.4 Injectable Container Types
- 3.5 Bean Qualifiers
- 3.6 Scopes
- 3.7 Bean Factories
- 3.8 Conditional Beans
- 3.9 Bean Replacement
- 3.10 Bean Configurations
- 3.11 Life-Cycle Methods
- 3.12 Context Events
- 3.13 Bean Events
- 3.14 Bean Introspection
- 3.15 Bean Validation
- 3.16 Bean Annotation Metadata
- 3.17 Micronaut Beans And Spring
- 3.18 Android Support
- 4 Application Configuration
- 5 Aspect Oriented Programming
- 6 The HTTP Server
- 6.1 Running the Embedded Server
- 6.2 Running Server on a Specific Port
- 6.3 HTTP Routing
- 6.4 Simple Request Binding
- 6.5 Host Resolution
- 6.6 Client IP Address
- 6.7 The HttpRequest and HttpResponse
- 6.8 Response Status
- 6.9 Response Content-Type
- 6.10 Accepted Request Content-Type
- 6.11 Reactive HTTP Request Processing
- 6.12 JSON Binding with Jackson
- 6.13 Data Validation
- 6.14 Serving Static Resources
- 6.15 Error Handling
- 6.16 API Versioning
- 6.17 Handling Form Data
- 6.18 Writing Response Data
- 6.19 File Uploads
- 6.20 File Transfers
- 6.21 HTTP Filters
- 6.22 HTTP Sessions
- 6.23 Server Sent Events
- 6.24 WebSocket Support
- 6.25 HTTP/2 Support
- 6.26 Server Events
- 6.27 Configuring the HTTP Server
- 6.28 Server Side View Rendering
- 6.29 OpenAPI / Swagger Support
- 6.30 GraphQL Support
- 7 The HTTP Client
- 7.1 Using the Low-Level HTTP Client
- 7.2 Proxying Requests with ProxyHttpClient
- 7.3 Declarative HTTP Clients with @Client
- 7.4 HTTP Client Filters
- 7.5 HTTP Client Sample
- 8 Cloud Native Features
- 8.1 Cloud Configuration
- Using Cloud Instance Metadata
- 8.1.1 Distributed Configuration
- 8.1.2 HashiCorp Consul Support
- Starting Consul
- Enabling Distributed Configuration with Consul
- Storing Configuration as Key/Value Pairs
- Storing Configuration in YAML, JSON etc.
- Storing Configuration as File References
- 8.1.3 HashiCorp Vault Support
- 8.1.4 Spring Cloud Config Support
- 8.1.5 AWS Parameter Store Support
- 8.1.6 Oracle Cloud Vault Support
- 8.2 Service Discovery
- 8.3 Client Side Load Balancing
- 8.4 Distributed Tracing
- Jaeger Configuration
- 8.1 Cloud Configuration
- 9 Serverless Functions
- 10 Message-Driven Microservices
- 11 Standalone Command Line Applications
- 12 Configurations
- 12.1 Configurations for Reactive Programming
- 12.2 Configurations for Data Access
- 12.2.9 Configuring Flyway
- 13 Language Support
- 14 Management & Monitoring
- 14.1 Creating Endpoints
- 14.2 Built-In Endpoints
- Getting information about a particular PropertySource
- 15 Security
- 16 Multi-Tenancy
- 17 Micronaut CLI
- 18 Appendices
暂无相关搜索结果！
本文档使用 BookStack 构建
