Skip to content

Commit 9e025df

Browse files
committed
Document on how to manage log files
1 parent 4c789e1 commit 9e025df

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

source/adminguide/management.rst

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -517,6 +517,29 @@ rules.
517517
the global configuration.
518518

519519

520+
Managing log files
521+
------------------
522+
523+
The log files are located in `/var/log/cloudstack`. This directory has the
524+
following subdirectories:
525+
526+
- `management` for the Management Server
527+
- `usage` for the Usage Server
528+
- `agent` for the Agent for KVM hosts
529+
530+
CloudStack uses log4j2 to manage log files. The log4j2 configuration file
531+
is located in the corresponding subdirectories in the `/etc/cloudstack/`
532+
directory and is named `log4j-cloud.xml`.
533+
534+
By default, cloudstack uses `TimeBasedTriggeringPolicy` which rolls over
535+
the log file every day and are kept indefinitely. The log files are
536+
compressed and archived in the same directory.
537+
538+
Over time, the logs can fill up the entire disk space. To avoid this, you can
539+
update the log4j-cloud.xml file to change the log file rollover and retention
540+
policy. You can checkout some configuration recipes from the log4j2 documentation
541+
`here <https://logging.apache.org/log4j/2.x/manual/appenders/rolling-file.html#recipes>`_.
542+
520543
Stopping and Restarting the Management Server
521544
---------------------------------------------------
522545

0 commit comments

Comments
 (0)