|
Oracle Enterprise Manager (EM) lets you monitor
the Oracle9i platform in smarter, more efficient ways.
Using the EM event system, you can be assured that your
systems are being monitored reliably and efficiently.
For example, you can have critical performance metrics checked
every 5 minutes, and schedule more resource-intensive checks
for index fragmentation during off-peak times.
During scheduled maintenance, you can set up blackout periods
that suspend monitoring to prevent false alerts when systems
are intentionally brought down. Event Schedules
and Blackouts are the two key features in the EM event system
that provide this type of efficiency and flexibility.
These allow you to set up monitoring when it is needed and
prevents false alerts when it is not.
Event Schedules allow you to specify
when and how often key availability and performance metrics
in your Oracle environment should be checked. For example,
you may want critical Alert log errors to be checked every
5 minutes, and more resource intensive checks of space
usage to occur at the end of the business day. Using
event schedules, EM (via the Intelligent Agent) monitors
each metric at its appropriate times and frequencies.
This ensures monitoring is aligned to what's critical in your
environment while providing efficient utilization of your
resources.
Event Schedules are specified during event
creation time and include the following options:
- On Interval --
Specifies EM should check the metric condition on intervals
of minutes or hours or days
- On Day of Week -- Specifies EM should
check the metric condition on specified days of the week
- On Day of Month -- Specifies EM should
check the metric condition on specified days of the month
The event schedule in Figure 1 below shows
the "On Interval" option used.
Figure 1: You can define
an event schedule to check performance metrics every
5 minutes.
Blackouts, on the other hand, allow
you to suspend monitoring when it makes sense to do so.
This is typically during times of planned maintenance or
unplanned emergency operations when systems are brought
down. During these times, maintenance work needs
to be performed efficiently and in a timely manner to minimize
unavailability of your systems. It is during
these critical periods that monitoring can be suspended
to prevent disruptive false alerts for systems that you
intentionally brought down.
You set blackouts via EM's Intelligent Agent
command line utility, agentctl. You can set
a blackout to be in effect for minutes, hours or days.
You can blackout a particular database on a node, or all
databases on the node. When a blackout is set, monitoring
for the blacked out service is temporarily suspended.
It resumes when the blackout ends or when a command is issued
to stop the blackout. Providing blackout functionality
in a command-line utility allows you to easily incorporate
blackout logic in your service maintenance scripts.
Furthermore, using the Enterprise Manager job system,
these maintenance scripts can be executed unattended during
scheduled maintenance periods.
Figure 2: During maintenance,
you can suspend the monitoring of a database via blackouts
Hence, event monitoring must not only be
comprehensive and reliable, it must be flexible enough to
operate within the normal workflow of your environment.
EM's Event Schedules and Blackouts lets you monitor the
Oracle environment in more efficient, effective and smarter
ways.
More
Info
Oracle9i
Database Daily Features
|
Bookmark
