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?
Well as one of the people who defined the term BSM in the Industry do not see how BSM is related to a heart-beat. A heart-beat may allow you to understand if a component of a service is up an running so its more connected to a regular monitoring technique and not BSM, but it will not allow you to understand the status of the service itself. BSM deals with the following things
1) Understanding of the structure of the service
2) Based on this planning what monitoring is needed to ensure its availability
3) Deploying and tuning this Monitoring
4) Aggregating all the information from all the monitoring tools to understand the status of the service
5) Understanding the impact of an event / incident on a service
6) Understanding the impact of change on the service and planning accordingly
For more information you can find information at neebula.com
I hope this helps
This User Gave Thanks to Ariel Gordon For This Post: