|
|
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 OSX
au_bsm_to_domain
AU_BSM_TO_DOMAIN(3) BSD Library Functions Manual AU_BSM_TO_DOMAIN(3) NAME
au_bsm_to_domain, au_domain_to_bsm -- convert between BSM and local protocol domains LIBRARY
Basic Security Module Library (libbsm, -lbsm) SYNOPSIS
#include <bsm/libbsm.h> int au_bsm_to_domain(u_short bsm_domain, int *local_domainp); u_short au_domain_to_bsm(int local_domain); DESCRIPTION
These interfaces may be used to convert between the local and BSM protocol domains. The au_bsm_to_domain() function accepts a BSM domain, bsm_domain, and converts it to a local domain, such as those passed to socket(2), that will be stored in the integer pointed to by local_domainp if successful. This call will fail if the BSM domain cannot be mapped into a local domain, which may occur if the socket token was generated on another operating system. The au_domain_to_bsm() function accepts a local domain, and returns the BSM domain for it. This call cannot fail, and instead returns a BSM domain indicating to a later decoder that the domain could not be encoded. RETURN VALULES
On success, au_bsm_to_domain() returns 0 and a converted domain; on failure, it returns -1 but does not set errno(2). SEE ALSO
au_bsm_to_socket_type(3), au_socket_type_to_bsm(3), au_to_socket_ex(3), libbsm(3) HISTORY
au_bsm_to_domain() and au_domain_to_bsm() were introduced in OpenBSM 1.1. AUTHORS
These functions were implemented by Robert Watson under contract to Apple Inc. The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems. BSD
December 28, 2008 BSD