Genesys – Customize log events

Do you know that log events can be customized from version 7.6 in Genesys? Wait, what is this ‘log event customization’?

Simple. Genesys allows you to define log level for each log message and you can customize it per application.

Oh … but why do I need to customize log events?

To explain this, I will start with real case scenario. Recently, I got an assignment to review Genesys solution as they were getting default routed calls during busy period and implement/recommend methods to improve solution performance.

After identifying and solving configuration, routing strategy, reporting and staffing allocation issues, they were still getting default routed calls. At this point, this is as much as you can do within Genesys standard tools. Next, I developed tool to find ‘default routed calls’ for analysis (here) , which helped me to identify call patterns and fix issues -both technical and process.

For obvious reasons, customer like to use this tool functionality –  to identify default routed calls and don’t need other features like reporting & logging etc. I can develop server application (good for me) but it is overweight solution for this requirement and want to keep it simple.

Analyzing URS logs and log messages, I found that I can configure alarm condition for log message ’15-20003′ which will help to store Conn ID and timestamp for further analysis. Exactly what I want !!

URS Log Message

URS Log Message

But I dont want to recommend interaction level logging information to be stored in log database for this piece of information. I want to improve overall solution performance and interaction level logging to log database will increase network traffic 🙁

This is an ideal scenario to use ‘log event customization’ feature from Genesys. From 7.6 version onwards, we can customize this log event i.e) change level from ‘INTERACTION’ to ‘STANDARD’ and configured ‘STANDARD’ level logging to ‘network’.

Even though, 20003 log level message is ‘INTERACTION’ level logging, it will be reassigned dynamically and sent to Message server to store it in log database. For customer notification, I configured alarm condition for this log event and send email notification (How to send email notification?)

Problem solved 🙂

Update 24th Sep 2014 : Please visit post ‘Genesys – How to customize log events?’ for step by step guidance on configuring log event customization,

(Visited 58 times, 1 visits today)

Tagged: ,

Leave a Reply

Your email address will not be published. Required fields are marked *