Have used an enhanced version of the LIBAJC WriteLog function for years to log relevant information and make troubleshooting easier.
WriteLog is rather basic and has a heap of limitations (like can't reliably write to same file from two drivers, no rotation if the file gets very big and so on).
Wondering if others have experimented here. Not after auditing per-se. This is purely a what happened "summary" type logging for troubleshooting operational issues.
However saw that had played with calling Log4J from IDM - but do not want to go down the JAR path if I don't have to.
Have tested a little with an ECMAScript version of this code. I like the idea of this approach as these JARs ship with IDM.
However there are some downsides with this.
- Log4J is EOL, replaced 4 years back by Log4J2 (which doesn't ship with IDM)
- The DailyRollingFileAppender has known issues, which means one needs to use Apache Extras For Apache Log4j in addition.
Anyone delved into this area and willing to share their experiences (potentially also some ecma code) ?