Each business service is unique. It depends on many network elements (devices and applications), hence its operability is ensured by the operability of those elements. However, there is no "magic formula" describing their relations. For example, if a critical service depends on an application server cluster, a complete failure of a single application server doesn't even mean that the business service is degraded. Establishing a service by "clicking several hosts and applications" is a good marketing device, but complex real-life services require a more advanced multi-level workflow.
Most services rely on a specific multi-vendor combination of hardware and software products, making the niche monitoring products offered by their manufacturers useless or inefficient for monitoring such services as a whole.
In addition, remaining highly available, most business services should also meet the custom Service Level Agreements (SLAs). Those SLAs are often contracted and their violation can lead to huge reputational and financial losses.
The status and performance indicators of a service modeled inside AggreGate Network Manager can be accompanied by their operational level and service level requirements, allowing to:
|Immediately react to the sudden SLA breaches by notifying system operators||Plan the capacity of underlying resources to ensure long-term service level compliance|
|Evaluate the impact of IT infrastructure failures on business processes||Predict the SLA violation dates and inform system administrators in advance|
|Collect the SLA compliance statistics for further reporting||Identify the migration, consolidation and license reduction opportunities|
|Visualize the availability and quality of business services|