|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History![](../images/icons/arrow_right.png)
{gliffy:name=Log filesystems|size=M|version=4}
{note}This configuration requires to [change the default logging configuration|petalsesbsnapshot:Logging in Petals].{note}
{tip}Don't forget to monitor your file system sizes with a monitoring tool as Nagios{tip}
h2. Tuning your system
![](../images/icons/arrow_right.png)
The following log traces can be generated, and each have special characteristics that can influence the choose of the file system managing the file containing the log traces:
* global log traces flushes in \{{${petals.log.dir}/petals.log}}: few traces are written in a weighty file that can become very large,
* monitoring traces, including payload dumps of messages, are written as small files in a directory that will contain a lot of sub-directorie. So the file-system must be effective with small files and a bug number of sub-directories.
![](../images/icons/arrow_right.png)
{note}This configuration requires to [change the default logging configuration|petalsesbsnapshot:Logging in Petals].{note}
{tip}Don't forget to monitor your file system sizes with a monitoring tool as Nagios{tip}
{tip}Don't forget to monitor your file system sizes with a monitoring tool as Nagios{tip}
{color:red}TODO:{color}
** {color:red}select an efficient journaling [filesystem|http://en.wikipedia.org/wiki/File_system] to write small files to store MONIT log files and payload dumps,{color}
** {color:red}select an efficient journaling [filesystem|http://en.wikipedia.org/wiki/File_system] to write small files to store MONIT log files and payload dumps,{color}
![](../images/icons/arrow_right.png)