Polish "Provide health for an AbstractRoutingDataSource's resolved targets"
See gh-25708
This commit is contained in:
parent
13600c3367
commit
0a8da4fd7d
|
@ -1,5 +1,5 @@
|
|||
/*
|
||||
* Copyright 2012-2020 the original author or authors.
|
||||
* Copyright 2012-2021 the original author or authors.
|
||||
*
|
||||
* Licensed under the Apache License, Version 2.0 (the "License");
|
||||
* you may not use this file except in compliance with the License.
|
||||
|
|
|
@ -989,6 +989,15 @@ TIP: You can use `@Qualifier("groupname")` if you need to register custom `Statu
|
|||
|
||||
|
||||
|
||||
[[production-ready-health-datasource]]
|
||||
==== DataSource Health
|
||||
The `DataSource` health indicator shows the health of both standard data source and routing data source beans.
|
||||
The health of a routing data source includes the health of each of its target data sources.
|
||||
In the health endpoint's response, each of a routing data source's targets is named using its routing key.
|
||||
If you prefer not to include routing data sources in the indicator's output, set configprop:management.health.db.ignore-routing-data-sources[] to `true`.
|
||||
|
||||
|
||||
|
||||
[[production-ready-kubernetes-probes]]
|
||||
=== Kubernetes Probes
|
||||
Applications deployed on Kubernetes can provide information about their internal state with https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#container-probes[Container Probes].
|
||||
|
|
Loading…
Reference in New Issue