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

apply requested changes

Browse Source 
Signed-off-by: Paul Schultz <pschultz@pobox.com>
This commit is contained in:
Paul Schultz
2025-01-13 12:30:16 -06:00
parent 1a0556f015
commit a4aa244fb7
32 changed files with 344 additions and 511 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/backend-system/core-services/auditor.md
-17
View File
@@ -85,20 +85,3 @@ When defining `eventId` and `subEventId` for your audit events, follow these gui
- Use `subEventId` to further categorize events within a logical group. For example, if the `eventId` is "fetch", the `subEventId` could be "by-id" or "by-location" to specify the method used for fetching.
- Avoid redundant prefixes related to the plugin ID, as that context is already provided.
- Choose names that clearly and concisely describe the event being audited.
## Configuring the service
The Auditor Service can be configured using the `backend.auditor` section in your `app-config.yaml` file.
### Console Logging
Console logging allows you to see audit events directly in your terminal output. This is useful for development and debugging purposes. To enable console logging, set the `enabled` flag to `true` within the `console` section:
```yaml
backend:
auditor:
console:
enabled: true
```
By default, console logging is enabled. You can disable it by setting the `enabled` flag to `false`.