Monitoring data, like all operations data, is at its most valuable when it leverages a presentation layer that puts the information in the proper...
You are here
What is Business Service Monitoring?
What is it?
BSM is the acronym for the advanced monitoring of hosts and services in Opsview 4.5 – allowing us to group similar hosts into components, set resiliency on these components, and add multiple components to form a top level service.
This will allow users a much-enhanced view into their IT infrastructure – as now Opsview will understand resiliency, availability, etc.
Users will also be able to undertake actions against every layer of the BSM, from the GUI. I.e. we are now able to set downtime against every check in the hierarchy with a few clicks; you will be able to acknowledge every problem in the ‘MySQL Cluster’ with a few clicks, add comments against BSM’s, etc. Previously this was done at a per host/service check level, as it was unavailable with keywords.
Whats the concept?
Currently– Opsview’s understanding of business services is at the keyword level.
We have a top-level component, our keyword, and then a lot of disparate services from numerous hosts “inside it”. When one service fails, the entire keyword will fail – which is often not the case in resilient IT:
The purpose of BSM is to negate this and give real-world views in terms of “we can allow 1 host to fail, and our ‘service’ is still operational” - achieving a “resilient keywords hierarchy” – keywords within keywords, with resiliency and more power.
Using BSM – we can have multiple hosts of the same type (already in Opsview) in components, allowing one host to fail but the component to still be “operational”. A business service can be comprised of multiple components, each with their own resiliency levels – giving a true end-to-end view of the business service.
We can then undertake operations at a component and a BSM level, such as:
- “Who/which team is responsible for this?” – Add notes to the BSM/component.
- “Schedule downtime against entire component”.
- “Acknowledge all issues in a component”.
- “View events related to this BSM / component”.
- Send alerts at a component / BSM level – i.e. I only want to know when a component is critical, not when a host in it has failed – as we have resiliency in place.
- Be alerted that a BSM’s availability has gone below a certain level, i.e. it is below your agreed SLA/OLA.
- Run historical reports against BSM’s and Components, automated or manual, and emailed in your companies brand to yourself / customer at a pre-determined time/date.
- And more!
What does this look like?
In an Opsview system, we can have a website called “Intranet” – with 6 components – including an ‘Apache cluster’, ‘Unix cluster’, etc. (As below – image taken from a live system).
Here we can see the components in our business service, and the hosts in those components – along with the ‘operational zone’ (the shaded section) – which is the graphical representation of ‘how many hosts do we require online?’.
With BSM – we can now monitor and display our entire stack in a single view, so we can see “one host has failed in the Unix cluster, it hasn’t affected our website yet but we will need to fix that soon” .
Business service monitoring is a terrific tool that will take existing hosts, services and host templates and allow the creation of a hierarchy of components and business services – showing the relationship between hosts and the business services they support, availability (SLA/OLA) at each layer, reporting, alerting, access control and more.
More like this
A customer contacted us with a requirement to monitor the functional status of their website and all its vital components to ensure...
With so many different systems being used in one location, the IT department, getting a handle on everything in a single view can be one of the...