Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions src/pages/manage/reverse-proxy/access-logs.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,29 @@ Access logs support several operational and security workflows:
- **Monitoring** - Track usage patterns across your services. Identify which services receive the most traffic, peak usage times, and unusual access patterns that may warrant investigation.
- **Compliance** - Maintain records of service access for regulatory requirements. Access logs provide an auditable trail of who accessed what, when, and from where.

## Retention and Cleanup

For the cloud version of NetBird, access logs are retained for 7 days.
For the self-hosted version, access log retention can be configured in the `management.json` or `config.yaml` by setting the following config parameters:

```json
{
"ReverseProxy": {
"AccessLogRetentionDays": 7,
"AccessLogCleanupIntervalHours": 24
}
}
```

```yaml
reverseProxy:
accessLogRetentionDays: 7
accessLogCleanupIntervalHours: 24
```

- **accessLogRetentionDays** - Define how long access logs are retained before they are automatically deleted.
- **accessLogCleanupIntervalHours** - Set how often the system checks for and deletes expired access log entries.

## Related pages

- [Reverse Proxy Overview](/manage/reverse-proxy) - learn how to create and manage reverse proxy services
Expand Down
Loading