From 9e60bae2f5ea8b3049fa74f302fd986b79faa03d Mon Sep 17 00:00:00 2001 From: Peter Wilson Date: Tue, 26 Mar 2024 13:54:37 +0000 Subject: [PATCH] attempt to improve description --- ...-vault-enterprise-perf-standby-logs-all-headers.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/partials/known-issues/1_15-audit-vault-enterprise-perf-standby-logs-all-headers.mdx b/website/content/partials/known-issues/1_15-audit-vault-enterprise-perf-standby-logs-all-headers.mdx index 8d9054f9a859..de2467ec66ec 100644 --- a/website/content/partials/known-issues/1_15-audit-vault-enterprise-perf-standby-logs-all-headers.mdx +++ b/website/content/partials/known-issues/1_15-audit-vault-enterprise-perf-standby-logs-all-headers.mdx @@ -6,12 +6,12 @@ #### Issue -Due to a bug in the Enterprise unsealing process, when using the new event framework Performance -Standby nodes in a Vault Enterprise cluster do not correctly receive configuration -providing them with the settings for which request headers should be written to the audit log. +Due to an issue in the new event framework, Performance Standby nodes in a Vault +Enterprise cluster do not correctly receive configuration regarding which request +headers should be written to the audit log. -Rather than no headers appearing in the audit logs, Vault Enterprise logs **all** -headers on Performance Standby nodes. +Rather than no headers appearing in the audit logs by default, Vault Enterprise +logs **all** headers on Performance Standby nodes. The header issue was resolved in `1.15.8`.