paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 38 Packages Projects Releases Wiki Activity

Update plugins/catalog-backend/README.md

Browse Source 
Co-authored-by: Paul Schultz <pschultz@pobox.com>
Signed-off-by: Gustavo Lira e Silva <guga.java@gmail.com>
This commit is contained in:
Gustavo Lira e Silva
2025-05-09 10:57:04 -03:00
committed by GitHub
parent 8e0f15f6de
commit b85aeefdd5
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/catalog-backend/README.md
+2 -1
View File
@@ -94,7 +94,8 @@ 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).
- **Note:** By default, "low" severity audit events like `entity-fetch` aren't logged because they map to the "debug" level, while Backstage defaults to "info" level logging. To see `entity-fetch` events, update your `app-config.yaml` by setting `backend.auditor.severityLogLevelMappings.low: info`. See the [Auditor Service documentation](https://backstage.io/docs/backend-system/core-services/auditor/#severity-levels-and-default-mappings) for details on severity mappings.
Filter on `queryType`.