From dc10fa5e25b357f366e07fa9cc71d6f223b5d824 Mon Sep 17 00:00:00 2001 From: Ronald Date: Tue, 20 Jun 2023 17:14:16 -0400 Subject: [PATCH] fix docs weirdness (#17827) --- .../content/docs/connect/config-entries/jwt-provider.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/connect/config-entries/jwt-provider.mdx b/website/content/docs/connect/config-entries/jwt-provider.mdx index f003106a3..8867a3e4f 100644 --- a/website/content/docs/connect/config-entries/jwt-provider.mdx +++ b/website/content/docs/connect/config-entries/jwt-provider.mdx @@ -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.