How can I force OTRS to stop logging errors in SQL databases

[otrssimpleuser]

Dear all,
I would like to know what am I doing wrong here to force OTRS to stop logging any errors in the database.

The error logs (and only error logs) are stored in the MySQL table : gi_debugger_entry_content.
I would like to NOT store anything at all in the table.
As 'error' is the minimum level of the log mechanism in OTRS, here, there is no solution to NOT store any logs.

Potential solution I've found:
GenericInterface -> GenericInterface::Operation::ResponseLoggingMaxSize
Set the value to '0' in order to force OTRS to write a maximum of 0 KB into the gi_debugger_entry_content table.

But I don't understand why error logs coming from GenericInterface are still being written in the table..
Any idea or suggestion ?
Thanks in advance !

P.S : Upgrading the OTRS version will not be possible

[jojo]

The GI debugger log is mandatory. All other logs are not stored in Database.

Why an update is not possible? You are using a very old and really unsecure version which can be compromised or destroyed by email.

[otrssimpleuser]

Can't update because OTRS is linked to an other tool, using this precise version of OTRS.
I'm afraid that, if I update OTRS, the other tool won't work anymore

[jojo]

well, if you can take the risk of beeing compromiseable and the loss of data...

[otrssimpleuser]

Any other suggestion ?

[jojo]

what is the name of the blocking tool? Who is the vendor?