A few days back, we at AMIS got our cloud trial for Oracle Management Cloud. I can now report from my first steps with Application Performance Monitoring, one of the key components of OMC. Application Performance Monitoring (APM) is clearly indispensable to any organization adopting a DevOps approach – and frankly required for any organization in general running applications to support business objectives. APM provides insight in the non-functional behavior of applications – or better yet: of the business functions provided by these applications. It alerts administrators to functions that have unacceptable response times or are at risk to display poor performance and it allows us to analyze these situations to figure out where in the application stack – front end, services, integration flows, database, etc. – and in which specific component the problems have arisen. After performing this type of root cause analysis, resolving the problem still needs to be done, but is kick started as early as possible and with as much analysis details as possible.
In this article, I will describe the very practical steps I took to go from having my trial provisioned to having my first application monitored in the dashboards of APM. At this point I will not yet have very compelling analyses to describe – but I do have a dashboard and my first alerts sent to me.
This picture visualizes my set up: a local Node.js environment on my laptop, running an application that responds a HTTP requests by serving up an Oracle JET application with all of its resources (static JS libraries, CSS files, images etc). The Node.js server is configured for oracle-apm as is this particular Node.js application. When the application is running, the APM agent is activated. The agent gathers details and metrics – and sends these details to the Oracle Management Cloud environment. Here, these details are collected, stored and processed. They can be visualized in a dashboard, used for analysis and for example lead to automated alerts when specified alert conditions are identified. Read the complete article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.