|
|
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_bsm_to_fcntl_cmd
AU_BSM_TO_FCNTL_CMD(3) BSD Library Functions Manual AU_BSM_TO_FCNTL_CMD(3) NAME
au_bsm_to_fcntl_cmd, au_fcntl_cmd_to_bsm -- convert between BSM and local fcntl(2) command values LIBRARY
Basic Security Module Library (libbsm, -lbsm) SYNOPSIS
#include <bsm/libbsm.h> int au_bsm_to_fcntl_cmd(u_short bsm_fcntl_cmd, int *local_fcntl_cmdp); u_short au_fcntl_cmd_to_bsm(int local_fcntl_cmd); DESCRIPTION
These interfaces may be used to convert between the local and BSM fcntl(2) command values. The au_bsm_to_fcntl_cmd() function accepts a BSM command value, bsm_fcntl_cmd, and converts it to a local command value passed to fcntl(2), that will be stored in the integer pointed to by local_fcntl_cmdp if successful. This call will fail if the BSM command value cannot be mapped into a local fcntl(2) command value which may occur if the command token was generated on another operating system. The au_fcntl_cmd_to_bsm() function accepts a local fcntl(2) command value, and returns the BSM fcntl(2) command value for it. This call can- not fail, and instead returns a BSM command value indicating to a later decoder that the command value could not be encoded. RETURN VALULES
On success, au_bsm_to_fcntl_cmd() returns 0 and a converted command value; on failure, it returns -1 but does not set errno(2). SEE ALSO
fcntl(2), au_bsm_to_domain(3), au_domain_to_bsm(3), au_bsm_to_socket_type(3), au_socket_type_to_bsm(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 Stacey Son 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
March 5, 2009 BSD