Yes, this is what I did. Pulling this from memory, so I might be slightly off on the exact commands used.
1. I deleted the `log4j.properties` file from the Metron REST jar. I believe I used `zip -d ...`. 2. I created my own log4j properties file. Something like... `/usr/metron/0.4.1/config/log4j/metron-rest/log4j.properties` 3. I then added `-Dlog4j.properties=/usr/metron/0.4.1/config/log4j/metron-rest/log4j.properties` as a JVM argument in one of the properties in /etc/sysconfig/metron. I think ultimately, we don't want to ship a log4j properties file in the JAR itself. On Fri, Jul 14, 2017 at 9:52 AM, Ryan Merriman <[email protected]> wrote: > The only way I know of is to change log4j.properites. Did you every figure > out a better way? > > On Tue, Jul 11, 2017 at 2:10 PM, Nick Allen <[email protected]> wrote: > > > How do I configure logging for Metron REST on a deployed host? > > > > Right now a log4j.properties file gets packaged into the metron-rest JAR > > itself. Is there is an easy way that I am missing? > > >
