What are distributed applications?
A distributed application is any application in which the components are distributed across multiple devices. For example, a web based application’s components could include multiple web servers, backend databases and networking devices. For the application to function at an acceptable level each component of the application must function at an acceptable level.
Why use distributed applications?
There are some cases where it can be feasible to use a single computer but the use of a distributed system is more practical for larger and more business critical applications. For example, it might be more cost-effective to share the workload across a cluster of low-end computer hardware rather than investing in a single high-end computer. An application built on a cluster of systems is inherently more scalable and fault tolerant.
Distributed applications can also use the Internet and the Cloud for both application features and additional resources that might be impractical to provide locally. Remotely hosted search engines, mapping utilities, file sharing, etc., can be seamlessly integrated into locally hosted web sites without the cost of developing, hosting, or maintaining these features. The drawback to using remotely hosted features is that you have no control over their performance and need to monitor them to ensure that they do not create a bottleneck for overall application performance.
What is a distributed application SLA?
The basic concept of a distributed application SLA is monitoring the performance data for each application’s components as it pertains to the performance of the overall application. So, for a web server, there would be a test on how long it takes for a page to load, or for a SQL server, how long it takes to respond to a query. The level of detail can range from basic user perspective (e.g. the web page must load in less than 2 seconds), to more in depth performance metrics (send an alert if any SQL Server disk queue length is > 2).
What are the parameters of distributed SLA monitoring?
Each component’s state is then color coded and stacked together in a real-time chart that provides a visual correlation between components. The underlying network congestion that is causing pings to slow down will affect other network dependent components and will be visible over all components affected by network congestion. This visual correlation can be used to quickly pinpoint the root cause of performance issues in an application.
Why do businesses need distributed application SLA monitoring?
Any enterprise with contractual performance obligations involving service level agreements needs to ensure and document compliance as well as reasons and causes of noncompliance. Correlating user experience measurements with the infrastructure of the distributed network can provide vital indicators affecting contract fulfillment as well as future business. To name three:
- application availability
- long term application performance
- root causes of outages or performance degradation affecting end-users
How does the Heroix Longitude SLA dashboard work?
Longitude’s SLA Dashboard gives real time displays of SLA performance as well as:
- drilldown for investigating compliance shortfalls
- historical reports
- ability to comment on extenuating circumstances or actions taken to resolve the problem identified
- tools for documenting changes in IT infrastructure and measuring the effects on SLA performance
Is Heroix Longitude right for your business?
If you are looking for affordable, easy-to-use performance monitoring software that works across Windows, Unix, Linux, VMware, Hyper-V and network devices, and can keep your distributed system compliant and working, our product and support maybe for you.
Stay tuned to this location for more details.