Just for you uber geeks out there the number that is placed in the database tables are actually binary..
Also be careful doing this since if you modify your database it can potentialy cause major issues.
Well, technically, ALL numbers stored in a digital computer are stored in binary. They can be REPRESENTED in different ways - as decimal numbers, as integers, as octal, as hexadecimal, etc.
I think what you REALLY mean is that they're bit-wise encoding, meaning that each bit stands for something. They're also known as "flags."
But in any case, I must say that information is very much appreciated. Now I'm going to have to write a short program to update that database and then see if I can write a script that will trigger that based on the overflow errors - or it could just work on a timer, but that would probably mean a much greater lag in resetting.
I've posted manytimes about the overflow issue. Kaseya had told me they were going to change the location of the event log filtering from the KServer to the local agent in the future. I'm assuming this will happen in V5.0 but I can't be sure.
So as of Friday afternoon I had resolved that I was going to solve this issuemyself. So you've savedme the time of reviewing the database and breaking down what fields where involved. Thank you.
Now the only issue is I have some systems with event log montoring and some without. So I'm looking in to writing a program to reset the values to a previously recorded state. This way having various event log settings would be possible.