> ### Historical report descriptions

> When you click the Create Report link on the Fathom Reports home page, the Create Report page appears with a list of report templates divided into the following menu groups:

> - AppServer™ reports.
> - Database reports.
> - General reports.
> - System reports.
> - WebSpeedŽ reports.
> Note: Fathom supports management of the WebSpeedŽ Transaction Server product. Throughout this guide, WebSpeed Transaction Server and WebSpeed are used interchangeably.

> Any report templates or menu groups you create will also show on the Create Report page.

> Table 2–1 lists and describes each Fathom-provided report.

> Table 2–1: Fathom-provided reports
> Report name | Template name | Description
> --- | --- | ---
> AppServer Application Profile | appServerProfile | Provides information on procedures run by the broker, including: how many times the procedure ran, the average and maximum durations of each request, the number of successful requests, the number of errors, and the number of times each request quit and was stopped. The AppServer Application Profile report retrieves its data from the OE_ActASProc, OE_ActBrk, OE_ActSrv, and OE_APPService tables in the FathomTrendDatabase.
> AppServer Performance | appServerPerformance | Provides performance information on broker, client, and server activity. Broker activity information returned includes: number of complete requests, number of queued requests, percentage of queued requests, average and maximum request duration, average and maximum CPU use, and average and maximum memory use. Client activity information returned includes: average and maximum number of active clients, and average and maximum number of client requests. Server activity information returned includes: average and maximum CPU pool use, average and maximum memory pool use, average and maximum number of busy servers, average and maximum number of running servers, and average and maximum number of locked servers. The AppServer Performance report retrieves its data from the OE_ActBrk, OE_ActSrv, OE_APPService, and Sys_Process tables in the FathomTrendDatabase.
> Database After-imaging | dbAfterImage | Provides performance details for after-imaging, including: read and write activity, full and partial buffer activity, and AIW write status. The Database After-imaging report retrieves its data from the Db_ActLog in the FathomTrendDatabase.
> Database Area Status | dbAreaStatus | Provides trend status for each area within a database. Included in this report is information about total blocks, the high water mark, free blocks, available space (in blocks), and available space as a percentage of area. The Database Area Status report retrieves its data from the DB_AreaStatus table in the FathomTrendDatabase.
> Database Before-imaging | dbBeforeImage | Provides performance details for before-imaging, including: read and write activity; wait activity; full, partial, and empty buffer activity; and BIW statistics. This report also helps you determine the health of your BI subsystem by indicating increases in the amount of BI writes (which can indicate the growth of an application or questionable application design). The Database Before-Imaging report retrieves its data from the Db_ActLog and Db_ActIOType tables in the FathomTrendDatabase.
> Database Buffer I/O | dbMemory | Provides details about memory buffer usages for all buffers (database, BI, and AI). The information provided in the Database Memory Usage report helps you determine the proper use of OpenEdge memory on your machine. This report retrieves its data from the Db_ActBuf and Db_ActLog tables in the FathomTrendDatabase.
> Database Checkpointing | dbCheckpoint | Provides performance details for checkpoints. The Database Checkpointing report retrieves its data from the Db_Checkpoint table in the FathomTrendDatabase.
> Database Details | dbDetail | Provides information on all database tables and includes fields from almost every table, depending on relevance. Use this report to gather cross-functional information and to understand the relationship between different aspects of an OpenEdge database. The Database Details report retrieves information from the following FathomTrendDatabase tables: Db_ActBuf, Db_ActRec, Db_ActLog, Db_ActAPW, Db_ActIdx, Db_ActLock, Db_ActSum, and Db_ActIOType.
> Database Disk Information | dbDisk | Provides performance details for database reads and writes to disk, including: database read and write activity, BI file, AI file, and index reads and writes. This report helps you track the growth of your database and predict when you need more throughput. The Database Disk Information report retrieves its data from the Db_ActSum, Db_ActAPW, and Db_ActIOType tables in the FathomTrendDatabase.
> Database Index Analysis | dbIDXAnalysis | Provides analysis of index information gathered from the execution of the database analysis job. Information included in this report includes the maximum, minimum, and average of the following: number of blocks in the index, number of bytes in the index, utilization percentage of the block space, and number of index levels in the index. The Database Index Analysis report retrieves its information from the Db_IdxAnalysis table. Note: In order for the Database Index Analysis report to display data, the Database Analysis job must first be run against the desired database. For more information on the Database Analysis job, see the Database Management Guide.
> Database Index Usage | dbIndexStat | Provides performance details for each index in the schema, including the number of updates, creates, deletes, and blocks returned to the free chain. By showing which of your indexes are most active, this report helps you determine the structure of your database areas and where to place indexes. Combining the information presented in this report with that presented in the Database Table Usage report gives you a complete picture of database activity. The Database Index Utilization report retrieves its data from the Db_IndexStat table in the FathomTrendDatabase. Note: Fathom reports on a default of 50 tables. Use the startup parameter -`idxrangesize` to increase this number, if necessary. This parameter must be set on the production database when it is started.
> Database Locking | dbLocks | Provides performance details for record locking, based on the categories of requests, finds, locks, and waits. Each of the four categories contains information about exclusive, record, share, and upgrade locks. The Database Locking report retrieves its data from the Db_ActLock table in the FathomTrendDatabase.
> Database Record Information | dbRecord | Provides performance details for record locking, including information on increased record update activity, increased fragment activity, and increased record deletion. This report groups information into three categories: record, fragment, and bytes. Each category contains read, update, create, and delete fields. The Database Record Information report retrieves its data from the Db_ActRec table in the FathomTrendDatabase.
> Database Server Activity | dbServer | Provides detailed information about client activity on servers, including I/O for the server in bytes, records, and blocks. This report helps you assess the performance of your servers by showing how balanced or unbalanced the server activity is. The Database Server Activity report retrieves its information from the Db_ActServer table in the FathomTrendDatabase.
> Database Summary | dbSummary | Provides a summary of performance information for several subsections of a database, including: logical and physical I/O, buffer activity, BI file activity, AI file activity, page writer activity, index I/O, table I/O, and record activity. The Database Summary report retrieves its data from the following FathomTrendDatabase tables: Db_ActBuf, Db_ActSum, Db_ActRec, Db_ActLog, Db_ActAPW, Db_ActIdx, and Db_ActIOType.
> Database Table Analysis | dbTabAnalysis | Provides analysis of table information gathered from the execution of the database analysis job. This reports includes the maximum, minimum, and average for the following: record counts, the number of bytes in the table, the number of record fragments in the table, and the scatter factor. The Database Table Analysis report retrieves its data from the Db_TabAnalysis table. Note: In order for the Database Table Analysis report to display data, the Database Analysis job must first be run against the desired database. For more information on the Database Analysis job, see the Database Management Guide.
> Database Table Usage | dbTableStat | Provides performance details for each table in the schema, including information related to the number of table updates, creates, and deletes. This report tells you which tables are the most active, allowing you to better structure your database areas by moving tables. The Database Table Utilization report retrieves its data from the Db_TableStat table in the FathomTrendDatabase. Note: Fathom reports on a default of 50 tables. Use the startup parameter -`tablerangesize` to increase this number, if necessary. This parameter must be set on the production database when it is started.
> Resource Alert Detail | alertIndividual | Provides summary and detail information for alerts specific to a resource, including counts of the different types of alerts that have occurred, details of all severe alerts, and data entered when the alert was cleared. The Resource Alert Summary report retrieves its data from the Cf_Alert_Detail table in the FathomTrendDatabase.
> Resource Alert Summary | alertGeneral | Provides summary information about a site's alerts, including information sorted by the resource name. This report shows which of a site's resources cause the most problems. The Resource Alert Summary report retrieves its data from the Cf_Alert_Detail table in the FathomTrendDatabase.
> Resource Status Detail | statusDetail | Provides a detail of status states for a resource. This report provides information that includes a category for each status change reported in the time frame chosen. Also, there are specific details for each status change within the database. The Resource Status Detail report retrieves its information from the Cf_Status table.
> Resource Status Summary | statusSummary | Provides a summary of status states for all resources. This report provides information that includes a category for each status reported in the time frame chosen. The Resource Status Summary report retrieves its data from the Cf_Status table.
> CPU Summary | systemCPU | Provides a summary of the defined CPU resource's performance. This report helps you track how well the CPU works, the different areas it works in, and how often it works in each area. Use the information from this report to identify growth in CPU usage over time. The CPU Summary report retrieves its data from the Sys_CPU table in the FathomTrendDatabase. Note: If run for a multi-CPU system, this report returns information based on all the CPUs together. For further information on individual CPUs, refer to the appropriate vendor's information.
> File Summary | fileSummary | Provides size information about the defined file monitor. This report returns the average of the file size over the period being reported. Use this report to check the size of ASCII-based text files. This report does not typically deal with variable-length extents. The File Size Summary report retrieves its information from the Sys_FileSize table in the FathomTrendDatabase.
> Network Activity | network | Provides status summaries for the defined network resource, including the count of statuses received during the report period as well as the average response time of tests. Use the information in this report to monitor and flag potential network bottlenecks.
> System Disk Device Activity | systemDisk | Provides performance information for defined disk devices, including the relationship between disk reads and writes and the average queue length of disk activity. Use this report to identify disk bottlenecks and a decline in disk performance. The System Disk Device Activity report retrieves its data from the Sys_Dev table in the FathomTrendDatabase.
> System Filesystem Usage | systemFileSystem | Provides usage information for defined local or remote file systems, including how fast disk space grows from all software (including OpenEdge). Use this report to debug actual or potential file space problems where OpenEdge temporary files reside. The System Filesystem Usage report retrieves its data from the Sys_Filesys table in the FathomTrendDatabase.
> System Memory Summary | systemMemory | Provides a summary of the defined memory resource's performance. By detailing how much memory is used and how much is available, this report helps you identify growth in memory consumption. Combining the information in this report with that of the Database Buffer I/O report provides views of memory from the standpoint of both the system and OpenEdge. The System Memory Summary report retrieves this information from the Sys_Mem table in the FathomTrendDatabase.
> WebSpeed Application Profile | webSpeedProfile | Provides information on procedures run by the broker, including: how many times the procedure ran, the average and maximum durations of each request, the number of successful requests, the number of errors, and the number of times each request quit and was stopped. The WebSpeed Application Profile report retrieves its data from the OE_ActWSProc, OE_ActBrk, OE_ActSrv, and OE_APPService tables in the FathomTrendDatabase.
> WebSpeed Performance | webSpeedPerformance | Provides performance information on broker, client, and agent activity. Broker activity information returned includes number of complete requests, number of queued requests, percentage of queued requests, average and maximum request duration, average and maximum CPU use, and average and maximum memory use. Client activity information returned includes average and maximum number of active clients and average and maximum number of client requests. Server activity information returned includes average and maximum CPU pool use, average and maximum memory pool use, average and maximum number of busy servers, average and maximum number of running servers, and average and maximum number of locked servers. The WebSpeed Performance report retrieves its data from the OE_ActBrk, OE_ActSrv, OE_APPService, and Sys_Process tables in the FathomTrendDatabase.

> For more information about FathomTrendDatabase tables, see the FathomTrendDatabase Guide and Reference.

Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095