Has anyone ever attempted to parse a BO webi log file with powershell (or other windows scripting language) to get something in a more friendly output that could be passed on to an internal support team for review? For example, when I review our log files I see a variety of error messages that might be something I need to pay attention to as a system admin or they might be 'training' type errors that I can hand off to our support team to get with the user. I want to parse out the 'useful' info and ignore the noise ( such as excess info, 'soft errors', or successes). Plus, the support team does not have access to our webi logs/webi servers.
I am self-teaching as I go with powershell and since I have other scripts running in powershell, I started with that (there could be a better way). I would just like to extract the date, server, full error information and username and format it to a list. There is just no easy way that I can figure out to identify a single log entry line... or to know where the error information 'really' ends. Maybe I'm overlooking the obvious though - which is very possible as these webi logs make my eyes go buggy!
Has anyone ever tried anything like this and can share some insight? we are on 4.0 sp7 patch 7 if it makes a difference in log format or anything.
thanks in advance,
Missy