topic Re: Error log practices in Operating System - HP-UX

Error log practices

Simon Abbott — Tue, 05 Feb 2002 10:39:51 GMT

Hello everyone,

We need to put a better error logging proceedure in place here. I am guessing that the way to go is either to buy an off-the-shelf package or to create somthing in access or excel.

The kind of thing we're looking to do is to enter all the errors, problems and unplanned downtime and have a search facility so we don't spend ages working out a problem that a colleague spent ages working on yesterday.

So any recomendations of packages and past experience would be greatful.

Many thanks,

Simon.

Re: Error log practices

steven Burgess_2 — Tue, 05 Feb 2002 11:43:29 GMT

Hi mate

It depends how efficent you really want to be.

You could start with an electronic diary that you could all update. And handover problems to the next man to advise what had happened that day. You could then link the problem record with the problem fix. This would create a knowledge base.

We here have a huge system that resides on our m/frame called solve. It gives you problem numbers each time you raise an issue. You then update the problem record with fixes etc. All have access to view problem records

We are also currently undergoing a replacement with a company called peregrine systems. This will allow reporting of all problems etc.

Call center type stuff really

Re: Error log practices

harry d brown jr — Tue, 05 Feb 2002 13:20:50 GMT

Simon,

You crack me up "...create somthing in access or excel."

http://www.microimages.com/~dwilliss/scripts/

http://rr.sans.org/logging/syslog.php

http://secinf.net/info/unix/lance/swatch.html

http://www.samag.com/documents/s=1146/sam0109m/0109m.htm

live free or die
harry

Re: Error log practices

Simon Abbott — Fri, 08 Feb 2002 10:40:37 GMT

Thank you for your reply Harry. You also crack me up because you didn't read the question properly. I wasn't talking about system log files.

Regards,

Simon.

Re: Error log practices

ian Dennison — Fri, 08 Feb 2002 12:40:47 GMT

Simon,

It seems there are 2 issues here,

1. Identifying and Capturing Error Events

2. Fault Logging and Tracking.

IT/Operations (aka VantagePoint) is probably the whizz-bang approach, if you have the bucks. Very good configuration and customisation, but intelligent filtering can be a little bit of work.

Remedy has a fairly well advanced HelpDesk Package, which IT/Operations does have a plug-in into (I think). I last used this plugin on ITO 5, which was called Trio and was horrible to use. Hopefully they have improved it since then!

Share and Enjoy! Ian

Re: Error log practices

Mark Vollmers — Fri, 08 Feb 2002 16:08:45 GMT

Simon-

Having a small operation with a small budget, one thing that I have is just a manual log with entries (that's when I keep it up to date, that is). One thing that I do is print out threads that I either have used or might use from here, though. It's a little cluttered, and not nearly as efficient or cool, but works well enough (better than the search has been working recently). Just something to consider.

Mark