From 9b5f7066c81ccb03881bb3eaae1c1d5dc36f9f8a Mon Sep 17 00:00:00 2001 From: Billy Tat Date: Mon, 30 Aug 2021 11:47:28 -0700 Subject: [PATCH] Update content/rancher/v2.6/en/troubleshooting/userid-tracking-in-audit-logs/_index.md --- .../en/troubleshooting/userid-tracking-in-audit-logs/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.6/en/troubleshooting/userid-tracking-in-audit-logs/_index.md b/content/rancher/v2.6/en/troubleshooting/userid-tracking-in-audit-logs/_index.md index 88b46b89cde..e6150b18bf8 100644 --- a/content/rancher/v2.6/en/troubleshooting/userid-tracking-in-audit-logs/_index.md +++ b/content/rancher/v2.6/en/troubleshooting/userid-tracking-in-audit-logs/_index.md @@ -20,4 +20,4 @@ A Rancher Admin should now be able to view Rancher audit logs and follow through ### Feature Description - When Kubernetes Audit logs are enabled on the downstream cluster, in each event that is logged, the external Identity Provider's username is now logged for each request, at the "metadata" level. -- When Rancher API Audit logs are enabled on the rancher installation, the external Identity Provider's username is also logged now at the "auditLog.level=1" for each request that hits the Rancher API server, including the login requests. +- When Rancher API Audit logs are enabled on the Rancher installation, the external Identity Provider's username is also logged now at the `auditLog.level=1` for each request that hits the Rancher API server, including the login requests.