fix docs weirdness (#17827)
This commit is contained in:
parent
72409898bc
commit
dc10fa5e25
|
@ -954,9 +954,7 @@ Defines behavior for caching the validation result of previously encountered JWT
|
|||
|
||||
## Metrics
|
||||
|
||||
The following `envoy` metrics can be used to track jwt authentication details.
|
||||
|
||||
~> **Note:** Envoy does not currently provide any documentation on these metrics.
|
||||
Envoy proxies expose metrics that can track JWT authentication details. Use the following Envoy metrics:
|
||||
|
||||
```yaml
|
||||
http.public_listener.jwt_authn.allowed
|
||||
|
@ -968,6 +966,8 @@ http.public_listener.jwt_authn.jwt_cache_hit
|
|||
http.public_listener.jwt_authn.jwt_cache_miss
|
||||
```
|
||||
|
||||
~> **Note:** Currently, Envoy does not reference these metrics in their documentation. Refer to [Envoy documentation](https://www.envoyproxy.io/docs/envoy/latest/) for more information about exposed metrics.
|
||||
|
||||
## Examples
|
||||
|
||||
The following examples demonstrate common JWT provider configuration patterns for specific use cases.
|
||||
|
|
Loading…
Reference in New Issue