Written by Porus Homi Havewala We are looking at the General Monitoring capabilities of Enterprise Manager, as experienced by Enterprise Manager Administrators or Cloud Administrators. Part I was here . In Part I, we had selected Host.. Monitoring.. Program Resource Utilization from the Host Target menu, and had started to set thresholds for each of the Program Names and Owner combinations. You are placed on the Metric and Collection Settings page. On this page, you can choose to view "All Metrics" or "Metrics with thresholds". This is where you specify the warning and critical thresholds we discussed earlier. The thresholds are supplied out-of-the-box for a number of metrics, but they can be changed depending on your company requirements. For example, a company may decide that 5% is too risky as a critical threshold for Filesystem Space available, and instead set it to 10%. The collection schedule can also be changed to be more frequent, but this is generally not recommended, since the Enterprise Manager Agent on the Target Server will increase its CPU Utilization by collecting the required metrics more often. The repository size may also increase as a result. If you want to set the Program Name and Owner combination thresholds, select "All Metrics". Then scroll down to the "Program Resource Utilization" entries. Click on the Multiple Edit icon - this icon, showing a bunch of pencils, means that multiple values can be specified. On the "Edit Advanced Settings" Page that appears, you can set your Program name and owner combinations, and specify the Warning and Critical thresholds. When you are back on the Metric and Collection Settings page, click on the "Other Collected Items" tab. We can see that a number of items are being collected such as CPUs, File Systems, Hardware, Installed OS Patches, Network Interface Cards, Open Ports, Operating System Properties, Software and so on. The collection schedule is set to every 24 hours. Click on one of the links. On this page, the Collection Schedule can be Enabled or Disabled. The default frequency is every 24 hours, but this can be changed. You can also specify if the Metric Data that is collected is to be used just for Alerting, or for Historical Trending as well. The upload interval can be changed - this affects which collection is uploaded, whether every one (1) or after a certain number of collections. The metrics that are affected by this collection are also seen. Select Host.. Monitoring.. All Metrics from the Host Target Menu. This displays the Metrics page in a new screen format that makes it easier to search for particular Metrics, and to disable/enable/modify collection schedules and warning/critical thresholds. Select the Buffer Activity Metric. You can click on any of the individual metrics in this group to modify the Thresholds, if they are not set. At the top of the screen, click on the Modify button to change the Collection schedule for this entire group of Metrics. As before, the Data Collection can be enabled or disabled. The Collection Frequency can be changed. The use of the Metric Data for Alerting and/or Historical Trending can also be modified, along with the Upload Interval that we have seen before. You are placed back on the All Metrics page. Various metrics can be modified on this page, such as Process, Inode, and File Tables Statistics including Number of Used File Handles, Switch/Swap Activity including System Swapins/Swapouts per second, Process Context Switches per second, Number of Logins for users, and so on. Incident Manager The Incident Manager is a new feature in Enterprise Manager Cloud Control 12c. You can centrally manage all the incidents that are grouped together in Problems, so that the administrative burden of looking at each incident separately is reduced. For example, there may be multiple Internal Errors ( ORA-600 ) of a certain type, such as [4136] , in the database. These multiple incidents are grouped together into a single Problem. You can acknowledge the problem, escalate it, raise the priority, assign to an owner, and so on. Let us take a brief look at this. Select Enterprise.. Monitoring.. Incident Manager to open the Incident Management system. We can see that there is a Problem to do with the ORA 600 [4136]. The number of incidents is shown as 2, meaning that the ORA 600 error has occurred twice. Notice there is no Owner of the problem. The first step is to acknowledge the problem by clicking on the Acknowledge link. After the problem is acknowledged, the person who acknowledged it becomes the Owner of the Problem. The next step is to click on the "Manage" button. This brings up the following screen. The Status can be changed to New, Work in Progress or Resolved. The Problem can be assigned to a different owner at this stage. We have selected DB3RDPARTY . The Priority can also be changed on this screen to Urgent, Very High, High, Medium or Low. The Escalated field can be changed to either of Levels 1 to 5. A comment can also be added. We have added "Please investigate this issue". Click on OK. This updates the tracking attributes of this problem. You are placed back on the Incident Manager page. The Problem now appears as Escalated to Level 2, with Priority as Urgent, Status as Work in Progress, and a new Owner who has not yet acknowledged the problem. We will continue looking at the Incident Manager and other general monitoring capabilities of Enterprise Manager in Part III of this article.
↧