From d4b59ff1ea566d0635a4269a015e43d54238df47 Mon Sep 17 00:00:00 2001 From: wiktor2200 Date: Tue, 12 Jul 2022 07:30:44 +0200 Subject: [PATCH] chore(docs): custom and built-in event logging class at the same time (#20098) * chore: custom and built-in event logging class at the same time * fix whitespaces * Update Event Logging docs --- docs/docs/installation/event-logging.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/docs/installation/event-logging.mdx b/docs/docs/installation/event-logging.mdx index 7b9bba1de4..2cb35d5047 100644 --- a/docs/docs/installation/event-logging.mdx +++ b/docs/docs/installation/event-logging.mdx @@ -9,9 +9,11 @@ version: 1 ### Event Logging -Superset by default logs special action events in its internal database. These logs can be accessed +Superset by default logs special action events in its internal database (DBEventLogger). These logs can be accessed on the UI by navigating to **Security > Action Log**. You can freely customize these logs by implementing your own event log class. +**When custom log class is enabled DBEventLogger is disabled and logs stop being populated in UI logs view.** +To achieve both, custom log class should extend built-in DBEventLogger log class. Here's an example of a simple JSON-to-stdout class: