From 7d7a8024c1a388d44df271fe62ef773ba02cbb50 Mon Sep 17 00:00:00 2001 From: Robert Gogolok Date: Fri, 10 Oct 2025 16:54:29 +0200 Subject: [PATCH] Correct audit.app.crash to app.crash --- managing-cf/audit-events.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/managing-cf/audit-events.html.md.erb b/managing-cf/audit-events.html.md.erb index a1c40ee..4b310ee 100644 --- a/managing-cf/audit-events.html.md.erb +++ b/managing-cf/audit-events.html.md.erb @@ -281,7 +281,7 @@ For auditing and compliance reasons, some operators may wish to keep a record of ### Special events -- audit.app.crash +- app.crash - blob.remove\_orphan @@ -292,7 +292,7 @@ For example, a user issuing a `cf stop APP_NAME` command causes an `audit.app.st * **Service events** (`audit.service*`) are created after the service broker has approved an interaction. -* **Crash and rescheduling events** (`audit.app.crash`, `audit.app.process.crash|rescheduling`) are created when Diego marks an app instance as crashed or evacuates app instances from cells on Diego Cell VM restarts. +* **Crash and rescheduling events** (`app.crash`, `audit.app.process.crash|rescheduling`) are created when Diego marks an app instance as crashed or evacuates app instances from cells on Diego Cell VM restarts. * **Blob events** (`blob.remove_orphan`) are created by a daily clean up job and do not represent user action.