OnDemand Users Group

Support Forums => CMOD for Multiplatforms => Topic started by: jsquizz on February 01, 2018, 06:49:12 PM

Title: 65/226 Message logging -- excessive
Post by: jsquizz on February 01, 2018, 06:49:12 PM
Hi all,

I was part of a major issue a few years ago on 8.4 where we had 65 and 226 messages turned on for every app group in production. It caused slowness and crazy instability. I believe there was a tech note for this, or it may have been a PMR we opened.

does anyone have more information on this? We are logging 100k+ a day :(
Title: Re: 65/226 Message logging -- excessive
Post by: Justin Derrick on February 01, 2018, 07:42:20 PM
It can be a problem because you're writing so many messages into the System Log, and eventually every server hits it's limit.

Depending on the regulations you need to comply with, you may actually need to keep all these messages.  If that's the case, then you need to make the database faster, possibly by moving up to SSDs for the database and transaction log filesystems.

Normally, I recommend you keep all logging turned on, but just keep that data for a shorter period of time.

If you want to keep all the log data, you can use the logging exit, and use some custom code to write the log data you need to keep (but don't necessarily want in the system log).  The snag here is that there are limitations to the number of times you can write to a file per second as well.

-JD.