Monitoring Hosts using Oracle Enterprise Manager 10g Grid Control Release 2

Purpose

The objective of this OBE is to introduce you to some of the host monitoring features available with Oracle Enterprise Manager 10g Grid Control Release 2.

Time to Complete

Approximately 30 minutes

Topics

This OBE covers the following topics:

 Overview
 Viewing Host Home Page
 Monitoring Host Performance
 Monitoring Log Files
 Monitoring Program Resource Utilization
 Monitoring Files and Directories
 Tracking Storage Resources
 Executing Host Command
 Summary
 Related information

Viewing Screenshots

 Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: Because this action loads all screenshots simultaneously, response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.

The screenshots will not reflect the specific environment you are using. They are provided to give you an idea of where to locate specific functionality in the Oracle Enterprise Manager 10g Grid Control console.

Overview

As soon as a Management Agent is deployed to the host, Enterprise Manager automatically starts monitoring availability, performance and configuration information for that machine. System administrators and anyone who requires host information, such as DBAs managing databases on those hosts benefit from Grid Control's host management features.

Back to Topic List

Viewing Host Home Page

The Host Home page provides an overview of the status and vital statistics for each host that is part of the Grid Control environment. Perform the following steps to navigate to the host home page:

1.

Open the browser and enter the following URL:

http://<management service hostname>.<domain>:<port>/em/

The default port value on a clean machine is 7777. However, if there are other instances running on the machine, then the port may be different.

The login page will be displayed. Enter the User Name and Password, and then click the Login button.

 

2.

Click the Targets tab.

 

3.

From the list of hosts, click any of the host name.

 

4.

Enterprise Manager consolidates the relevant host information into a convenient single-screen Host Home page. You can see the availability, key configuration information, and outstanding alerts, as well as other pertinent information about the host. Convenient links allow you to view all of the metrics collected for the host, change the thresholds as appropriate, or perform administrative actions.

 

Back to Topic List

Monitoring Host Performance

Enterprise Manager allows you to monitor the performance of host targets by automatically monitoring a comprehensive set of host metrics, such as CPU Usage, Memory Usage, Disk I/O, Network Interface Activity, and other statistics. Perform the following steps to monitor the performance of a given host:

1.

Click the Performance subtab.

 

2.

The Host Performance page provides an overview of the host performance, by summarizing key performance statistics. This allows administrators to quickly isolate performance problems, and determine whether resources need to be added or redistributed for this host.

The Performance Summary page displays CPU Utilization, Memory Utilization and Disk I/O, together with the top processes (by CPU and Memory consumption). This enables you to determine whether the system is currently CPU-bound, Memory-bound or I/O bound. In addition, you can analyze historical trends for a variety of time-periods. Select "Last 24 Hours" to view historical performance data. From the page, you can also view more details about CPU, Memory, and Disk I/O, by selecting the appropriate page in the "View" dropdown.

 

3.

Select CPU Details from the View drop-down list. This page shows real-time and historical information about CPU Usage statistics, as well as the processes consuming the most CPU resources.

 

4.

Select Memory Details from the View drop-down list. This page provides a memory-centric view, by displaying real-time and historical memory usage on the host, as well as the processes that are currently consuming most memory resources.

 

5.

Select Disk Details from the View drop-down list. This page provides the disk details, enabling administrators to quickly identify the most utilized and underutilized disks.

 

6.

Select Program Resource Utilization from the View drop-down list. This page provides a quick glimpse of the programs being monitored on the host. With this information, you can see the trends in resource usage for:

  • Specific program or set of programs
  • Special user or set of users
  • Combination of programs and users

Note: By default only overall resource consumption of all programs running on this host is being monitored. By the end of the exercise you will learn how to set up monitoring of specific programs.

 

7.

The Performance pages summarize key performance information for a host. In addition, you can see all of the metrics monitored for host by navigating to the All Metrics page. To get to the All Metrics page, click the Home tab.

 

8.

Click the All Metrics link from the Related Links section.

 

9.

From this page, you can see all of the metrics collected out-of-box, as well as the default collection frequencies. By clicking on any of the metrics, you can view real-time information and analyze historical trends for this metric.

 

Back to Topic List

Scenario:

Suppose you have a custom LoanApp application, and you would like to monitor the application log files for potential intrusions, to ensure that the application is always up and that the log file directory does not exceed 12MB. The three exercises that follow will walk you through the processes of setting this up. For the purposes of this exercise, let's assume that your LoanApp application is logging all of its activity into the "loanapp.log" log file, located in the /app/log directory. In addition, the application logs all of the intrusion attacks in the following message formats:

  • <Timestamp>: APP-ERR-7501: WARNING: Potential Intrusion detected. User jdoe failed to login 10 times in the past 5 minutes.
  • <Timestamp>: APP-ERR-7502: ERROR: Potential intrusion detected. jdoe failed to login 25 times in the past 24 hours. Shutting down access to jdoe account.

Monitoring Log Files

Now, let's use the Log File Monitoring functionality in Enterprise Manager to monitor for potential intrusions. We will configure Enterprise Manager to generate a warning alert whenever a "WARNING" message is generated in the log file, and to generate a critical alert whenever an "ERROR" message is generated in the log file.

1.

Navigate to the host home page by clicking on the target locator link.

 

2.

Scroll down to the Related Links section and click the Metric and Policy Settings link.

 

3.

Find the metric Log File Pattern Matched Line Count from the metric list and click the Edit icon for this metric.

 

4.

Click the Add button to set up monitoring for the warning message.

 

5.

Specify the Log File Name as /app/log/loanapp.log, Match Pattern as WARNING: Potential Intrusion, Warning Threshold as 1. This will ensure that a warning alert gets generated every time there is at least one occurrence of the warning message. Click the Add button again to set up monitoring for the critical message.

 

