Feature Request: Ability to support multiple log directories about loggerpro HOT 2 CLOSED

Hi, why don't append you logs directly to your ELK stack? There is the LoggerPro.ElasticSearchAppender.pas which is designed on purpose. If this is not viable for you, we can surely promote some private methods to virtual, but that doesn't sole the problem because you need a method to "close" a file when the request is terminated (a.k.a. "at the last log line of that request"). That could be done in a middleware. Another approach could be to append your logs in a redis instance and then use Logstash, or other specific software, to do ingestion into elasticsearch. With you don't have any problem about the number of files. There are many different solutions, I don't know the system, but IMHO overriding a method in the FileAppender is not enough. Let me know what you think.

from loggerpro.

Thanks Daniele. I'll look at the ElasticSearchAppender once we've got the ELK stack up and running.

On the interim I have subclassed the TLoggerProFileAppenderManaged so it can deal with a file per GUI and writes to a sub directory created from the first two characters of the GUID (16x16 possible sub directories)

This issue can be closed

from loggerpro.