All the Perl that's Practical to Extract and Report
use Perl Log In
shockme (2685)
reversethis-{gro.dnuowtixe} {ta} {kcohs}
http://exitwound.org/
AOL IM: stephenhargrove (Add Buddy, Send Message)
If you really must have more information about me, see my home node [perlmonks.org] at PerlMonks [perlmonks.org] or my journal [exitwound.org] at exitwound.org.
Event Logs and Ear Infections
He breathed a huge sigh of relief when he discovered that the doctor wasn't going to give him a shot. It was hilarious.
Once back at the office, I started digging around in Win32::EventLog. I can't believe Activestate hasn't made libwin32 available through PPM yet. Anyway, it was short work getting the module to compile.
I spent the evening writing a script to remotely access our NT/2K servers and report back some statistics on the Event Logs, as well as error and warning messages via Mail::Sendmail. It works like a charm. Beautiful stuff. But, with almost 75 servers, it's information overload. I'm going to have to identify certain error and warning codes that can safely be ignored. That would greatly decrease the amount of information contained in each email, and make "real" problems more obvious.
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Logs (Score:1)
One of my few victories at my last job [perl.org] was in successfully insisting that the log analyses start out small and comprehensible (rather than comprehensive), and they mostly stayed that way. When "people" asked for pie-charts, and reports on every single user session (times a
Re:Logs (Score:1)
Actually, this project is of my own undertaking. We've got 75 servers supported by 3 people, and I'm hoping that by utilizing this script, it'll help us stay focused on the "important" stuff and, at the same time, possibly give us heads-up on any impending doom. ;)
If things get any worse, I'll have to ask you to stop helping me.