Sadly, the net is littered with definitions for APM that are mostly confusing or aligned to some vendor’s tool capabilities. At IT Ecology, we define APM as a discipline within IT and systems management that focuses on the management of application performance throughout an application’s life-cycle by:

• Continually improving an application’s performance during development and QA to meet or exceed performance expectations
• Monitoring performance against baselines in production
• Enabling quick impact and root cause analysis when performance degradation is experienced in production

IT Ecology’s APM methodology

APM deployments that cannot prove value to the business are generally doomed in the medium to long term, no matter the amount of excitement that exists in the beginning of such a project. IT Ecology have developed a vendor-independent, ITIL-aligned APM methodology which through the use of carefully developed questionnaires assesses an organisation’s maturity in deploying APM and makes recommendations with regards to APM disciplines, tool selection and possible shortcomings.

What about Agile?

Agile affects every aspect of the application life-cycle. It encourages an iterative release cycle of smaller work packages and promotes leaner approaches to ALM in order to speed up time to market. Poor implementation of APM in an Agile project usually leads to performance issues in production that are hard to find and costly to rectify.

The role of DevOps

DevOps encourages communication, integration, automation and collaboration between developers and other IT professionals. In the context of APM, DevOps is supported by APM solutions and processes that add value across the entire application life-cycle, enabling communication of performance metrics across traditional silos.