Webtrends: export detailed server errors

possible?

[followgreg]

I was wondering if there is a way to export a list of files generating errors from the Webtrends.

Example: For a server generating http 500 errors >> I would export all files generating these errors returning HTTP 500?
Note: I have no server error logs...which is the reason why I'm asking if I can do the above.

Not sure if my question is clear but I hope someone can help :)

..

[followgreg]

Am I alone on this one? :)

[cgrantski]

If you have no server logs, then what you have is SDC logs?

[followgreg]

I actually have server logs, just that I have no 'error logs' which makes more difficult to analyze 500 error codes.

I just would like to export files generating errors from the standard logs using webtrends.

[cgrantski]

Still trying to understand. Sounds like you have older Apache logs where the access info is in different logs from the errors info.

Or you have IIS logs where the return code field is not being collected.

Either way, if 500 errors are not being logged then you can't report on them.

I've gotta be missing something here. Is WebTrends giving you counts of 500 errors? If yes, then you are collecting 500 errors. WebTrends can, in fact, tell you what file requests immediately preceded the 500 errors, which sounds like it's what you want. But it's not straightforward to get that.

Please continue clarifying and I'll try to continue helping.

[followgreg]

Thanks so much cgrantski your help is much apreciated!

I actually have IIS log files and webtrends counts HTTP 500 errors but I would need to view which file/url causes the problem without going manually through the whole set of logs (almost 2 gigs ).

I still can not find a solution, the error count drives me crazy and I am being lazy for foing manually through these huge logs.

[cgrantski]

WebTrends can't do it because it ignores 500 pages in analysis, meaning you can't even make a filter for them. The only place it doesn't ignore them is in the errors summary report, which only gives a count. But you know all this.

We once helped a client track down some really nasty 500 errors using WebTrends, so this is familiar territory to me.

My suggestion: use the DOS FIND /V command to make a much smaller sublog of all lines with 500 status codes in them, and either use WT to give you a summary of those sublogs, or just shove it into Excel.

A FIND command would be:

FIND /V ".com 500 " filename > filename.500

It will take a few minutes to go through a 2 GB file.

You can also use FOR to make this work on all the logs in a folder, but the one I showed is the basic.

".com 500 " assumes the status code directly follows the host field in your IIS logs, which is typical.

Now you have to force WebTrends to analyze this log with the *.500 extension. You can do two things: 1) do a replace throughout the log that changes ".com 500 " to ".com 200 " and then just analyze it with WT as is, or 2) add a line to the WebTrends profile that is going to analyze this log, which causes WT to treat 500 codes as 200's. The profile file has a .wlp extension, the line to insert is "SuccessReturnCodes=500", and the line should go into the [profile] section of the *.wlp file. This trick works for WT 7.x (the current generation) and possibly also for WT 6.x, I can't remember.

This nice thing about this kind of analysis is that once you have isolated your 500's you can get look for patterns in browsers, cookie acceptance, etc as well as requested files and the previous file (via the referrer field).