Often I am asked to trace a particular call what time it called, how long it queued, who answered it etc.
I have tried to work through the tserver log files on the server but these are difficult to follow, fill up quickly and due to the logging level set disappear of the system.
Does anyone have any suggestions on how to do this?
I don’t know if that would help you but I can provide you a log parser. What you can do then is for instance enter a ConnID and a set of TServer logfiles and then you get in a new file all the events corresponding to the given ConnID. This is then much easier to read then a raw logfile. You can also enter for instance a Skill and RequestAnswer and then you get all the calls answered for a given skill.
Of course you would need to set your log configuration so that it keeps enough logfiles on the disk.
Another simple alternative for tracing basic information about calls is to use the level “TRACE” of the logs writen by the router to the SCI. There you can see when an intercation was started and when and to whom it was routed.
Wow!!! Looking at the response… I think we all need a log parser. I had a very good friend of mine who is actually also posting here send me a copy of the one he has developed himself about a year ago in Access… you know who you are, so can I post it for everyone here?
I have sent the logparser I have to some people. But I don’t remember who got it and who didn’t because my mailbox exploded (seems quite popular this logparser :). So if anyone is interested just send me a new email ([email removed]).
An other interesting way of reading logfiles is to use syntax highlighting with a good text editor and a custom syntax highlighting file.
You can also use Kazimir, which is a T-Server parser that Genesys internally uses. They don’t support it, but it’s solid, and it’s pretty obvious how to use it. I’ve used it a lot.
Also, for less detailed call information, if your application generates Vista logs, you can read these logs (and it’s relatively easy to write a log parser for Vista logs – I’ve done so).