diff --git a/api/envoy/extensions/formatter/metadata/v3/metadata.proto b/api/envoy/extensions/formatter/metadata/v3/metadata.proto index 9b110a4893812..86b5053b1fdde 100644 --- a/api/envoy/extensions/formatter/metadata/v3/metadata.proto +++ b/api/envoy/extensions/formatter/metadata/v3/metadata.proto @@ -26,7 +26,7 @@ option (udpa.annotations.file_status).package_version_status = ACTIVE; // :ref:`Metadata ` info, // where TYPE is type of metadata (see above for supported types), // NAMESPACE is the filter namespace used when setting the metadata, KEY is an optional -// lookup up key in the namespace with the option of specifying nested keys separated by ':', +// lookup key in the namespace with the option of specifying nested keys separated by ':', // and Z is an optional parameter denoting string truncation up to Z characters long. // The data will be logged as a JSON string. For example, for the following ROUTE metadata: // diff --git a/docs/root/configuration/observability/access_log/usage.rst b/docs/root/configuration/observability/access_log/usage.rst index 383e6e12b1a84..1b6ba004befef 100644 --- a/docs/root/configuration/observability/access_log/usage.rst +++ b/docs/root/configuration/observability/access_log/usage.rst @@ -506,7 +506,7 @@ The following command operators are supported: HTTP :ref:`Dynamic Metadata ` info, where NAMESPACE is the filter namespace used when setting the metadata, KEY is an optional - lookup up key in the namespace with the option of specifying nested keys separated by ':', + lookup key in the namespace with the option of specifying nested keys separated by ':', and Z is an optional parameter denoting string truncation up to Z characters long. Dynamic Metadata can be set by filters using the :repo:`StreamInfo ` API: *setDynamicMetadata*. The data will be logged as a JSON string. For example, for the following dynamic metadata: @@ -541,7 +541,7 @@ The following command operators are supported: HTTP :ref:`Upstream cluster Metadata ` info, where NAMESPACE is the filter namespace used when setting the metadata, KEY is an optional - lookup up key in the namespace with the option of specifying nested keys separated by ':', + lookup key in the namespace with the option of specifying nested keys separated by ':', and Z is an optional parameter denoting string truncation up to Z characters long. The data will be logged as a JSON string. For example, for the following dynamic metadata: