After the Nebula environment we are deploying runs for a long time, the log files of graphd and storage are sometimes very large, tens to hundreds of GB, and there is a risk of filling up the disk.
We are using the Nebula V3.0.0 community edition, and there is no configuration parameter to control the total log file capacity and allow circular writing of log files in its manual, and there is no such configuration parameter in the latest V3.6.0 manual.
According to the posts in the community, the function of controlling the total capacity of log files can be realized through the logrotate software service. However, this solution is relatively limited and requires the logrotate software on the system, which is also troublesome.
I still hope that Nebula itself can provide this function. Both the Python and Java log libraries have this function, and the C++ log library should also have this function. Nebula should use this function and open it through configuration parameters.
