rohityadavcloud commented on code in PR #450:
URL:
https://github.com/apache/cloudstack-documentation/pull/450#discussion_r1816146418
##########
source/adminguide/management.rst:
##########
@@ -517,6 +517,29 @@ rules.
the global configuration.
+Managing log files
+------------------
+
+The log files are located in `/var/log/cloudstack`. This directory has the
+following subdirectories:
+
+- `management` for the Management Server
+- `usage` for the Usage Server
+- `agent` for the Agent for KVM hosts
+
+CloudStack uses log4j2 to manage log files. The log4j2 configuration file
+is located in the corresponding subdirectories in the `/etc/cloudstack/`
+directory and is named `log4j-cloud.xml`.
+
+By default, cloudstack uses `TimeBasedTriggeringPolicy` which rolls over
+the log file every day and are kept indefinitely. The log files are
+compressed and archived in the same directory.
+
+Over time, the logs can fill up the entire disk space. To avoid this, you can
+update the log4j-cloud.xml file to change the log file rollover and retention
+policy. You can checkout some configuration recipes from the log4j2
documentation
+`here
<https://logging.apache.org/log4j/2.x/manual/appenders/rolling-file.html#recipes>`_.
Review Comment:
Should we give an entire example, on how do this? For example change from
time based to size based?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
