When the discussion turns to monitoring, that discussion most often focuses upon either monitoring the infrastructure for performance and availability, or monitoring the performance and availability of certain key applications. While it is essential to monitor both the infrastructure (hardware and software) that supports the key applications in your environment, and the applications themselves, it is also critical not to overlook the single most important person in the environment – the actual end user of the application or IT service.
Articles Tagged with New Relic
In Applications Performance Equals Response Time, not Resource Utilization, we took the position that while for the majority of the applications deployed on physical hardware the general practice was to infer their performance by looking at normal vs. abnormal resource utilization statistics, once you virtualize an application, it becomes necessary to directly measure its response time in order to ensure adequate service to business constituents and end users.
Monitoring computing infrastructure and applications for capacity, availability, and performance is a business that has been around for a long time – in fact for just about as long as computers have been used for business critical applications (since the mainframe lead era of the 1960’s). Since that time several waves of change have swept through the computer industry, and with each wave of change has come new computing architectures, new applications, requirements for monitoring and new monitoring approaches. Those waves have included mini-computers, personal computers, LAN based file sharing, client/server based computing, Internet (browser) based computing, N-tier SOA based applications, and now include agile development, virtualization, cloud based computing, and the proliferation of mobile based applications.
In “IT as a Service Reference Architecture“, we presented a a categorization of the the functionality and the products that are needed in order to construct an IT as a Service system. Purposely missing from this architecture was the question of how to monitor the performance of the services delivered from the service catalog via the underlying policies and automation in the IT as a Service stack.
For a developer, and subsequently the team of people that has to support certain kinds of applications in production, a PaaS cloud can be a wonderful thing. Why can a PaaS cloud be so wonderful? Because if you have a web based application based upon Java, Ruby-on-Rails, or .NET you can find a cloud provider that handles the entire hardware and software platform for your application.
It is now very clear the VMware vSphere 4.0 and 4.1 have demonstrated the robustness and performance necessary in order for them to be trusted virtualization platforms for many business critical applications. It is also very clear that many organizations are well down the road toward putting business critical applications on vSphere. We may not yet be at the point where the most response time critical applications (like online trading) are on vSphere, but we are certainly at the point where line of business applications like SAP and enterprise resident CRM applications are being virtualized.