Skip to content

Commit 39d6d27

Browse files
Mik Vyatskovk8s-ci-robot
authored andcommitted
Fix stage names in audit logging documentation (#7746)
Signed-off-by: Mik Vyatskov <[email protected]>
1 parent a4af6f5 commit 39d6d27

File tree

1 file changed

+1
-1
lines changed
  • docs/tasks/debug-application-cluster

1 file changed

+1
-1
lines changed

docs/tasks/debug-application-cluster/audit.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -147,7 +147,7 @@ The following flags are used only in the `batch` mode.
147147
Parameters should be set to accommodate the load on the apiserver.
148148

149149
For example, if kube-apiserver receives 100 requests each second, and each request is audited only
150-
on `StageResponseStarted` and `StageResponseComplete` stages, you should account for ~200 audit
150+
on `ResponseStarted` and `ResponseComplete` stages, you should account for ~200 audit
151151
events being generated each second. Assuming that there are up to 100 events in a batch,
152152
you should set throttling level at at least 2 QPS. Assuming that the backend can take up to
153153
5 seconds to write events, you should set the buffer size to hold up to 5 seconds of events, i.e.

0 commit comments

Comments
 (0)