One of the 1.400 changes in the new NetCrunch 10 Suite is the Business Status Node. But what is a Business Status Node and when is it relevant?
Let’s imagine that you’re monitoring two redundant connections (such as Etherchannel), services or devices. While some administrators would prefer to be notified about ‘status down’ of any of these services or devices individually, others might find it unnecessarily alarming. After all, if these devices or services are redundant, the service offered is still up.
NetCrunch 10 Suite has tackled this problem by introducing the concept of a Business Status Node.
With a Business Status Node you can take several services, nodes or sensors and combine them into one, virtual status. This way, for example, if you have two redundant connections and one of them goes down, you will only receive a ‘warning’ status – which reflects the status of the whole service provided, rather than the status of its components.
This is only one of the many ways in which engineers at NetCrunch are tacking the issue of alert overflow.