No administrator wants to be in a situation where a problem occurred an hour ago and they no longer have any information on it because they only have real-time data. In addition, administrators also want to be able to answer the question that typically comes up when everything was running fine one day and fails to perform on the next: “What has changed?” For these reasons, administrators need historical information to refer to at all tiers of the application. This includes the host as well as visibility across the stack of both monitoring and configuration data to answer, writes Glen Hawkins, senior director of product management, Middleware and Application Management at Oracle, in a blog titled, “Demystifying WebLogic and Fusion Middleware Management.”
Any number of possible causes may be the culprit - the number of end users may have increased, or the way the end users are using the application changed, or there might have been application changes, WebLogic domain changes, JVM changes, a patch applied, or someone even may have started running something new on the machine or impacted the OS.
No matter what the cause, the ability to correlate the myriad possible changes and come to a quick conclusion is key to ensuring optimal application service levels in a production environment for end users, says Hawkins. “That means that you need a full stack 24/7 real-time and historical monitoring solution that can also provide meaningful diagnostics and track/compare configuration standards across the entire application system stack which is something that only Oracle Enterprise Manager Cloud Control is able to provide in the case of the Oracle stack.” Read on.