Sometimes due to some reasons my log file is filled with some big amount of records - and it seems that the “max_entries” does not work:
system_log:
max_entries: 200
And at least twice I observed a situation when the Log file became too large.
I believed that this “max_entries” is a kind of “safety” to prevent a situation like I described.
Created an issue here:
opened 04:08AM - 23 Dec 22 UTC
integration: system_log
### The problem
Running HA in Container on a host with 32GB SD memory.
At le… ast twice I observed an issue:
- log files became very large,
- no free space was left on SD,
- recorder stopped working.
Here the log file became > 6GB:
My config:
```
system_log:
max_entries: 200
fire_event: true
```
I believed that no more than 200 entries will be saved in the Log.
Seems that `max_entries` does not work.
Earlier I sometimes noticed too that amount of rows in Log is larger than 200; but it was not crucial for me - before I faced THIS HUGE amount.
It is clear that the Log should not be filled with such amount of errors/warnings - that I should find a reason of these errors/warnings in my setup. But the point of this issue is "Why max-enties does not work?".
### What version of Home Assistant Core has the issue?
2022.12.7
### What was the last working version of Home Assistant Core?
_No response_
### What type of installation are you running?
Home Assistant Container
### Integration causing the issue
System Log
### Link to integration documentation on our website
https://www.home-assistant.io/integrations/system_log/
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
