timestamp for alert log

[Kevin Scantlan]

I often get requests to follow up as to when and/or if an alert was triggered.  I faithfully to the hcimonitord directory under the /exec directory.  I look in the hcimonitord.log file and start searching.  I find something like the following:

[aler:aler:INFO/0:  hcimonitord] New alert #52:

{VALUE pstat} {SOURCE ceralg_ord_ib_3} {MODE actual} {WITH -1} {COMP {== opening

}} {FOR {nmin 15}} {WINDOW {* * * * * *}} {HOST {}} {ACTION {{exec {hciguimsg -a

lert -message “ceralg_ord_ib_3 has been opening for 15 minutes, please page OCF/

Cerner primary!”  -display 161.130.112.131:0}}}}

So I look to see what date/time this alert triggered and I have no idea!  This is extremely frustrating.  I do my best and look some date time anywhere in the “log” to have at least some time ranges, if I’m lucky.  The image that comes to my mind is the following:

James T. Kirk:  Captain’s log, Stardate….. uh…. don’t know… my log has no date or time in it.

I would think it should be a simple matter to put a date/time stamp with the message.  There is a date/time stamp in the hcimonitord.err file, why not also in the hcimonitord.log file.

While searching the documentation, I came across what can be used for the hcisitectl command.  There’s a “-A” parameter that allows parameters to be passed to the various daemons that can be used by this command.  But, it does not ellaborate what those parameters, which does no one any good.  What are the parameters for the monitor daemon?

How has anyone else gotten around this lack of timestamp in the monitor daemon “log”?  Why doesn’t Quovadx put a timestamp here?  I’ve been a programmer for over 25 years and almost ALL applications worth their salt put timestamps in their logs.That’s what a log is! ( P.S., there are no timestamps in the process logs either.)

OK… I’m done ranting and raving.

Topic

[Michael Hertel]

[aler:aler:INFO/0:  hcimonitord] New alert #52:

You’ll see “New alert” as the daemon is loading your configuration.

There is no time stamp.

Look further for:

[aler:aler:WARN/0:  hcimonitord] Alert #7 triggered.

There is a timestamp right before it.

[Kevin Scantlan]

OK… I learned something.  I hadn’t known what the “New Alerts” really was… now I know it’s loading the configuration.  Thanks.

I still have questions about all of the parameters of hcisitectl command,  espeically the -A parameter.

[Michael Hertel]

hci rs6kf% hcisitectl -h

Usage:

       hcisitectl [-f] [-h ] [{ -K | -k }] [{ -S | -s }] [-u <#users>] [-A ]

Where:

       -K              = Kill ALL daemon processes

       -k       = Kill specified daemons, what is comma separated list

                         what: l = lockmgr

                               m = hcimonitord

       -S              = Start ALL daemon processes

       -s       = Start specified daemons, what is comma separated list

                         what: l = lockmgr

                               m = hcimonitord

       -u <#users>     = specify maximun number of users for lockmgr.

                        The #users defaults to 500 and must be great than 200.

       -A       = specify startup args for daemons, args is a

                         comma separated list.  Each entry is of the

                         form: =

                         where what is l or m (as above) and

                         are the arguments to pass to that daemon.

       -f              = force killing of daemons

       -h              = name of remote host

       -n              = Don’t run under service on NT

       if no options are specified, the status of the daemons

       is verified and reported.

[Kevin Scantlan]

Yes, that’s what the documentation says, but it never goes and tells what that list of possible arguments are for the -A parameter.  I would think it would be more than just an k (for kill) or s (for start).  That’s already covered.

[Author]

Replies