Skip to content

Conversation

@levinster82
Copy link

Size-based rotation:

  • When frigate.log reaches 100MB, it rotates immediately

Time-based rotation:

  • Daily at midnight (default logback behavior)

How it works:

  1. During operation: If the file hits 100MB, it gets rotated right away to frigate.YYYY-MM-DD.0.log.gz
  2. Daily: Even if the file is smaller than 100MB, it rotates at midnight to frigate.YYYY-MM-DD.0.log.gz
  3. Multiple rotations per day: If the file hits 100MB multiple times in one day, you get frigate.YYYY-MM-DD.0.log.gz, frigate.YYYY-MM-DD.1.log.gz, etc.

Cleanup:

  • Keeps 30 days of rotated logs
  • Maximum 3GB total log storage
  • Old files are automatically deleted

## Size-based rotation:
- When frigate.log reaches 100MB, it rotates immediately

## Time-based rotation:
- Daily at midnight (default logback behavior)

## How it works:
1. **During operation**: If the file hits 100MB, it gets rotated right away to `frigate.YYYY-MM-DD.0.log.gz`
2. **Daily**: Even if the file is smaller than 100MB, it rotates at midnight to `frigate.YYYY-MM-DD.0.log.gz`
3. **Multiple rotations per day**: If the file hits 100MB multiple times in one day, you get `frigate.YYYY-MM-DD.0.log.gz`, `frigate.YYYY-MM-DD.1.log.gz`, etc.

## Cleanup:
- Keeps 30 days of rotated logs
- Maximum 3GB total log storage
- Old files are automatically deleted
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant