add note about visibility of entity-fetch audit events in logs
add clarification about visibility of entity-fetch audit events in logs Signed-off-by: Gustavo Lira <guga.java@gmail.com>
This commit is contained in:
@@ -0,0 +1,5 @@
|
||||
---
|
||||
'@backstage/plugin-catalog-backend': patch
|
||||
---
|
||||
|
||||
"Added a note clarifying that `entity-fetch` audit events are not visible by default in the logs and are only displayed when the log severity level is adjusted."
|
||||
@@ -94,6 +94,7 @@ The Catalog backend emits audit events for various operations. Events are groupe
|
||||
**Entity Events:**
|
||||
|
||||
- **`entity-fetch`**: Retrieves entities.
|
||||
- **Note:** By default, `entity-fetch` audit events are not visible in the log output. This is because these events are classified with a severity level of "low", which maps to the "debug" log level. The default log level in Backstage is "info", so debug-level events (severity "low") are filtered out. To see `entity-fetch` events in the logs, adjust the Auditor Service configuration by setting `backend.auditor.severityLogLevelMappings.low` to `info` in your `app-config.yaml`. For more information, refer to the [Auditor Service documentation on severity levels and default mappings](https://backstage.io/docs/backend-system/core-services/auditor/#severity-levels-and-default-mappings).
|
||||
|
||||
Filter on `queryType`.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user