A (large) customer recently asked me to implement a feature whereby they
could monitor zone activity via syslog.  The motivation is that for this
customer, any zone state change not during maintenance windows is a cause
for alarm.

I prototyped this feature last night and I'd like to solicit your
feedback on it.  Currently, the messages look like this on zone
bootup:

Oct 27 01:37:50 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "running" (boot)

This on reboot:

Oct 27 01:37:57 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "running" (reboot)

This on reboot from inside the zone (reboot(1m)):

Oct 27 01:37:57 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "running" (zone initiated reboot)

This on "halt"

Oct 27 17:25:04 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "installed" (halt)

This on a "halt" which got stuck:

Oct 27 17:37:19 xanadu zoneadmd[136912]: [ID 230691 daemon.info] zone norton 
state changed to "down" (halt)

Several reboots in a row look like this:

Oct 27 01:37:57 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "running" (reboot)
Oct 27 01:38:12 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "running" (reboot)
Oct 27 01:39:22 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "running" (reboot)

A failed reboot would look like this:

Oct 27 01:37:57 xanadu zoneadmd[135850]: [ID 230691 daemon.info] zone norton 
state changed to "installed" (reboot)

So here are my questions:

    - Do you think this is useful?

    - Do you think the log level (Info) is right?  daemon.info is
      *not* logged by default, whereas notice is.  (So basically: do
      you want these messages in /var/adm/messages by default, or not?)

    - Do you think the facility of 'daemon' is OK?  With Solaris
      syslog you can't AFAIK route messages based on the value of
      'program' (which in this case is 'zoneadmd').

    - Any comment about whether the info provided is sufficient?
      For example, when a zone reboots it goes through numerous
      state transitions, but I chose to express this as one
      big transition-- does that work for everyone?

Thanks,

        -dp

-- 
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to