|
|
Sponsored Content
Special Forums
UNIX and Linux Applications
Infrastructure Monitoring
Questions about BSM (Business Service Management)
Post 302782199 by zaxxon on Monday 18th of March 2013 11:31:38 AM
03-18-2013
Questions about BSM (Business Service Management)
Hi all,
management currently has the idea (maybe injected by some nifty salesman
), that BSM consists especially of data gathered from systems with heart-beat like messages. In other words, they think about to implement as many systems, that can provide not only status changes from ok to faulty and back, but also send "ok"-messages in regular intervals to show, that the systems/services/agents/whatever are working fine.
Me and about every other technician here is thinking that this is some kind of overhead, a tad too much paranoia.
I asked a consultant, if that these heart-beat flood is really part of the "general" BSM concept and he said yes.
I checked the Wikipedia entry for this and didn't find anything that this kind of "paranoid message storm" is really needed to implement the thought/model of BSM into an IT-monitoring-infrastructure.
Does anybody have a hint or source to some document/website/etc, that points out that such "ok"-messages are part of monitoring in a BSM compliant environment?
I also checked this rather old publication IBM Business Service Managemet (2004) a bit as well, but all I have read so far doesn't point out clear to me that heart-beat stuff.
Thanks for any info.
management currently has the idea (maybe injected by some nifty salesman
), that BSM consists especially of data gathered from systems with heart-beat like messages. In other words, they think about to implement as many systems, that can provide not only status changes from ok to faulty and back, but also send "ok"-messages in regular intervals to show, that the systems/services/agents/whatever are working fine.Me and about every other technician here is thinking that this is some kind of overhead, a tad too much paranoia.
I asked a consultant, if that these heart-beat flood is really part of the "general" BSM concept and he said yes.
I checked the Wikipedia entry for this and didn't find anything that this kind of "paranoid message storm"
is really needed to implement the thought/model of BSM into an IT-monitoring-infrastructure.Does anybody have a hint or source to some document/website/etc, that points out that such "ok"-messages are part of monitoring in a BSM compliant environment?
I also checked this rather old publication IBM Business Service Managemet (2004) a bit as well, but all I have read so far doesn't point out clear to me that heart-beat stuff.
Thanks for any info.
Last edited by zaxxon; 03-18-2013 at 12:40 PM..
|
|
LEARN ABOUT MOJAVE
au_free_token
AU_FREE_TOKEN(3) BSD Library Functions Manual AU_FREE_TOKEN(3) NAME
au_free_token -- deallocate a token_t created by any of the au_to_*() BSM API functions LIBRARY
Basic Security Module Library (libbsm, -lbsm) SYNOPSIS
#include <bsm/libbsm.h> void au_free_token(token_t *tok); DESCRIPTION
The BSM API generally manages deallocation of token_t objects. However, if au_write(3) is passed a bad audit descriptor, the token_t * parameter will be left untouched. In that case, the caller can deallocate the token_t using au_free_token() if desired. The tok argument is a token_t * generated by one of the au_to_*() BSM API calls. For convenience, tok may be NULL, in which case au_free_token() returns immediately. IMPLEMENTATION NOTES
This is, in fact, what audit_write(3) does, in keeping with the existing memory management model of the BSM API. SEE ALSO
audit_write(3), au_write(3), libbsm(3) HISTORY
The OpenBSM implementation was created by McAfee Research, the security division of McAfee Inc., under contract to Apple Computer, Inc., in 2004. It was subsequently adopted by the TrustedBSD Project as the foundation for the OpenBSM distribution. AUTHORS
This software was created by Robert Watson, Wayne Salamon, and Suresh Krishnaswamy for McAfee Research, the security research division of McAfee, Inc., under contract to Apple Computer, Inc. The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems. BSD
April 19, 2005 BSD