visual log analysis tool

[Vic]

Has anyone out there developed some type of log analysis tool that would siff through the log and for example draw a stick diagram for a particular call?

I think any one of us would be more than happy to get our hands on something like that pouring through the logs sometimes can be really really nnoying, especially if you have to do it everyday!

[Rory]

Vic,

Don't have anything as advanced as the stick diagram, but I did write something which ports the TServer log (v5.1) into an MS Access 2000 database. Haven't used it for some time and it probably would need some fine tuning (eg. error traping) however it did the job we needed. Have to write your own queries to analyse the data but at least it gets into a more legible format.

Rory

[Vic]

Hi, Rory,

it would be interesting to see it...
Can you drop me an email with more info?

If we have it in a databse, I am sure stick diagram would not that be THAT hard.... (I think..)

[Joe]

I'd be very interested in such a tool as well.

[Vic]

I think it would be interesting to see if we can pu together something.

I have some people here who can program, so if somebody can help me with putting together a design, we can probably do something that can benefit everyone.

What do you think?

[Stephen Keilholz]

I developed a Perl program which helps with log analysis. The basic idea was to parse the log file into a stream of events and report on only those events which matched the search criteria.
Here is some additional information:
-------------------------------
Usage: evgrep [i|I|e|E] pattern files
where i or I reports only unique ConnID records (all forms)
within events matching the pattern
e or E reports only event names (first line of event)
for matching events

Default mode is to report the entire content of each event in which the pattern is found. Id mode can be useful for identifying the ConnID based on another piece of information (i.e. ANI). Event mode can be useful for looking at the sequence of events without the associated detail.
-------------------------------
Two problems have come to my attention regarding this:
1. An associated event may not have the CONNID within it
2. Autosplitting of log files splits events causing the last part
of a split event to be missed.

Email me if further information is desired.
Stephen

[consultant]

can one of you guys share it with this group.

This is of immense importance to all the users in the Genesys community.

Thank you

[Vic]

I think you are right!
I have modified a program I have received from somebody else (you know who you are ) which works with G5.1.

IT is not visual but it writes both Events and Request for MERIDIAN AND SYMPOSIUM TServers only in one table. So if you want it, just email it to me. ( Note: for reason beyond my control, this program cannot be distributed here in Japan for free (like somebody would really pay for it! ) however, if you are abroad just email me and I will send it to you.

Vic

[Anthony]

Hi, I would also like a copy please...

[jack]

Hi VIC, can you send me one copy, thank you!

[eugene]

Vic, can you send me a copy as well.

Eugene

[Macca]

Have you tried using the Kazimir application that's available free of the Genesys Support website?
I creates something resembling a stick diagram in an Excel spreadsheet.
It's great to get the bare flow of call quickly in an easily readable format.