Indeed it is possible to use Log4J to produce your own functional log streams, separate from the domain logs. Whereas in this article I use the “Database” Sensor Action, you would use a custom Java sensor action. In this Java class, you can write to a Log4J log just like you would in any other Java class. All you need to do is choose an appropriate log category (i.e. the “name” of the logger), and configure the log4j config file on the server to use a different “appender” for log messages written to this logger. I have done this in the past, works like a charm. I had a generic mechanism to create the “log category” based on process name, activity name, trigger moment etc. This way, we could change log levels per process, activity etc.

I might even be able to retrieve some source code. You can contact me at myfirstname dot mylastname at amis.nl

The client I am working at is requiring us to “log” to their LOG4J logs (seperate from the DOMAIN logs). Can we route this information to another log4j logs? According to the Oracle Manual you can route it to a JAVA Class. We thought that we could establish a seperate log4j logger using a Java Class that we route all of our sensor actions. Have you or anyone else done that?

Ingrid

That’s quite nice! We could have used that in our workshop.
Just one remark…when adding a log statement to an existing assign operation it might be wise to add it as the first assign operation in the list. So when one of the following assign operation fails, at least your log message has been processed.