Howdy All,
I suppose this is a two part question. Thank you for reading!
A few weeks back we had a planned power outage. After the outage, the LT_TNEW_SESSION_LOG table started populating with a ton of seemingly useless debug info. The table states that the 'log_level' is set to 'debug'. This is causing a extreme growth in this table and bogging down SQL back ups. I'm not entirely sure *how* debug level got flipped on which is what makes this a two parter:
First, is there something could cause to log level to automatically set to debug? Is it possible something didn't come up correctly after the power outage that forced a debug state? Haven't really encountered any issues in Tessitura/TNEW since and I haven't found anything that stood out but, the logs are nightmare to get through in debug so I might be missing something. Databases are consistent and healthy.
Second, how do I turn down the TNEW logging levels? My search through the documentation has not borne fruit.
Thank you very much for any insights you might have!
Hello Jason! This is Kelsey with Tessitura Network Support. I can see from our records that you also created a Support ticket for this matter:We discovered that only Super Admin users have access to turn off trace logging for your TNEW Admin site, which we confirmed didn't seem to be the issue in this case. As discussed, for future reference, you'll go to Site Data > Component Editor > Configuration: Logging and switch the Trace Logging Enabled to False. We also verified your logging was set to the correct levels and that there should be a job scheduled to purge LT_TNEW_SESSION_LOG.
We then discovered that within the LTR_TNEWCUSTOM_WEB_DEFAULTS table the "debug_mode_is_enabled" item name value was set to "Y". You then were able to change that to "N". You then performed a TNEW Cache Clear on your TNEW Admin site and you then confirmed that the LT_TNEW_SESSION_LOG stopped filling with data!
If you have any additional follow-up, questions, or concerns though, please let us know any time.