Hello! In the case of 1), I would recommend redirecting STDOUT to log file to make sure it is written to log.
In case of 2), I feel your pain but I'm not sure I have any practical recommendation. I tend to tweak my configurations until they work. IGNITE_QUIET should probably be false. Regards, -- Ilya Kasnacheev пт, 13 дек. 2019 г. в 01:22, Sabar Banks <sabar.ba...@prudential.com>: > Hello Ignite Team, > > Here at Prudential, we are leveraging Ignite as one of our IMDG business > solutions. I wanted to raise a question regarding the logging mechanism out > of the box. > > > > To be succinct: > > 1. Is there any way to enable Ignite to only write to a log file, and > maintain IGNITE_QUIET = true, and avoid using the console logger > (IGNITE_CONSOLE_APPENDER=false), when: > 1. The topology changes: Let say when a server node is spun up. Or > when a client connects and disconnects. > 2. When an error occurs in the cluster > 2. Is there a better way to prevent ignite from modifying a custom, or > stock, log4j2 configuration? > 1. We noticed, that if we put ignite in quiet mode, and try to > apply a stock Log4j2 implementation, ignite will suppress even our stock > log4j2 configuration, in our server application code. The only work > around > we’ve seen, is to disable the instantiation of the console logger in > ignite. However this causes us to lose logs pertaining to topology. > > > > From what we’ve been working with, it looks like you only get topology > logs at the info log level. This forces us to place ignite in verbose mode, > and write the console output to a log file. This has been negatively > affecting our runtimes, and also causing us to run out of disc space in our > server cluster. > > > > We are currently using version 2.5 of ignite, if that helps. > > > > Let me know if additional information is required. > > > > Thanks in advance. > > > > -Sabar > > > > > > Sabar Banks > Sys Analyst/Dev Associate > 973 - 802 - 5519 > sabar.ba...@prudential.com > > > > [image: cid:image001.png@01D2AC5E.3AD92BA0] > > >