Analyze logs

[mgcristino]

Hi,

i'm using genesys troubleshooting utilities for log analyzis, but i need to customize this analyzis. Does anyone know or have or was hable to decode genesys utilities? As far as i understand genesys troubleshooting utilities are perl applications, but i don't know how the utilities process the logs.

Could someone help me?


Best Regards,

[cavagnaro]

That is something called reverse engineering and is against any software protection copyright, I believe no one here can help on that. Remember we are under Genesys eyes, so be carefull with your requests.
Ask Genesys directly if they can help you or contact the developer directly.

[mgcristino]

Sorry for giving a wrong ideia with my comment about "decode genesys utilities",  i pretend to ask if someone was hable to generate the same information with another process or aplication.

i'll ask Genesys directly if they could help me.

Thanks.

[Mike Kamlet]

Log file formats are failr easily parsed with Perl, awk, etc

We have written a number of utilities that grab messages from logs for various purposes.

[eu4iacz]

I agree that unix is enough. Than you can analyze your logfiles in easiest way, when you know what to look for in it:-). When you have Win apps you can install unx tools and you can analyze too :-). awk, sed or perl scripts can be used.
[quote author=Mike Kamlet link=topic=2857.msg11508#msg11508 date=1205932117]
Log file formats are failr easily parsed with Perl, awk, etc

We have written a number of utilities that grab messages from logs for various purposes.
[/quote]

[S]

I think kazimir is good tool for troubleshooting logs and so is the other tool- don't remember the name though, TServerlogparser??

[victor]

[quote author=Mike Kamlet link=topic=2857.msg11508#msg11508 date=1205932117]
Log file formats are failr easily parsed with Perl, awk, etc

We have written a number of utilities that grab messages from logs for various purposes.
[/quote]

Hi, Mike,

would you mind sharing them with the rest of us? Right now, I am using a combination of awk, sed and grep to get things done, because Genesys default tools are simply not getting the job done. I have a suspicion that this is done on purpose to get some extra cashflow for their PS. Of course, given the demand for it, who can blame them?

Best regards,
Vic

[Mike Kamlet]

Here's a sample of what I've built --

This script allows the user to pull all (or specific) events/requests from multiple log files (they can be zipped as well) that meet specific criteria.

Examples:  Find all Queued/Diverted events for specific queue
              Find all events for a call with a given customer account #