Oracle® Email Administrator's Guide Release 2 (9.0.4.1) Part Number B10720-02 |
|
|
View PDF |
This chapter describes how to collect and view Oracle Email system statistics using the oesmon
monitoring utility and the oeschart
charting utility.
This chapter contains the following topics:
The oesmon
utility obtains raw metric data directly from Oracle Email server processes and provides a summary of the mail system's statistics. Each statistic is represented by either an ASCII string or a number, rendered in keyword-value pairs.
oesmon
provides the syntax options listed in Table 7-1.
Oracle Email has nine service types, such as the IMAP service. These services can run on the same host or on separate hosts. One or more instance of a service can be running on a host. The oesmon
utility collects statistical information on a service on a host (target). Targets are named as a concatenation of:
host:um_system:service_type
where:
host
is the name of the host where the service is runningservice_type
is one of the following:
All statistics and managed objects have names. Names are case sensitive and contain only alphanumeric characters and the underscore character. Statistic names are hierarchical and separated by a period (.). A request for a managed object returns all of the managed objects and statistics beneath it.
See Also:
Appendix E, "Server Statistics" for a complete list of the available statistics |
Consider the following example:
oesmon get mycomputer:um_system:pop .um.admin
In this case, two values are returned for the two metric objects in the hierarchy:
.um.admin.os_pid = 8239 .um.admin.uptime = Wed Jan 29 14:17:36 2003 .um.admin.log.discard = 0 .um.admin.log.total = 100
where:
.um.admin.log.discard
is the number of log messages discarded when high log levels cause log messages to be generated faster than they can be written to disk..um.admin.log.total
is the total number of log messages logged by the processes, including the ones that are discarded and written to disk.
oesmon get mycomputer:um_system:pop .um.admin.os_pid
Only the process identifier is returned.
.um.admin.os_pid = 8239
See Also:
Appendix E, "Server Statistics" for more information on server statistics. |
Oracle Email servers track a range of metrics that are periodically stored in a set of mail statistics tables. The oeschart
utility generates charts and images that can be used to publish reports and Web pages; providing a company with a graphic picture of the status of the mail system implementation.
This section contains the following topics:
You can set the frequency by which metrics are sampled and recorded using the oidadmin
administration tool provided by Oracle Internet Directory.
The orclMailAdminCollectionInterval
parameter specifies the number of seconds that elapse between statistics collecting. A setting of zero (0) seconds stops the service from logging statistics altogether.
You should set the orclMailAdminCollectionInterval
parameter at the target level, rather than the instance level. If you set the value at the instance level, statistics collection occurs at different intervals for each instance of the same type of mail service.
Collecting statistics at the same interval for all server types is not recommended. The collection process utilizes different amounts of resources and collects statistics of varying degrees, depending on which mail service is engaged in collecting the statistics. For example, the housekeeping collection process is more resource intensive and collects fewer dynamic statistics than the SMTP server collection process.
The recommended collection intervals for the different types of servers are:
Perform the following steps to clean up mail statistics through the housekeeping process:
Statistics Cleanup
parameter.Tertiary
Storage
Age
Threshold
parameter to the number of days you want to retain sample data.Each mail process has a default store database. Processes supporting multiple stores, such as the IMAP server, have a default store that is set in the orclMailAdminStoreDN
parameter during the installation of each middle tier.
Statistical information is stored in tables in the esperftbl
tablespace in the default mail store of the process. Because these tables can expand indefinitely, you should monitor the esperftbl
tablespace and delete or export data as needed.
The schema consists of the following:
The es_perf_process
table is a list of the process instance records. The column process_dn
is the complete distinguished name (DN) of the process, found in Oracle Internet Directory. The processes that produce metric data insert records into this table as needed.
Column Name | Valid Values | Description |
---|---|---|
|
Number (not null) |
An internal assigned unique number for each process |
|
Varchar2 (500) |
The DN of the process in Oracle Internet Directory |
The es_perf_timestamp
table records each time metric data is stored into the tables. This table, along with the es_perf_data
table grows without bound over time. You must clean out historic data that is no longer needed for charting or analysis at their installation. This can be done by configuring the housekeeping process.
Column Name | Value | Description |
---|---|---|
|
Number |
Internally assigned unique number for each time period that a process enters a statistics time stamp |
|
Date |
Time the data was inserted |
The es_perf_sample
table records each metric at each timestamp. This table increases over time, so you must delete data that is no longer required in order to keep the table size manageable.
There are two possible columns that store the sample data, depending upon whether the data is numerical (nvalue
) or a string (svalue
).
es_perf_data
is a view of the tables described in this section: es_perf_process, es_perf_metric
, es_perf_timestamp
, and es_perf_sample
.
The oeschart
utility creates graphs. The utility requires a single command-line parameter that points to a property file. The property file is a text file with keyword value pairs defining the information the utility needs to generate the graph. A valid property file would have the following mandatory and optional parameters.
The following tables describe mandatory entries and optional values:
The following is an example of a property file that informs the oeschart
utility to generate an xy graph of the number of concurrent IMAP sockets for all IMAP servers in aggregate over the last twenty four hours:
server=testdb.us.oracle.com sid=test port=1521 process_dn=test1:um_system:imap: metric_name=.ES_SPS.socket.currload graph_type=xy_current image_file_name=socketcount image_title=Socket count on test1 image_dir=./ number_of_hours=24 encode_type=png show_statistics=true aggregate_time_period=600 debug=false max_lifetime=120
oeschart
obtains information from the es_perf
schema and generates one of four possible types of charts. Three of these are variations of scatter graphs. The fourth is a bar chart.
By executing oeschart
in regular intervals, you are provided with a current view that can be published on a company Web site or within Oracle Enterprise Manager.
For example, you can schedule the creation of graphs that show information such as the number of connected sockets, the log in response time, and the number of queued outbound messages, and publish the results in a custom HTML page or in Oracle Enterprise Manager.
To display graphs in Oracle Enterprise Manager:
The $ORACLE_HOME/emdw/sysman/admin/metadata
directory contains a list of target metadata definition files.
For a particular target definition, add the following elements to the InstanceProperties
section:
<!--This property specifies the total number of statistic charts to be displayed --> <InstanceProperty NAME="totalNumberOfStats" CREDENTIAL="FALSE" OPTIONAL="TRUE"> <Display> <Label NLSID="totalnumberofstats">Total Number of Statistics</Label> </Display> </InstanceProperty> <!--This property specifies the header title for the first charting picture --> <InstanceProperty NAME="Title0" CREDENTIAL="FALSE" OPTIONAL="TRUE"> <Display> <Label NLSID="stat0">Statistic Number 0</Label> </Display> </InstanceProperty> <!--This property specifies the tool tips string for the first charting picture, coded to Section 508 standards--> <InstanceProperty NAME="ToolTips0" CREDENTIAL="FALSE" OPTIONAL="TRUE"> <Display> <Label NLSID="tooltips0">This is tooltips 0 for ADA</Label> </Display> </InstanceProperty> <!--This property specifies the relative picture path under the servlet for the first charting pictyre.--> <InstanceProperty NAME="PicPath0" CREDENTIAL="FALSE" OPTIONAL="TRUE"> <Display> <Label NLSID="picpath0">Picture Path 0</Label> </Display> </InstanceProperty> <!--This property specifies the physical path for the first charting picture. The admin code will test if the file exists according to the path below--> <InstanceProperty NAME="PicPhysicalPath0" CREDENTIAL="FALSE" OPTIONAL="TRUE"> <Display> <Label NLSID="picphysicalpath0">Picture Physical Path 0</Label> </Display> </InstanceProperty>
To increase the number of charts displayed, change the value of the totalNumberOfStats
parameter in the targets.xml
file accordingly, and the additional picture properties must be defined using the following naming standard:
Title[
N
],
ToolTips[
N
],
PicPath[
N
],
PicPhysicalPath[
N
]
Where:
N
is a non-negative natural number
targets.xml
file to specify the property instance values, by adding the following properties to the specific target section in $ORACLE_HOME/emdw/sysman/emd/targets.xml
:
<Property NAME="totalNumberOfStats" VALUE="1"/> <Property NAME="ToolTips0" VALUE="My First Statistic Tool Tips"/> <Property NAME="PicPhysicalPath0" VALUE="<...>/sysman/webapps/emd/ias/umsg/es/images/pic1.gif"/> <Property NAME="PicPath0" VALUE="/emd/ias/umsg/es/images/pic1.gif"/> <Property NAME="Title0" VALUE="My First Statistic Header"/>
If any of the following situations occur, the charting picture is skipped and not displayed in Oracle Enterprise Manager.
totalNumberOfStats
is missing, zero, or not a numberTitle[N]
is missing for the particular chartToolTips[N]
is missing for the particular chartPicPath[N]
is missing for the particular chartPicPhysicalPath[N]
is missing for the particular chartPicPhysicalPath[N]
does not exist