Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: DJM on July 23, 2009, 10:50:37 AM
-
Hi all
There is a specific log event (of confserv & csproxies) we want to store in the LogDB, which by default is a trace level event. We want to change this to a standard level, so it will be logged centrally.
We ideally don't want to change our logging levels, as this will result in about 10 apps now pumping all their trace messages to the LogDB.
Any changes to an lms file (which defines the log messages, their log levels, and log format) appear to result in "Unable to load Log Messages file...". There appears to be a checksum at the top of the file:
f096aba6|LMS|1.0|CONFSERV.lms|7.0.000|*
Has anyone ever managed to sucessfully modify an lms file ? Tier 1 Genesys support suggests no it's not possible, but just wondering if anyone else has any experience with this
Thanks
-
Hi,
I've never tried to modify LMS file and would consider it as a bit dangerous as nobody of us knows how it really works...
There is an easier and supported way how to achieve what you want. Message Server can be configured to exclude selected messages generated by particular application so such messages are not written into LogDB. Please check "Framework 7.6 Configuration Options Reference Manual" and search for the options "block-messages", "block-messages-from-<DBID>" and "block-messages-by-<type>"
R.
-
Hi René
Thanks very much for your response - I've taken a look at the documentation - that's definately an option, I can see there are about 30 trace messages in total we'd need to block
Thanks again