6.

Specify the Log File Name as /app/log/loanapp.log, Match Pattern as ERROR: Potential Intrusion, Critical Threshold as 1. This will ensure that a critical alert gets generated every time there is at least one occurrence of the error message. Click the Continue button to return to the Metric and Policy Settings page.

7.

Your changes will be reflected in the metrics table. Click the OK button to save your changes.

 

8.

Click the OK button on the confirmation page.

 

Back to Topic List

Monitoring Program Resource Utilization

In this exercise you will use Enterprise Manager's Program Resource Utilization features to ensure that there is always at least one LoanApp process running. Perform the following steps to setup program resource utilization monitoring:

1.

Click the Metric and Policy Settings link.

 

2.

Select All metrics from the View drop-down list.

 

3.

You will see a number of program-specific metrics, such as Program's Max CPU Utilization and Program's Max Process Count. In order to ensure that there is always at least one LoanApp process, we will use the Program's Min Process Count metric. Click the Edit icon for the Program's Min Process Count metric.

 

4.

The table lists all Program Name/Owner objects monitored for this metric. You can specify different threshold settings for each Program Name/Owner combination. Click the Add button to add monitoring of the LoanApp processes.

 

5.

Specify LoanApp as the Program Name, leave Owner as DBA , set Warning Threshold to 2, and Critical Threshold to 1. This will ensure that a critical alert gets generated whenever there are no LoanApp processes running, and a warning alert gets generated whenever there is only one LoanApp process running. In addition, you have an option to specify a corrective action to restart the application by clicking Edit . Click the Continue button to return to the Metric and Policy Settings page.

 

6.

Your changes will be reflected in the metrics table. Click the OK button to save your changes.

Click the OK button on the confirmation page.

 

Back to Topic List

Monitoring Files and Directories

In this exercise you will use Enterprise Manager's file and directory monitoring functionality to ensure that the LoanApp log file directory does not exceed 12MB. In this case, you may wish to set up a warning threshold at 5MB and a critical threshold at 10MB. Perform the following steps to configure file and directory monitoring:

1.

Click the Metric and Policy Settings link.

 

2.

Select All metrics from the View drop-down list.

 

3.

You will see four file and directory monitoring specific metrics, such as File or Directory Permissions, File or Directory Size (MB) and so on. Click the Edit icon for the File or Directory Size (MB) metric.

 

4.

The table lists all File or Directory Name objects monitored for this metric. You can specify different threshold settings for each File or Directory Name object. Click the Add button to set up monitoring for the /app/log directory.

 

5.

Specify the File or Directory Name as /app/log , Warning Threshold as 5 MB and Critical Threshold as 10 MB. Click the Continue button to return to the Metric and Policy Settings page.

 

6.

Your changes will be reflected in the metrics table. Click OK to save your changes.

 

Back to Topic List

Tracking Storage Resources

Tracking the storage resource allocation and usage is essential to large IT departments. Unallocated and underutilized storage can be put to better use. In addition, you need to understand historical trends at a business entity-level in order to effectively plan for future growth. In this exercise you will learn how storage information is collected and presented in Oracle Enterprise Manager 10g Grid Control Release 2. Perform the following steps to view storage resource utilization:

1.

Scroll down to Related Links section and click the Storage Details link.

 

2.

The Storage Details page provides detailed storage resource allocation and usage information for your host. The Storage Details page provides the following information:

  • Overall Utilization: Shows summary attributes that provide a system-level view of storage resource utilization.
  • Provisioning Summary: Shows allocation-related summary attributes for File Systems, ASM, Volumes, and Disks for the associated hosts.
  • Consumption: Shows usage-related summary attributes for Databases and File Systems. In addition, details are provided for each storage layer, such as Disks, File Systems, ASM, and so on.

Click the Storage History link under the Related Links section.

 

3.

The Storage History page provides a quick glimpse of the history of the storage usage for the choice selected in the View list. Using this page, you can view the Storage History at a host level, as well as the storage history for databases, local file systems, local disks, volumes, and writable NFS statistics.

Using the historical trends presented on this page, you can analyze usage trends and predict how much storage your organization may need in the future.

 

4.

In addition, Enterprise Manager provides Storage Reports at a group level as well. To view the Group Storage Details report click the Groups subtab.

 

5.

Click Host Group from the list.

 

6.

Scroll down to the Related Links section and click the Storage Details link.

 

7.

From here you can quickly analyze the storage utilization across all the hosts managed by this group.

 

Back to Topic List

Executing Host Command

In this exercise you will learn how to execute host commands remotely from the Enterprise Manager Console. Perform the following steps to execute a host command remotely from the Enterprise Manager Console:

1.

Navigate to any host's home page. Click the Execute Host Command link in the Related Links section.

 

2.

Specify the host credentials and click the OK button.

 

3.

On this page, you can run any OS command, and immediately view the output of that command. Enter the following command in the Command field and click the Execute button to verify that the EM agent is running:

ps -ef | grep emagent

 

 

4.

You should see the details about the EM agent process in the output window.

Back to Topic List

 

Summary

In this lesson, you learned how to:

 View Host Home Page
 Monitor Host Performance
 Monitor Log Files
 Monitor Program Resource Utilization
 Monitor Files and Directories
 Track Storage Resources
 Execute Host Command

Back to Topic List

Related Information

 To ask a question about this OBE tutorial, post a query on the OBE Discussion Forum.

Back to Topic List

 Place the cursor over this icon to hide all screenshots.

 

 

 

Left Curve
Popular Downloads
Right Curve
Untitled Document