System Monitoring using Oracle Enterprise Manager 10g Grid Control Release 2
System Monitoring using Oracle Enterprise Manager 10g
Grid Control Release 2
This OBE describes and shows you some of the system monitoring
features such as corrective actions, notifications, monitoring templates, and
groups using Oracle Enterprise Manager 10g Release 2.
Approximately 1 hour
This OBE covers the following topics:
 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.
The objective of this OBE is to help you become familiar with
the system monitoring, notification, and group management features in Oracle
Enterprise Manager 10g Release 2 (EM). The System Monitoring features
that will be covered apply to any managed IT component (called a 'target') such
as hosts, databases, and application servers. (Additional monitoring features
that are specific to those components will not be covered in this session).
Back to Topic List
Corrective Actions allow administrators to specify automated
responses to alerts or policy violations. Corrective Actions ensure that routine
responses to alerts or policy violations are automatically executed, thereby
saving administrator time and ensuring that problems are dealt with before they
noticeably impact end users. Perform the following steps to define corrective
actions:
|
1.
|
Open the browser and enter the
following URL:
http://<management
service hostname>.<domain>:<port>/em/
The default port value on a clear 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. |
Click the All Targets subtab.
|
| 4. |
In the Search drop-down list, select Listener, and click
the Go button.
|
| 5. |
Click any one of the listed listeners.
|
| 6. |
The listener home page appears. Scroll down to the bottom of the page
and locate and click the Metric and Policy Settings link.
|
| 7. |
On the Metric and Policy Settings page, look for the Status metric and
click the pencil like icon under the Edit column to edit it.
|
| 8. |
Click the Add button under the Corrective
Actions section to define a corrective action.
|
| 9. |
The Add Corrective Action page appears. Here, you will add a corrective
action that will start the listener when the listener status is down.
From the drop-down list, select OS Command, and click the Continue
button.
|
| 10. |
On the General page, specify the name as Startup Listener for
your corrective action.
|
| 11. |
Click the Parameters property page.
|
| 12. |
On the Parameters page, select Script from the Command Type drop-down
list.
|
| 13. |
In the OS Script box that appears, enter the following commands including
control characters:
export ORACLE_HOME=%OracleHome%;
%OracleHome%/bin/lsnrctl start %LsnrName%
Note: %OracleHome%
and %LsnrName% are case-sensitive.
|
| 14. |
Click the Credentials property page.
|
| 15. |
On the Credentials page, select the Override Preferred Credentials
option button.
|
| 16. |
Specify the host username and the password. Click the Continue
button.
|
| 17. |
You should be back to the Edit Advanced Settings page. Click the
Continue button.
|
| 18. |
For testing purposes, change the collection schedule for the Status metric
to 2 minutes. To do so, click the Every 5 minutes link under the
Collection Schedule column for the Status metric.
|
| 19. |
Change the Collection Frequency to repeat every 2 minutes.
|
| 20. |
Click the Continue button.
|
| 21. |
Click the OK button to save the changes.
|
| 22. |
The confirmation page appears. Click the OK button.
|
| 23. |
You are back to the Listener home page.
|
Back to Topic List
Enterprise Manager's notification system allows you to notify
administrators when metric severity conditions (metric thresholds) are met or
exceeded, when policy violations occur, and when jobs change state. However,
the notification system permits even greater flexibility and utility. Perform
the following steps to define a notification schedule:
|
1.
|
Click the Preferences link located at the top-right
corner of the console.
Note: In this exercise it is assumed that your
EM Super Administrator has already configured the SMTP gateway to to enable
email notifications. Only a privileged user can configure SMTP server.
If you are a Super Administrator you can configure the SMTP server from
the Setup -> Notification Methods page.
|
|
2.
|
Click the Add Another Row button in the E-mail Addresses section
of this page to specify an e-mail address.
|
| 3. |
Specify an e-mail address in the E-mail Address field.
|
| 4. |
Click the Apply button to save the changes.
|
| 5. |
Notice the confirmation message informing you that your preferences
data has been updated. Once you enter an e-mail address, a 24x7 notification
schedule will be created for you. Click the Schedule link located
on the left part of the page to review this schedule.
|
| 6. |
The notification schedule shown should be completely filled with the
user's email addresses. This means that any alert to which you have subscribed
to, will be sent to your email addresses. Click the Public Rules
link that you find on the left part of the page. You will see a list of
notification rules.
|
| 7. |
Select the checkbox for the Listener Availability rule and click
the Apply button.
|
| 8. |
You get the Update succeeded confirmation message.
Note: To test the corrective action that you defined in the first
exercise and to check whether you get the notification email when the
listener is down. Stop the listener manually by clicking the Stop button
on the listener home page. The corrective action should restart the listener
automatically. At the same time you should also receive an email notification
indicating that the listener is down.
|
Back to Topic List
Perform the following steps to check the status of the corrective
action for the listener's Status metric:
| 1. |
Navigate to your listener home page and click the number next to Availability
(%).
|
| 2. |
The Availability (Status History)
page for the listener appears. Scroll down the page. In the Availability
History for Last 24 Hours section at the bottom of the page, switch
the View drop-down to All History.
|
| 3. |
Locate the entry for the listener going down. There should be an eyeglass
icon next to this entry. Click on the eyeglass icon.
|
| 4. |
The Alert Details page should come up. It should show you a list of
all notifications and corrective actions that ran as a result of the listener
going down. Locate and click on the link for your corrective action and
review its results.
|
Back to Topic List
A Monitoring Template is a collection of monitoring settings
that you can define once and apply to multiple targets. It enables administrators
to easily propagate standardized monitoring settings across managed targets.
In this section you see how to create a monitoring template and also how to
apply this template to a target. In real-world scenarios, templates would most
likely be applied to many targets or groups, but the process for applying the
template to a single target or to groups of targets is the same. Perform the
following steps to see how to use templates:
| 1. |
To access the monitoring templates functionality,
click Setup from the top-right corner.
|
| 2. |
Click Monitoring Templates from the left-navigation bar.
|
| 3. |
To create a new monitoring template click the Create button.
|
| 4. |
A Monitoring Template is initially prefilled by copying monitoring settings
from a target. Choose the target that has the monitoring settings that
you would like to use in the template. Click the flashlight icon to select
the target.
|
| 5. |
In this exercise you use a database target. Select Database Instance
from the Target Type drop-down list. You can choose any of the available
databases. Select the database target and click Select.
|
| 6. |
The database you selected should now be in the Target field. Click Continue.
|
| 7. |
Specify a name for the new template and click the Metric Thresholds
subtab.
|
| 8. |
On this page you can edit the thresholds of the metrics that are part
of this template. For this exercise we will do a few simple changes. Change
the Warning Threshold for the Archive Area Used (%) to 90 and also click
the link under the Collection Schedule column to change the collection
schedule.
|
| 9. |
Change the frequency to 15 minutes and click Continue.
|
| 10. |
You can now see the updated Collection Schedule. Click the Policies
subtab.
|
| 11. |
This template does not involve any policy settings, therefore you can
remove the policy rules from the template. Click the Select All
link to select all the policies and then click the Remove button.
Note: Removing of policy rules from the template does not remove
or impact any policy rules defined on the destination target when you
actually apply the template to a target.
|
| 12. |
Click Yes to confirm.
|
| 13. |
You might have to do steps 11 and 12 repeatedly until all policies rules
have been removed from the template. Once you're done, click OK
to save the changes.
|
| 14. |
A new template is successfully created. The next step is to apply this
template to a target. Select the template that you just created and click
the Apply button.
Note: When applying a template to a target the user that is doing
the Apply operation needs at least Operator privileges on the destination
targets. Different templates can be applied to the same target. If these
templates contain the same metric, then the settings from previously applied
templates could be overwritten. Thus collaboration among administrators
is recommended when using templates. Administrators also have an option
to prevent templates from overriding a target's metric settings.
|
| 15. |
You have to select the destination target to which this template will
be applied. Click the Add button.
|
| 16. |
You can choose any set of targets or groups on which the template will
be applied. For this exercise, select the database target assigned to
you (see label on your workstation) and click the Select button.
|
| 17. |
You can select multiple targets or groups before you apply the template.
In this case you are only selecting one target. Click OK to apply
the template.
|
| 18. |
The new template is successfully applied to the selected target.
|
Back to Topic List
Groups are an efficient and effective way to logically organize,
manage, and monitor the components in your global environments. Each group has
its own group home page. The group home page shows the most important information
for the group and enables you to drill down for more information. The home page
shows the overall status of the group, including its current availability, a
rollup of alerts and violations, and critical patch advisories for members of
the group. Perform the following steps, to create and maintain groups:
|
1.
|
Click the Targets tab.
|
| 2. |
Click the Groups subtab.
|
| 3. |
Click the Add button to add a new group.
|
| 4. |
Specify the name for your group as Database and Host Group, as
you need to create Database and Hosts groups. Then click the Add
button in the Members section to add members.
|
| 5. |
The Search and Select page pops up in a different Explorer window.
Click the Target Type drop-down list, and change Target Type to
Host.
|
| 6. |
Select any 5 hosts and click the Select button.
|
| 7. |
Click the Add button again.
|
| 8. |
In the Search and Select page that pops up, change the Target
Type to Database Instance.
|
| 9. |
Select any 5 database targets and click the Select button.
|
| 10. |
Click the Charts subtab.
|
| 11. |
Notice that some default charts are available based on the type of members
that you have added. You need not edit these charts for this exercise.
Retain the defaults for now, and click the OK button.
|
| 12. |
Notice the Group Database and Host Groups has been added confirmation
message at the top of the page. Scroll down the page to locate your group
in the list of groups and click on its name.
|
| 13. |
The Group: Database and Host Groups home page appears. It provides
an overview of the overall status, alert, and policy violation information
for the group. The Charts page shows the performance charts for the group.
The Administration page provides a central point for running tasks collectively
against the group.
|
| 14. |
Review the group home page. Once you are done, launch the System Dashboard
by clicking the Launch Dashboard button on upper right corner of
the page.
|
| 15. |
Review the alert information presented to you in the System Dashboard.
Customize the dashboard, by clicking the
the Customize link on the upper right hand corner of the dashboard.
|
| 16. |
Uncheck the Show Alert Details box.
|
| 17. |
Click the Columns subtab.
|
| 18. |
The Edit Group : Database and Host Groups page will allow you
to select the metrics displayed in columns on the dashboard. Click the
Modify button.
|
| 19. |
Add 3 more database metrics to the dashboard. In the Available Columns
list, change Type to Database Instance.
|
| 20. |
Select any 3 database metrics. Double-click on the metric names one after
the other. This will move it to the Selected Columns list.
|
| 21. |
Click the Continue button.
|
| 22. |
The 3 metrics you selected should be on the list. You can change any
of the abbreviations for these metrics. Click the OK button
|
| 23. |
The System Dashboard now appears with your changes. Review the
dashboard, and click on the Group name at the upper left corner
of the dashboard to return back to the group home page.
|
| 24. |
The group home page appears.
|
Back to Topic List
SQL User-Defined Metrics (SQL UDMs) enables you to extend
monitoring of databases by plugging in your own SQL queries to monitor conditions
that are specific to your environment. The values returned by your queries can
be compared against the thresholds that you specify, and alerts are triggered
when thresholds are crossed. In Oracle Enterprise Manager 10g Release 2, SQL
UDMs have been enhanced in the following ways:
- SQL queries for SQL UDMs can return two-column, multirow
values.
- Thresholds can be defined on individual rows returned by
the SQL query.
- The format of the alert message can be customized.
- A "Test" button is provided to allow verification
of the SQL query and credentials.
Perform the following steps to create SQL User-Defined
Metrics:
| 1. |
Click the Databases subtab to access
the list of databases..
|
| 2. |
Select any one of the listed databases.
|
| 3. |
The Database homepage is displayed. Scroll down to the bottom of the
page and click User-Defined Metrics.
|
| 4. |
User-Defined SQL Metrics enable you to extend the monitoring of your
environment by defining new metrics to be monitored. New metrics are
defined by specifying your own SQL statements. The table shows you a
list of User-Defined Metrics defined for this database target. Click
the Create button to create a new SQL user-defined metric.
|
| 5. |
Enter the specifics for the User-Defined Metric. You can refer to the
instruction text on the page but generally you will need to enter the
Metric Name, select the Metric Type, SQL Query Output (the number of
values returned by your query - single value or two-column values) and
then enter the SQL Query. You can use your own query (see Note below
if you do so) or use the sample query as shown in the screenshot below
(select ename, sal from emp;).
For Database Credentials, you can use database user scott (with password
tiger). Specify the threshold information, customize the alert message
and specify the collection schedule. Feel free to use the sample settings
shown in the screenshot below. After all the required values are entered
click the Test button to verify the correct execution of the
SQL statement.
Note: When you use your own SQL query, the query must return
either a single scalar value or 2-column multi-row values. In the latter
case, the first column is the KEY and the second column is the VALUE.
The Metric Type for your User-Defined Metric should match the data type
of the VALUE column.
|
| 6. |
You can see that the test is successful. The test only shows the first
10 rows returned by the SQL statement. Click OK to continue.
|
| 7. |
You have successfully created a new SQL user-defined metric.
Based on the query and thresholds you specified, you may have to wait
for few minutes for an alert to be triggered for your metric.
|
Back to Topic List
In this lesson, you learned how to:
 |
Define Corrective Actions |
|
Review Corrective Actions |
|
Set up E-mail Notifications |
|
Use Monitoring Templates |
|
Create Groups |
|
Create SQL User-Defined Metric |
Back to Topic List
|
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.
|
Bookmark
