Feature Discussions

[king]

Dear community,

FirstSpirit offers its own log4j-specific FirstSpirit appender named "de.espirit.firstspirit.server.logging.FSAppender". Details for its configuration possibilities see "FirstSpirit Manual for Administrators", chapter "Logging configuration".

A default example configuration is offered with the installation of FirstSpirit. It can be found below "fs-logging.conf".

log4j.appender.fs=de.espirit.firstspirit.server.logging.FSAppender
log4j.appender.fs.consoleLogging=false
log4j.appender.fs.plainLogging=true
# dated logging is used by web montior for log file display
log4j.appender.fs.datedLogging=true
log4j.appender.fs.maxFileSize=1024MB
log4j.appender.fs.buffer=8192
log4j.appender.fs.flushCycle=10

The problem: when using and relying on an external and professional log rotate framework like "logrotate" that does allow rotating not only Java-specific logs, it might be very helpful when it could be possible to completely deactivate the log4j specific logrotation within this custom appender.

Up to now, this is not possible!

This feature request votes for an introduction of an additional attribute to allow that explicitly! Additionally, it has to be ensured, that the search functionality within the FirstSpirit server monitoring would continue working (detail see "FirstSpirit Manual for Administrators") - even when relying on an external logrotate framework. Either by specify which suffixes have to be used (numerical or timestamp based).

[king]

Dear e-Spirit core development team, Dear Peter Jodeleit,

wouldn't it be an argument to ease disabling FirstSpirit logrotation in "FSAppender" configurations instead of forcing the customer to realize its own log4j-Appender implementation?

For sure, the log file naming and content conventions have to be guaranteed by the external tool. Here, it would be just an additional directive located in the FirstSpirit standard core product - where on the other hand a separate implementation has to be maintained and integrated.

So, the central arguments are:

- standardization of log rotation via "logrotate" (currently in use for Apache, Tomcat, etc.)

- centralization of log rotate configurations in a single tool

[MichaelaReydt]

Hello Holger

thank you for your idea to improve FirstSpirit. It is important for us to learn from the experiences of our customers and partners. For this reason we appreciate feedback and any suggestion.

We have evaluated the issue once again, but have no plans for a realization in the near future. Therefore, we cannot consider your feature request at this time.

You can find more details about our feature selection process in our Features Policy.

Best regards

Michaela