Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring Questions about BSM (Business Service Management) Post 302784983 by Ariel Gordon on Sunday 24th of March 2013 05:19:26 AM
Old 03-24-2013
BSM and heart-beat

Zaxxon

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

Ariel
This User Gave Thanks to Ariel Gordon For This Post:
 
clusvcmgrd(8)						       Red Hat Cluster Suite						     clusvcmgrd(8)

NAME
rgmanager - Resource Group (Cluster Service) Manager Daemon DESCRIPTION
rgmanager handles management of user-defined cluster services (also known as resource groups). This includes handling of user requests including service start, service disable, service relocate, and service restart. The service manager daemon also handles restarting and relocating services in the event of failures. HOW IT WORKS
The service manager is spawned by an init script after the cluster infrastructure has been started and only functions when the cluster is quorate and locks are working. During initialization, the service manager runs scripts which ensure that all services are clear to be started. After that, it determines which services need to be started and starts them. When an event is received, members which are no longer online have their services taken away from them. The event should only occur in the case that the member has been fenced whenever fencing is available. When a cluster member determines that it is no longer in the cluster quorum, the service manager stops all services and waits for a new quorum to form. COMMAND LINE OPTIONS
-f Run in the foreground (do not fork). -d Enable debug-level logging. -w Disable internal process monitoring (for debugging). -N Do not perform stop-before-start. Combined with the -Z flag to clusvcadm, this can be used to allow rgmanager to be upgraded with- out stopping a given user service or set of services. SEE ALSO
clusvcadm(8) Jan 2005 clusvcmgrd(8)
All times are GMT -4. The time now is 01:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy