But what does a comprehensive monitoring require? It requires a combination of planning and right implementation in the areas of how and what targets (Service components - hardware infrastructure, software infrastructure, SOA applications, J2EE applications) need to be monitored based on their organization prioritization, who have the rights to act on those events, setting up rule based alerts and propagate SLA breached events to the right audience - Service Desk (or Helpdesk), DBA’s, Middleware team, Application teams, etc. The DevOps teams can get a 360 degree view (Uptime, KPI, Business Matrix) using the views provided by Enterprise Manager Service and System Dashboards. In addition, synthetic tests and beacons are utilized to validate Service URLs for end point invocation & validation of functional tests.
To summarize, service components residing both on premise and on the cloud requires comprehensive monitoring and continues to be a critical requirement for most of the organizations. To implement an effective monitoring solution, the right tools, best practices and processes have to be aligned and implemented properly.