[BUG] [EagleEye][INFO] Log file rolled over by outside: ?/logs/eagleeye/eagleeye-self.log, force reload

## Issue Description
[EagleEye][INFO] Log file rolled over by outside: ?/logs/eagleeye/eagleeye-self.log, force reload
[EagleEye][ERROR] Fail to mkdirs: /app/?/logs/eagleeye
Type: *bug report*

### Describe what happened
服务是部署在公司的k8s环境里的，但是pod的磁盘设置了只读权限，所以报错，希望能禁用该日志或输出到控制台

### Describe what you expected to happen

### How to reproduce it (as minimally and precisely as possible)

1.
2.
3.

### Tell us your environment
版本：2.0.0-alpha

### Anything else we need to know?
我想关闭该日志，请问应该如何操作？

Start by reproducing the EagleEye log rollover failure in a Kubernetes pod with a read-only disk, using the reported 2.0.0-alpha environment. Trace the configuration or entry point responsible for /logs/eagleeye/eagleeye-self.log and determine whether the requested outcome is disabling this log or redirecting it to the console; done means the chosen behavior works without mkdir or rollover errors.

Written by the indexing model from the issue text.