OpenEdge Management: Reporting
-
Upload
ciro-antunes -
Category
Documents
-
view
236 -
download
0
Transcript of OpenEdge Management: Reporting
-
8/9/2019 OpenEdge Management: Reporting
1/90
OPENEDGE
10PROGRESS
OpenEdgeManagement:Reporting
-
8/9/2019 OpenEdge Management: Reporting
2/90
2009 Progress Software Corporation and/or its subsidiaries or affiliates. All rights reserved.
These materials and all Progress software products are copyrighted and all rights are reserved by Progress Software Corporation. The
information in these materials is subject to change without notice, and Progress Software Corporation assumes no responsibility for any
errors that may appear therein. The references in these materials to specific platforms supported are subject to change.
Actional, Apama, Apama (and Design), Artix, Business Empowerment, DataDirect (and design), DataDirect Connect, DataDirect
Connect64, DataDirect Technologies, DataDirect XML Converters, DataDirect XQuery, DataXtend, Dynamic Routing Architecture,EdgeXtend, Empowerment Center, Fathom, IntelliStream, IONA, IONA (and design), Making Software Work Together, Mindreef,
ObjectStore, OpenEdge, Orbix, PeerDirect, POSSENET, Powered by Progress, PowerTier, Progress, Progress DataXtend, Progress
Dynamics, Progress Business Empowerment, Progress Empowerment Center, Progress Empowerment Program, Progress OpenEdge,
Progress Profiles, Progress Results, Progress Software Developers Network, Progress Sonic, ProVision, PS Select, SequeLink, Shadow,
SOAPscope, SOAPStation, Sonic, Sonic ESB, SonicMQ, Sonic Orchestration Server, SonicSynergy, SpeedScript, Stylus Studio,
Technical Empowerment, WebSpeed, Xcalia (and design), and Your Software, Our TechnologyExperience the Connection are
registered trademarks of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and/or other countries.
AccelEvent, Apama Dashboard Studio, Apama Event Manager, Apama Event Modeler, Apama Event Store, Apama Risk Firewall,
AppsAlive, AppServer, ASPen, ASP-in-a-Box, BusinessEdge, Business Making Progress, Cache-Forward, DataDirect Spy, DataDirect
SupportLink, Fuse, Fuse Mediation Router, Fuse Message Broker, Fuse Services Framework, Future Proof, GVAC, High Performance
Integration, ObjectStore Inspector, ObjectStore Performance Expert, OpenAccess, Orbacus, Pantero, POSSE, ProDataSet, Progress ESP
Event Manager, Progress ESP Event Modeler, Progress Event Engine, Progress RFID, Progress Software Business Making Progress,
PSE Pro, SectorAlliance, SeeThinkAct, Shadow z/Services, Shadow z/Direct, Shadow z/Events, Shadow z/Presentation, Shadow Studio,
SmartBrowser, SmartComponent, SmartDataBrowser, SmartDataObjects, SmartDataView, SmartDialog, SmartFolder, SmartFrame,SmartObjects, SmartPanel, SmartQuery, SmartViewer, SmartWindow, Sonic Business Integration Suite, Sonic Process Manager, Sonic
Collaboration Server, Sonic Continuous Availability Architecture, Sonic Database Service, Sonic Workbench, Sonic XML Server,
StormGlass, The Brains Behind BAM, WebClient, Who Makes Progress, and Your World. Your SOA. are trademarks or service marks
of Progress Software Corporation or one of its affiliates or subsidiaries in the U.S. and other countries. Java and all Java-based marks
are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Any other trademarks contained
herein are the property of their respective owners.
For the latest documentation updates see OpenEdge Product Documentation on PSDN (http://communities.progress.com/
pcom/docs/DOC-16074).
December 2009
Last updated with new content: Release 10.2B Product Code: 4496; R10.2B
Third party acknowledgements See the Third party acknowledgements sectionon page Preface8.
-
8/9/2019 OpenEdge Management: Reporting
3/90
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface1
1. Understanding Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
OpenEdge Management report terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
OpenEdge Management report types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Report instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Create Report page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Report Edit page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Creating a report instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2. Historical Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Overview of historical reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Working with report templates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Historical report descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Customizing graphical output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Graphical output environment variables . . . . . . . . . . . . . . . . . . . . . . . . . 212
Report output field and column headings . . . . . . . . . . . . . . . . . . . . . . . . 216
3. Working with Report Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Scheduling reports to run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Viewing report output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Viewing report history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Scheduled reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Completed reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Running reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
4. Creating Custom Report Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Creating a custom report template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Editing the report template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Copying the report template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Deleting the report template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Importing and exporting report templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
-
8/9/2019 OpenEdge Management: Reporting
4/90
Contents
Contents2
5. Real-time Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
System Information report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
System Activity report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Open Alert Detail report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Hotspot report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Database Summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Open Alert Summary report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6. OpenEdge Management Diagnostic Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Viewing OpenEdge Management log files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
OpenEdge Management Task Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
OpenEdge Management Work Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index1
-
8/9/2019 OpenEdge Management: Reporting
5/90
Contents
Contents3
Figures
Figure 11: OpenEdge Management Reports Details page . . . . . . . . . . . . . . . . . . 13
Figure 12: Reports list frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 21: CPU Summary output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Figure 22: Customized graph output for CPU Summary . . . . . . . . . . . . . . . . . . . . 213Figure 23: AppServer Application Profile output . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 24: Request duration graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 25: Return code success graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Figure 26: Run count graph . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Figure 31: Sample Database Area Status report output . . . . . . . . . . . . . . . . . . . . 34
Figure 51: Real-time reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
-
8/9/2019 OpenEdge Management: Reporting
6/90
Contents
Contents4
Tables
Table 21: OpenEdge Management-provided reports . . . . . . . . . . . . . . . . . . . . . . 23
Table 22: AppServer Application Profile column headings . . . . . . . . . . . . . . . . . . 216
Table 23: AppServer Client Activity column headings . . . . . . . . . . . . . . . . . . . . . 216
Table 24: AppServer Broker Activity column headings . . . . . . . . . . . . . . . . . . . . . 216Table 25: AppServer Activity column headings . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Table 26: Database After-Imaging column headings . . . . . . . . . . . . . . . . . . . . . . 217
Table 27: Database Area Status column headings . . . . . . . . . . . . . . . . . . . . . . . . 217Table 28: Database Before-Imaging fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Table 29: Database Checkpointing column headings . . . . . . . . . . . . . . . . . . . . . . 217
Table 210: Database Details fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Table 211: Database Disk Information fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Table 212: Database Index Analysis column headings . . . . . . . . . . . . . . . . . . . . . 219
Table 213: Database Index Utilization column headings . . . . . . . . . . . . . . . . . . . . 219
Table 214: Database Locking fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Table 215: Database Buffer I/O fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Table 216: Database Record Information fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Table 217: Database Server Activity column headings . . . . . . . . . . . . . . . . . . . . . . 220
Table 218: Database Summary fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Table 219: Database Table Analysis column headings . . . . . . . . . . . . . . . . . . . . . 221Table 220: Database Table Usage column headings . . . . . . . . . . . . . . . . . . . . . . . 221
Table 221: CPU Summary fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Table 222: File Summary column headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Table 223: Network Activity column headings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Table 224: System Disk Device Activity column headings . . . . . . . . . . . . . . . . . . . 222
Table 225: System Filesystem Usage column headings . . . . . . . . . . . . . . . . . . . . 222
Table 226: System Memory Summary column headings . . . . . . . . . . . . . . . . . . . . 222
Table 227: WebSpeed Application Profile column headings . . . . . . . . . . . . . . . . . 223Table 228: WebSpeed Client Activity column headings . . . . . . . . . . . . . . . . . . . . . 223
Table 229: WebSpeed Broker Activity column headings . . . . . . . . . . . . . . . . . . . . 223
Table 230: WebSpeed Server Activity column headings . . . . . . . . . . . . . . . . . . . . 223
Table 51: System Information report details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Table 52: System Activity report details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Table 61: Task Scheduler Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
-
8/9/2019 OpenEdge Management: Reporting
7/90
Preface
This Preface contains the following sections:
Purpose
Audience
Organization
Using this manual
Typographical conventions
Examples of syntax descriptions
OpenEdge messages
Third party acknowledgements
-
8/9/2019 OpenEdge Management: Reporting
8/90
Preface
Preface2
Purpose
This guide describes how to create and run reports using OpenEdge Management.
Audience
This manual is designed for users of the OpenEdge Management product. Typical users are
OpenEdge database administrators and any others responsible for the daily management of an
OpenEdge database.
Organization
Chapter 1, Understanding Reports
Introduces OpenEdge Management report types and OpenEdge Management report
terminology and contains steps for creating a report instance.
Chapter 2, Historical Reports
Describes the trend report templates supplied by OpenEdge Management.
Chapter 3, Working with Report Instances
Explains how to schedule reports and view report output. Also contains steps for working
with scheduled, completed, and running reports.
Chapter 4, Creating Custom Report Templates
Describes how to create, edit, copy, delete, import, and export custom report templates.
Chapter 5, Real-time Reports
Provides a description of each real-time report.
Chapter 6, OpenEdge Management Diagnostic Reports
Provides an overview of the reports used to debug OpenEdge Management. Includes
information on the OpenEdge Management log file and the work scheduler.
-
8/9/2019 OpenEdge Management: Reporting
9/90
Preface
Preface3
Using this manual
OpenEdge provides a special purpose programming language for building business
applications. In the documentation, the formal name for this language isABL (Advanced
Business Language). With few exceptions, all keywords of the language appear in all
UPPERCASE, using a font that is appropriate to the context. All other alphabetic language content
appears in mixed case.
For the latest documentation updates, see the OpenEdge Product Documentation category on
PSDN (http://communities.progress.com/pcom/docs/DOC-16074).
References to ABL compiler and run-time features
ABL is both a compiled and an interpreted language that executes in a run-time engine. The
documentation refers to this run-time engine as theABL Virtual Machine (AVM). When the
documentation refers to ABL source code compilation, it specifiesABLor the compileras the
actor that manages compile-time features of the language. When the documentation refers to
run-time behavior in an executing ABL program, it specifies the AVMas the actor that managesthe specified run-time behavior in the program.
For example, these sentences refer to the ABL compilers allowance for parameter passing and
the AVMs possible response to that parameter passing at run time: ABL allows you to pass a
dynamic temp-table handle as a static temp-table parameter of a method. However, if at run time
the passed dynamic temp-table schema does not match the schema of the static temp-table
parameter, the AVM raises an error. The following sentence refers to run-time actions that the
AVM can perform using a particular ABL feature: The ABL socket object handle allows the
AVM to connect with other ABL and non-ABL sessions using TCP/IP sockets.
References to ABL data types
ABL provides built-in data types, built-in class data types, and user-defined class data types.
References to built-in data types follow these rules:
Like most other keywords, references to specific built-in data types appear in all
UPPERCASE, using a font that is appropriate to the context. No uppercase reference ever
includes or implies any data type other than itself.
Wherever integerappears, this is a reference to the INTEGERor INT64data type.
Wherever character appears, this is a reference to the CHARACTER,LONGCHAR, or CLOBdatatype.
Wherever decimalappears, this is a reference to the DECIMALdata type.
Wherever numericappears, this is a reference to the INTEGER, INT64, or DECIMALdata type.
References to built-in class data types appear in mixed case with initial caps, for example,
Progress.Lang.Object. References to user-defined class data types appear in mixed case, as
specified for a given application example.
-
8/9/2019 OpenEdge Management: Reporting
10/90
Preface
Preface4
Typographical conventions
This manual uses the following typographical conventions:
Convention Description
Bold Bold typeface indicates commands or characters the user types,provides emphasis, or the names of user interface elements.
Italic Italic typeface indicates the title of a document, or signifies newterms.
SMALL, BOLD
CAPITAL LETTERSSmall, bold capital letters indicate OpenEdge key functions andgeneric keyboard keys; for example, GETand CTRL.
KEY1+KEY2 A plus sign between key names indicates a simultaneouskeysequence: you press and hold down the first key while pressing thesecond key. For example, CTRL+X.
KEY1 KEY2 A space between key names indicates a sequentialkey sequence:you press and release the first key, then press another key. Forexample, ESCAPE H.
Syntax:
Fixed width A fixed-width font is used in syntax statements, code examples,system output, and filenames.
Fixed-width italics Fixed-width italics indicate variables in syntax statements.
Fixed-width bold Fixed-width bold indicates variables with special emphasis.
UPPERCASEfixed width
Uppercase words are ABL keywords. Although these are alwaysshown in uppercase, you can type them in either uppercase orlowercase in a procedure.
This icon (three arrows) introduces a multi-step procedure.
This icon (one arrow) introduces a single-step procedure.
Period (.)orcolon (:)
All statements except DO, FOR, FUNCTION, PROCEDURE, and REPEATend with a period. DO, FOR, FUNCTION, PROCEDURE, and REPEATstatements can end with either a period or a colon.
[] Large brackets indicate the items within them are optional.
[ ] Small brackets are part of ABL.
{} Large braces indicate the items within them are required. They areused to simplify complex syntax diagrams.
{ } Small braces are part of ABL. For example, a called externalprocedure must use braces when referencing arguments passed bya calling procedure.
-
8/9/2019 OpenEdge Management: Reporting
11/90
Preface
Preface5
Examples of syntax descriptions
In this example, ACCUMis a keyword, and aggregate and expressionare variables:
FORis one of the statements that can end with either a period or a colon, as in this example:
In this example, STREAMstream, UNLESS-HIDDEN, and NO-ERRORare optional:
In this example, the outer (small) brackets are part of the language, and the inner (large) brackets
denote an optional item:
A called external procedure must use braces when referencing compile-time arguments passed
by a calling procedure, as shown in this example:
In this example, EACH, FIRST, and LASTare optional, but you can choose only one of them:
| A vertical bar indicates a choice.
... Ellipses indicate repetition: you can choose one or more of thepreceding items.
Convention Description
Syntax
ACCUM aggregate expression
FOR EACH Customer NO-LOCK:
DISPLAY Customer.Name.
END.
Syntax
DISPLAY [STREAM stream][UNLESS-HIDDEN ][NO-ERROR ]
Syntax
INITIAL [ constant[, constant]]
Syntax
{&argument-name }
Syntax
PRESELECT [EACH |FIRST |LAST ]record-phrase
-
8/9/2019 OpenEdge Management: Reporting
12/90
Preface
Preface6
In this example, you must include two expressions, and optionally you can include more.
Multiple expressions are separated by commas:
In this example, you must specify MESSAGEand at least one expressionor SKIP[(n) ], and
any number of additional expressionor SKIP[( n ) ]is allowed:
In this example, you must specify {include-file, then optionally any number of argumentor
&argument-name = "argument-value", and then terminate with }:
Long syntax descriptions split across lines
Some syntax descriptions are too long to fit on one line. When syntax descriptions are split
across multiple lines, groups of optional and groups of required items are kept together in the
required order.
In this example, WITHis followed by six optional items:
Syntax
MAXIMUM ( expression, expression[, expression]...)
Syntax
MESSAGE {expression|SKIP [( n ) ]}...
Syntax
{ include-file
[argument|&argument-name = "argument-value"]...}
Syntax
WITH [ACCUM max-length][expressionDOWN ]
[CENTERED ][nCOLUMNS ][SIDE-LABELS ]
[STREAM-IO ]
-
8/9/2019 OpenEdge Management: Reporting
13/90
Preface
Preface7
Complex syntax descriptions with both required and
optional elements
Some syntax descriptions are too complex to distinguish required and optional elements by
bracketing only the optional elements. For such syntax, the descriptions include both braces (for
required elements) and brackets (for optional elements).
In this example, ASSIGNrequires either one or more fieldentries or one record. Options
available with fieldor recordare grouped with braces and brackets:
OpenEdge messages
OpenEdge displays several types of messages to inform you of routine and unusual occurrences:
Execution messagesinform you of errors encountered while OpenEdge is running a
procedure; for example, if OpenEdge cannot find a record with a specified index field
value.
Compile messagesinform you of errors found while OpenEdge is reading and analyzing
a procedure before running it; for example, if a procedure references a table name that is
not defined in the database.
Startup messagesinform you of unusual conditions detected while OpenEdge is getting
ready to execute; for example, if you entered an invalid startup parameter.
After displaying a message, OpenEdge proceeds in one of several ways:
Continues execution, subject to the error-processing actions that you specify or that are
assumed as part of the procedure. This is the most common action taken after execution
messages.
Returns to the Procedure Editor, so you can correct an error in a procedure. This is the
usual action taken after compiler messages.
Halts processing of a procedure and returns immediately to the Procedure Editor. This
does not happen often.
Terminates the current session.
OpenEdge messages end with a message number in parentheses. In this example, the message
number is 200:
If you encounter an error that terminates OpenEdge, note the message number before restarting.
Syntax
ASSIGN { [FRAME frame]{field[= expression]}
[WHEN expression]}...
| {record[EXCEPT field...]}
** Unknown table name table.(200)
-
8/9/2019 OpenEdge Management: Reporting
14/90
Preface
Preface8
Obtaining more information about OpenEdge messages
In Windows platforms, use OpenEdge online help to obtain more information about OpenEdge
messages. Many OpenEdge tools include the following Help menu options to provide
information about messages:
Choose Help Recent Messagesto display detailed descriptions of the most recent
OpenEdge message and all other messages returned in the current session.
Choose HelpMessagesand then type the message number to display a description of a
specific OpenEdge message.
In the Procedure Editor, press the HELPkey or F1.
On UNIX platforms, use the OpenEdge procommand to start a single-user mode character
OpenEdge client session and view a brief description of a message by providing its number.
To use the pro command to obtain a message description by message number:
1. Start the Procedure Editor:
2. Press F3to access the menu bar, then choose HelpMessages.
3. Type the message number and press ENTER. Details about that message number appear.
4. Press F4to close the message, press F3to access the Procedure Editor menu, and choose
File Exit.
Third party acknowledgements
OpenEdge includes AdventNet - Agent Toolkit licensed from AdventNet, Inc.
http://www.adventnet.com. All rights to such copyright material rest with AdventNet.
OpenEdge includes ANTLR (Another Tool for Language Recognition) software Copyright
2003-2006, Terence Parr All rights reserved. Neither the name of the author nor the names of
its contributors may be used to endorse or promote products derived from this software without
specific prior written permission. Software distributed on an AS IS basis, WITHOUTWARRANTY OF ANY KIND, either express or implied. See the License for the specific
language governing rights and limitations under the License agreement that accompanies the
product.
OpenEdge includes software developed by the Apache Software Foundation
(http://www.apache.org/). Copyright 1999 The Apache Software Foundation. All rights
reserved (Xerces C++ Parser (XML) and Xerces2 Java Parser (XML)); Copyright 1999-2002
The Apache Software Foundation. All rights reserved (Xerces Parser (XML); and Copyright
2000-2003 The Apache Software Foundation. All rights reserved (Ant). The names Apache,
Xerces, ANT, and Apache Software Foundation must not be used to endorse or promote
products derived from this software without prior written permission. Products derived from
this software may not be called Apache, nor may Apache appear in their name, without
OpenEdge-install-dir/bin/pro
-
8/9/2019 OpenEdge Management: Reporting
15/90
Preface
Preface9
prior written permission of the Apache Software Foundation. For written permission, please
contact [email protected]. Software distributed on an AS IS basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the License for the specific
language governing rights and limitations under the License agreement that accompanies the
product.
OpenEdge includes Concurrent Java software Copyright 1994-2000 Sun Microsystems, Inc. All
Rights Reserved. -Neither the name of or trademarks of Sun may be used to endorse or promoteproducts including or derived from the Java Software technology without specific prior written
permission; and Redistributions of source or binary code must contain the above copyright
notice, this notice and the following disclaimers: This software is provided "AS IS," without a
warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS
AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN MICROSYSTEMS, INC. AND
ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY
LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE
SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN MICROSYSTEMS, INC.
OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, ORFOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE
DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF
LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE,
EVEN IF SUN MICROSYSTEMS, INC. HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
OpenEdge includes DataDirect software Copyright 1991-2007 Progress Software
Corporation and/or its subsidiaries or affiliates. All Rights Reserved. (DataDirect Connect for
JDBC Type 4 driver); Copyright 1993-2009 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved. (DataDirect Connect for JDBC); Copyright
1988-2007 Progress Software Corporation and/or its subsidiaries or affiliates. All RightsReserved. (DataDirect Connect for ODBC); and Copyright 1988-2007 Progress Software
Corporation and/or its subsidiaries or affiliates. All Rights Reserved. (DataDirect Connect64
for ODBC).
OpenEdge includes DataDirect Connect for ODBC and DataDirect Connect64 for ODBC
software, which include ICU software 1.8 and later - Copyright 1995-2003 International
Business Machines Corporation and others All rights reserved. Permission is hereby granted,
free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation
the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so, provided that the above
copyright notice(s) and this permission notice appear in all copies of the Software and that both
the above copyright notice(s) and this permission notice appear in supporting documentation.
OpenEdge includes DataDirect Connect for ODBC and DataDirect Connect64 for ODBC
software, which include software developed by the OpenSSL Project for use in the OpenSSL
Toolkit (http:/www.openssl.org/). Copyright 1998-2006 The OpenSSL Project. All rights
reserved. And Copyright 1995-1998 Eric Young ([email protected]). All rights reserved.
OpenEdge includes DataDirect products for the Microsoft SQL Server database which contain
a licensed implementation of the Microsoft TDS Protocol.
OpenEdge includes software authored by David M. Gay. Copyright 1991, 2000, 2001 byLucent Technologies (dtoa.c); Copyright 1991, 1996 by Lucent Technologies (g_fmt.c); and
mailto:[email protected]:[email protected] -
8/9/2019 OpenEdge Management: Reporting
16/90
Preface
Preface10
Copyright 1991 by Lucent Technologies (rnd_prod.s). Permission to use, copy, modify, and
distribute this software for any purpose without fee is hereby granted, provided that this entire
notice is included in all copies of any software which is or includes a copy or modification of
this software and in all copies of the supporting documentation for such software. THIS
SOFTWARE IS BEING PROVIDED "AS IS", WITHOUT ANY EXPRESS OR IMPLIED
WARRANTY. IN PARTICULAR, NEITHER THE AUTHOR NOR LUCENT MAKES ANY
REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR
PURPOSE.
OpenEdge includes software authored by David M. Gay. Copyright 1998-2001 by Lucent
Technologies All Rights Reserved (decstrtod.c; strtodg.c); Copyright 1998, 2000 by Lucent
Technologies All Rights Reserved (decstrtof.c; strtord.c); Copyright 1998 by Lucent
Technologies All Rights Reserved (dmisc.c; gdtoa.h; gethex.c; gmisc.c; sum.c); Copyright
1998, 1999 by Lucent Technologies All Rights Reserved (gdtoa.c; misc.c; smisc.c; ulp.c);
Copyright 1998-2000 by Lucent Technologies All Rights Reserved (gdtoaimp.h); Copyright
2000 by Lucent Technologies All Rights Reserved (hd_init.c). Full copies of these licenses
can be found in the installation directory, in the c:/OpenEdge/licenses folder. Permission to use,
copy, modify, and distribute this software and its documentation for any purpose and withoutfee is hereby granted, provided that the above copyright notice appear in all copies and that both
that the copyright notice and this permission notice and warranty disclaimer appear in
supporting documentation, and that the name of Lucent or any of its entities not be used in
advertising or publicity pertaining to distribution of the software without specific, written prior
permission. LUCENT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS
SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS. IN NO EVENT SHALL LUCENT OR ANY OF ITS ENTITIES BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY
DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCEOF THIS SOFTWARE.
OpenEdge includes http package software developed by the World Wide Web Consortium.
Copyright 1994-2002 World Wide Web Consortium, (Massachusetts Institute of
Technology, European Research Consortium for Informatics and Mathematics, Keio
University). All rights reserved. This work is distributed under the W3C Software License
[http://www.w3.org/Consortium/Legal/2002/copyright-software-20021231] in the hope
that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty
of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
OpenEdge includes ICU software 1.8 and later - Copyright 1995-2003 International Business
Machines Corporation and others All rights reserved. Permission is hereby granted, free of
charge, to any person obtaining a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit
persons to whom the Software is furnished to do so, provided that the above copyright notice(s)
and this permission notice appear in all copies of the Software and that both the above copyright
notice(s) and this permission notice appear in supporting documentation.
OpenEdge includes Imaging Technology copyrighted by Snowbound Software 1993-2003.
www.snowbound.com.
OpenEdge includes Infragistics NetAdvantage for .NET v2009 Vol 2 Copyright 1996-2009Infragistics, Inc. All rights reserved.
-
8/9/2019 OpenEdge Management: Reporting
17/90
Preface
Preface11
OpenEdge includes JSTL software Copyright 1994-2006 Sun Microsystems, Inc. All Rights
Reserved. Software distributed on an AS IS basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the License for the specific language governing rights and
limitations under the License agreement that accompanies the product.
OpenEdge includes OpenSSL software developed by the OpenSSL Project for use in the
OpenSSL Toolkit (http://www.openssl.org/). Copyright 1998-2007 The OpenSSL
Project. All rights reserved. This product includes cryptographic software written by EricYoung ([email protected]). This product includes software written by Tim Hudson
([email protected]). Copyright 1995-1998 Eric Young ([email protected]) All rights
reserved. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to endorse
or promote products derived from this software without prior written permission. For written
permission, please contact [email protected]. Products derived from this software may
not be called "OpenSSL" nor may "OpenSSL" appear in their names without prior written
permission of the OpenSSL Project. Software distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the License for the specific
language governing rights and limitations under the License agreement that accompanies the
product.
OpenEdge includes Quartz Enterprise Job Scheduler software Copyright 2001-2003 James
House. All rights reserved. Software distributed on an AS IS basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the License for the specific
language governing rights and limitations under the License agreement that accompanies the
product. This product uses and includes within its distribution, software developed by the
Apache Software Foundation (http://www.apache.org/).
OpenEdge includes code licensed from RSA Security, Inc. Some portions licensed from IBM
are available at http://oss.software.ibm.com/icu4j/.
OpenEdge includes the RSA Data Security, Inc. MD5 Message-Digest Algorithm. Copyright
1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.
OpenEdge includes Sonic software, which includes software developed by Apache Software
Foundation (http://www.apache.org/). Copyright 1999-2000 The Apache Software
Foundation. All rights reserved. The names Ant, Axis, Xalan, FOP, The Jakarta
Project, Tomcat, Xerces and/or Apache Software Foundation must not be used to
endorse or promote products derived from the Product without prior written permission. Any
product derived from the Product may not be called Apache, nor may Apache appear in
their name, without prior written permission. For written permission, please contact
OpenEdge includes Sonic software, which includes software Copyright 1999 CERN -European Organization for Nuclear Research. Permission to use, copy, modify, distribute and
sell this software and its documentation for any purpose is hereby granted without fee, provided
that the above copyright notice appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation. CERN makes no representations about
the suitability of this software for any purpose. It is provided "as is" without expressed or
implied warranty.
OpenEdge includes Sonic software, which includes software developed by ExoLab Project
(http://www.exolab.org/). Copyright 2000 Intalio Inc. All rights reserved. The names
Castor and/or ExoLab must not be used to endorse or promote products derived from the
Products without prior written permission. For written permission, please contact
[email protected]. Exolab, Castor and Intalio are trademarks of Intalio Inc.
mailto:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected]:[email protected] -
8/9/2019 OpenEdge Management: Reporting
18/90
Preface
Preface12
OpenEdge includes Sonic software, which includes software developed by IBM. Copyright
1995-2003 International Business Machines Corporation and others. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
associated documentation files (the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or
sell copies of the Software, and to permit persons to whom the Software is furnished to do so,
provided that the above copyright notice(s) and this permission notice appear in all copies of the
Software and that both the above copyright notice(s) and this permission notice appear in
supporting documentation. Software distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the License for the specific
language governing rights and limitations under the License agreement that accompanies the
product. Except as contained in this notice, the name of a copyright holder shall not be used in
advertising or otherwise to promote the sale, use or other dealings in this Software without prior
written authorization of the copyright holder.
OpenEdge includes Sonic software, which includes the JMX Technology from Sun
Microsystems, Inc. Use and Distribution is subject to the Sun Community Source License
available at http://sun.com/software/communitysource.
OpenEdge includes Sonic software, which includes software developed by the ModelObjects
Group (http://www.modelobjects.com). Copyright 2000-2001 ModelObjects Group. All
rights reserved. The name ModelObjects must not be used to endorse or promote products
derived from this software without prior written permission. Products derived from this
software may not be called ModelObjects, nor may ModelObjects appear in their name,
without prior written permission. For written permission, please contact
OpenEdge includes Sonic software, which includes code licensed from Mort Bay Consulting
Pty. Ltd. The Jetty Package is Copyright 1998 Mort Bay Consulting Pty. Ltd. (Australia) and
others.
OpenEdge includes Sonic software, which includes files that are subject to the Netscape Public
License Version 1.1 (the License); you may not use this file except in compliance with the
License. You may obtain a copy of the License athttp://www.mozilla.org/NPL/. Software
distributed under the License is distributed on an AS IS basis, WITHOUT WARRANTY OF
ANY KIND, either express or implied. See the License for the specific language governing
rights and limitations under the License. The Original Code is Mozilla Communicator client
code, released March 31, 1998. The Initial Developer of the Original Code is Netscape
Communications Corporation. Portions created by Netscape are Copyright 1998-1999
Netscape Communications Corporation. All Rights Reserved.
OpenEdge includes Sonic software, which includes software developed by the UniversityCorporation for Advanced Internet Development http://www.ucaid.eduInternet2 Project.
Copyright 2002 University Corporation for Advanced Internet Development, Inc. All rights
reserved. Neither the name of OpenSAML nor the names of its contributors, nor Internet2, nor
the University Corporation for Advanced Internet Development, Inc., nor UCAID may be used
to endorse or promote products derived from this software and products derived from this
software may not be called OpenSAML, Internet2, UCAID, or the University Corporation for
Advanced Internet Development, nor may OpenSAML appear in their name without prior
written permission of the University Corporation for Advanced Internet Development. For
written permission, please [email protected].
OpenEdge includes the UnixWare platform of Perl Runtime authored by Kiem-Phong Vo andDavid Korn. Copyright 1991, 1996 by AT&T Labs. Permission to use, copy, modify, and
mailto:[email protected]:[email protected]:[email protected]:[email protected] -
8/9/2019 OpenEdge Management: Reporting
19/90
Preface
Preface13
distribute this software for any purpose without fee is hereby granted, provided that this entire
notice is included in all copies of any software which is or includes a copy or modification of
this software and in all copies of the supporting documentation for such software. THIS
SOFTWARE IS BEING PROVIDED AS IS, WITHOUT ANY EXPRESS OR IMPLIED
WARRANTY. IN PARTICULAR, NEITHER THE AUTHORS NOR AT&T LABS MAKE
ANY REPRESENTATION OR WARRANTY OF ANY KIND CONCERNING THE
MERCHANTABILITY OF THIS SOFTWARE OR ITS FITNESS FOR ANY PARTICULAR
PURPOSE.
OpenEdge includes Vermont Views Terminal Handling Package software developed by
Vermont Creative Software. Copyright 1988-1991 by Vermont Creative Software.
OpenEdge includes XML Tools, which includes versions 8.9 of the Saxon XSLT and XQuery
Processor from Saxonica Limited (http://www.saxonica.com/) which are available from
SourceForge (http://sourceforge.net/projects/saxon/). The Original Code of Saxon
comprises all those components which are not explicitly attributed to other parties. The Initial
Developer of the Original Code is Michael Kay. Until February 2001 Michael Kay was an
employee of International Computers Limited (now part of Fujitsu Limited), and original code
developed during that time was released under this license by permission from InternationalComputers Limited. From February 2001 until February 2004 Michael Kay was an employee
of Software AG, and code developed during that time was released under this license by
permission from Software AG, acting as a "Contributor". Subsequent code has been developed
by Saxonica Limited, of which Michael Kay is a Director, again acting as a "Contributor". A
small number of modules, or enhancements to modules, have been developed by other
individuals (either written especially for Saxon, or incorporated into Saxon having initially been
released as part of another open source product). Such contributions are acknowledged
individually in comments attached to the relevant code modules. All Rights Reserved. The
contents of the Saxon files are subject to the Mozilla Public License Version 1.0 (the "License");
you may not use these files except in compliance with the License. You may obtain a copy of
the License at http://www.mozilla.org/MPL/ and a copy of the license can also be found in theinstallation directory, in the c:/OpenEdge/licenses folder. Software distributed under the
License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the License for the specific language governing rights and limitations
under the License.
OpenEdge includes XML Tools, which includes Xs3P v1.1.3. The contents of this file are
subject to the DSTC Public License (DPL) Version 1.1 (the "License"); you may not use this
file except in compliance with the License. A copy of the license can be found in the installation
directory, in the c:/OpenEdge/licenses folder. Software distributed under the License is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
implied. See the License for the specific language governing rights and limitations under the
License. The Original Code is xs3p. The Initial Developer of the Original Code is DSTC.
Portions created by DSTC are Copyright 2001, 2002 DSTC Pty Ltd. All rights reserved.
OpenEdge includes YAJL software Copyright 2007, Lloyd Hilaiel. Redistribution and use in
source and binary forms, with or without modification, are permitted provided that the
following conditions are met: 1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form
must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution. 3. Neither the name
of Lloyd Hilaiel nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission. THIS SOFTWARE IS
PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED
-
8/9/2019 OpenEdge Management: Reporting
20/90
Preface
Preface14
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
8/9/2019 OpenEdge Management: Reporting
21/90
1
Understanding Reports
You can create a variety of reports based on data in the OpenEdge Management Trend
Database. Each report is based on a report template that is either provided with OpenEdge
Management or created by you.
This chapter introduces the basics of OpenEdge Management reporting, as described in the
following sections:
OpenEdge Management report terminology
OpenEdge Management report types
Report instances
-
8/9/2019 OpenEdge Management: Reporting
22/90
Understanding Reports
12
OpenEdge Management report terminology
It is important to understand OpenEdge Management report terminology so that you can be sure
you are creating reports based on and containing the kind of data you require.
Remember the following terms as you create OpenEdge Management reports:
Report History The history of how a report ran.
Report Instance The report entity that you schedule to run in order to produce the
report result. The report instanceidentifies specific details that you want reported on; a
report instance can specify, for example, a particular resource on which to report or a
period of time that the report covers. You specify these report instance details and also
schedule when you want the report to run. A report instance is based on a report template.
Report Log A file where error messages and debug tracing information for a report is
written.
Report Output The formatted data returned when a report instance is run.
Report Template The report templatedefines the characteristics of the report. When
you want to create a report instance, you begin by selecting the template on which the
report is to be based. If you want, you can make changes to some of the properties inherited
from the template for a particular report instance so that you get the reporting data you
require; for example, you can specify when you want the report to run and what period of
time the report should cover. There are template properties that you cannot change in the
report instance; for example, you cannot change the type and number of resources in the
report or the location in which the report results are written when the report is run.
In summary, to create reports in OpenEdge Management, you use a report templateto create a
report instancethat runs to produce the report output.
-
8/9/2019 OpenEdge Management: Reporting
23/90
OpenEdge Management report types
13
OpenEdge Management report types
To open the OpenEdge Management Reportshome page, click Reportsin the OpenEdge
Management console menu bar. The OpenEdge Management ReportsDetails page opens, as
shown in Figure 11.
Figure 11: OpenEdge Management Reports Details page
When you click Reportsin the OpenEdge Management console menu bar, the list frameupdates, showing the three kinds of reports:
Defined Reports based on information in the OpenEdge Management Trend Database.
You create instances of these reports using report templates. See the Historical report
descriptions section on page 23for more information about defined reports.
Realtime Reports that show the state of your resources and system at the time the
reports are run.
Diagnostic A report of the OpenEdge Management AdminServer log file, the Work
Scheduler, and the Task Scheduler.
-
8/9/2019 OpenEdge Management: Reporting
24/90
Understanding Reports
14
OpenEdge Management supplies the report templates shown in Figure 12and adds to this list
any report templates you create.
Figure 12: Reports list frame
-
8/9/2019 OpenEdge Management: Reporting
25/90
-
8/9/2019 OpenEdge Management: Reporting
26/90
Understanding Reports
16
The middle section includes:
Report on one of the following: 15-minute intervals, hourly information, daily
information,or weekly information Indicates how the report output will be
structured and is based upon the Report formatyou choose.
Report Period Indicates whether the report instance will cover a previous
number of hours, days, weeks, or months or a specific period of days, weeks, or
months. The format you select for the report determines the maximum number of
periods that the report can include, as shown in the following table:
Time period within the day to include in the report Indicates whether the
report instance should cover a full day (24 hours) or a partial day.
Display units The units in which the data is presented. Options are per second,
per minute, per hour, per transaction, per record, or as raw data.
The bottom section includes:
Environment Any environment variables. Available environment variables
depend on the type of report you are creating and your environment. For a list of
environment variables available for your report, run the report with the Generate
debug log fileoption on. The debug log file lists all environment variables and, if
applicable, their values. For more information about viewing environment variables
in the debug log file, see the entry for Generate debug log file.
If the reports output will appear in HTML, you may want to set the
GRAPH1COLUMNS or the fathomResourcesPerGraph variables. See the
Graphical output environment variables section on page 212for more
information about these two variables.
Account information The user name, group, and password (if you want to run
the report as a user other than the AdminServer).
Working directory The OpenEdge Management working directory (if you do
not want to use the default working directory).
4GL client parameters Any additional ABL client startup parameters.
This report format . . . Shows a maximum of . . .
Hourly 24 hours
Daily 31 days (7 days if you also select theReport onoption)
Weekly 52 weeks
Monthly 48 months
-
8/9/2019 OpenEdge Management: Reporting
27/90
Report instances
17
Generate debug log file Indicates whether OpenEdge Management will create a
trace file when it executes the report instance. Select the check box if you want to
create debug log files; otherwise, leave the check box cleared. Creating a debug log
file allows you to examine the reports environment variables. When you are viewing
the debug log file, you see that lines beginning with envprovide the names and
values of applicable environment variables, as shown in the following example:
For a detailed explanation about environment variables, see the chapter on jobs in
OpenEdge Management: Resource Monitoring.
Creating a report instance
The specific steps you follow to create a report instance vary depending on the reports menu
group.
To create a report instance:
1. From the management console menu bar, click Reports.
2. Click Create Report.
3. From the Create Reportpage, click the type of report you want to create. The Report
Edit page for that report type appears.
http://../omrmg/omrmg.pdfhttp://../omrmg/omrmg.pdf -
8/9/2019 OpenEdge Management: Reporting
28/90
Understanding Reports
18
4. Complete the top section of the Report Editpage, as described in the Report Edit page
section on page 15. Note that certain reports contain unique fields. The following
information will help you complete the unique fields:
AppServer Application Profile and WebSpeed Application Profile reports include:
(1 of 2)
Field Explanation
Resources The resource whose activity you want in thereport.
Click the right arrow to move a highlightedresource from the Availablecolumn to theSelectedcolumn. Click the left arrow to movea highlighted resource from the Selectedfieldto the Availablefield.
Click the up and down arrows to change the
order in which the resources will appear in thereport output.
Procedure filter To run a procedure filter, choose Literal,Begins With, or Matchesand enter theapplicable text in the field. Use the procedurefilter to return data about when the broker rana procedure. When the report instance runs,OpenEdge Management will search theOE_ActBrk table in the OpenEdgeManagement Trend Database for the textentered.
Literal To use the Literal filter, type the exact text youwant to find; for example, inventory.p.
Begins with To use the Begins withfilter, type thebeginning of the procedure name; for example,in, inv, or inven.
-
8/9/2019 OpenEdge Management: Reporting
29/90
Report instances
19
AppServer Performance and WebSpeed Performance reports include:
Matches To use the Matchesfilter, type the characterexpression that you want to match (such as.nventory orinven*).
Note: The expression can contain wildcardcharacters. A period (.) indicates that anysingle character is acceptable in that positionand an asterisk (*) indicates that any group ofcharacters is acceptable. To use a literal periodor asterisk in the expression, precede theperiod or asterisk by a tilde (~).
You can also use the OR symbol or a verticalline ( | ) in the Matchesfield to indicate asearch for one procedure or another procedure.For example, the expressioninventory.p | onorder.p indicates a search foreither of these two procedures. The searchconcludes when at least one of them is found.
Note: You can identify multiple files usingthis approach. For example,inventory.p | onorder.p | bckorder.p.
Sort order The criteria by which the returned proceduredata is sorted and whether the data is sorted indescending or ascending order.
(2 of 2)
Field Explanation
Field Explanation
Resources The resource whose activity you want in the report.
Click the right arrow to move a highlighted resourcefrom the Availablecolumn to the Selectedcolumn.Click the left arrow to move a highlighted resourcefrom the Selectedcolumn to the Availablecolumn.
Click the up and down arrows to change the order inwhich the resources will appear in the report output.
Data to display The desired broker activity on which to report: Client,
Broker, and/or Server.
Click the left arrow to move highlighted text from theAvailableto theSelectedcolumn. Click the rightarrow to move highlighted text from the Selectedtothe Availablecolumn.
Click the up and down arrows to change the order inwhich the activity data will appear in the report output.
-
8/9/2019 OpenEdge Management: Reporting
30/90
Understanding Reports
110
Resource Alert Detail, Resource Status Detail, CPU Summary, Network Activity,
System Disk Device Activity, System Memory Summary, and all Database menu
group reports include:
5. Complete the middle section of the Report Edit page, described in the Report Edit page
section on page 15. Note that the time interval indicated by the Report format option
changes based on the report format chosen, as shown in the following table:
6. Complete the bottom section of the Report Editpage, as described in the Report Edit
page section on page 15.
7. Click Save. The name of your report instance appears, along with a summary of the report
definition, in the list frame under Defined Reports.
After you create your report instance, you can:
Click Editto make changes in the report specifics. When you finish the edits, click Save.
Click Copyto make a copy of the report specifics, perhaps to use for another report. Type
a new name for the report instance, and click Save.
Click Deleteto remove the report instance. Click OKto delete the report instance.
You can either run the report now or schedule it to run at a later time. See the Running reportssection on page 310for more details.
Field Explanation
Resources The resource whose activity you want in the report
This reportformat
With Report on optionselected Displays the data
Hourly 15-minute intervals Hourly, in four 15- minuteintervals
Daily Hourly Daily in hourly increments
Weekly Daily Weekly in daily increments
Monthly Weekly Monthly in weeklyincrements
-
8/9/2019 OpenEdge Management: Reporting
31/90
2
Historical Reports
Historical reports are created from information in the OpenEdge Management Trend Database.
This chapter describes historical reports and how to create them, as outlined in the following
sections:
Overview of historical reports
Historical report descriptions
Customizing graphical output
-
8/9/2019 OpenEdge Management: Reporting
32/90
Historical Reports
22
Overview of historical reports
Historical reports are created using data from the OpenEdge Management Trend Database.
To see available historical report templates, click Create Reportfrom the OpenEdge
Management ReportsDetails page. The Create Reportpage appears.
Working with report templates
You can modify or delete any of the existing OpenEdge Management templates, or you can
create your own templates. All report templates, regardless of whether they are provided with
OpenEdge Management or created, appear in this list of report templates. If you add, delete, or
rename a report template, that change is reflected on the Create Reportpage.
When you create a report template, you provide the templates name, menu group (choose from
the existing groups or create your own), and a brief report description that appears on the Create
Reportpage. See the Creating a custom report template section on page 42for detailedinstructions on creating a report template.
Each of the report templates provided with OpenEdge Management defines reports based on
one resource (with the exception of the AppServer and WebSpeed reports, which can report on
multiple resources). When you modify the OpenEdge Management-provided report templates
or create your own templates, you can choose to generate a report based on multiple resources
or resources of different types (database and system CPU in one report, for example).
You can modify or remove any of the individual templates you see listed on the Create Report
page. This flexibility allows you to set up an OpenEdge Management Reportspage that
includes only those reports relevant to your business needs.
To delete a report template:
1. Expand the Report Templatescategory in the report list frame.
2. Click the report template name. The Report Template Summary page appears.
3. Click Delete. The template no longer appears on the Create Report page or in the list
frames list of templates.
-
8/9/2019 OpenEdge Management: Reporting
33/90
Historical report descriptions
23
Historical report descriptions
When you click the Create Reportlink on the OpenEdge Management ReportsDetails page,
the Create Reportpage appears with a list of report templates divided into the following menu
groups:
AppServer reports
Database reports
General reports
System reports
WebSpeed reports
Any report templates or menu groups you create also appear on the Create Reportpage.
Table 21lists and describes each OpenEdge Management-provided report.
Table 21: OpenEdge Management-provided reports (1 of 9)
Report name Template name Description
AppServerApplication Profile
appServerProfile Provides information on procedures runby the broker, including how manytimes the procedure ran, the average andmaximum durations of each request, thenumber of successful requests, thenumber of errors, and the number oftimes each request quit and was stopped.
The AppServer Application Profilereport retrieves its data from theOE_ActASProc, OE_ActBrk,OE_ActSrv, and OE_APPService tablesin the OpenEdge Management TrendDatabase.
-
8/9/2019 OpenEdge Management: Reporting
34/90
Historical Reports
24
AppServerPerformance
appServerPerformance Provides performance information onbroker, client, and server activity.Broker activity information returned
includes number of complete requests,number of queued requests, percentageof queued requests, average andmaximum request duration, average andmaximum CPU use, and average andmaximum memory use. Client activityinformation returned includes averageand maximum number of active clients,and average and maximum number ofclient requests. Server activityinformation returned includes averageand maximum CPU pool use, averageand maximum memory pool use,
average and maximum number of busyservers, average and maximum numberof running servers, and average andmaximum number of locked servers.The AppServer Performance reportretrieves its data from the OE_ActBrk,OE_ActSrv, OE_APPService, andSys_Process tables in the OpenEdgeManagement Trend Database.
DatabaseAfter-imaging
dbAfterImage Provides performance details forafter-imaging, including read and writeactivity, full and partial buffer activity,
and AIW write status. The DatabaseAfter-imaging report retrieves its datafrom the Db_ActLog in the OpenEdgeManagement Trend Database.
Database Area Status dbAreaStatus Provides trend status for each areawithin a database. Included in this reportis information about total blocks, thehigh water mark, free blocks, availablespace (in blocks), and available space asa percentage of area. The Database AreaStatus report retrieves its data from theDB_AreaStatus table in the OpenEdge
Management Trend Database.
Table 21: OpenEdge Management-provided reports (2 of 9)
Report name Template name Description
-
8/9/2019 OpenEdge Management: Reporting
35/90
Historical report descriptions
25
DatabaseBefore-imaging
dbBeforeImage Provides performance details forbefore-imaging, including read andwrite activity; wait activity; full, partial,
and empty buffer activity; and BIWstatistics. This report also helps youdetermine the health of your BIsubsystem by indicating increases in theamount of BI writes (which can indicatethe growth of an application orquestionable application design). TheDatabase Before-imaging reportretrieves its data from the Db_ActLogand Db_ActIOType tables in theOpenEdge Management TrendDatabase.
Database Buffer I/O dbMemory Provides details about memory bufferusages for all buffers (database, BI, andAI). The information provided in theDatabase Buffer I/O report helps youdetermine the proper use of OpenEdgememory on your machine. This reportretrieves its data from the Db_ActBufand Db_ActLog tables in the OpenEdgeManagement Trend Database.
DatabaseCheckpointing
dbCheckpoint Provides performance details forcheckpoints. The DatabaseCheckpointing report retrieves its data
from the Db_Checkpoint table in theOpenEdge Management TrendDatabase.
Database Details dbDetail Provides information on all databasetables and includes fields from almostevery table, depending on relevance.Use this report to gathercross-functional information and tounderstand the relationship amongdifferent aspects of an OpenEdgedatabase. The Database Details reportretrieves information from the following
OpenEdge Management TrendDatabase tables: Db_ActBuf,Db_ActRec, Db_ActLog,Db_ActAPW, Db_ActIdx,Db_ActLock, Db_ActSum, andDb_ActIOType.
Table 21: OpenEdge Management-provided reports (3 of 9)
Report name Template name Description
-
8/9/2019 OpenEdge Management: Reporting
36/90
-
8/9/2019 OpenEdge Management: Reporting
37/90
Historical report descriptions
27
Database Locking dbLocks Provides performance details for recordlocking, based on the categories ofrequests, finds, locks, and waits. Each of
the four categories contains informationabout exclusive, record, share, andupgrade locks. The Database Lockingreport retrieves its data from theDb_ActLock table in the OpenEdgeManagement Trend Database.
Database RecordInformation
dbRecord Provides performance details for recordlocking, including information onincreased record update activity,increased fragment activity, andincreased record deletion. This reportgroups information into three
categories: record, fragment, and bytes.Each category contains read, update,create, and delete fields. The DatabaseRecord Information report retrieves itsdata from the Db_ActRec table in theOpenEdge Management TrendDatabase.
Database ServerActivity
dbServer Provides detailed information aboutclient activity on servers, including I/Ofor the server in bytes, records, andblocks. This report helps you assess theperformance of your servers by showing
how balanced or unbalanced the serveractivity is. The Database Server Activityreport retrieves its information from theDb_ActServer table in the OpenEdgeManagement Trend Database.
Database Summary dbSummary Provides a summary of performanceinformation for several subsections of adatabase, including logical and physicalI/O, buffer activity, BI file activity, AIfile activity, page writer activity, indexI/O, table I/O, and record activity. TheDatabase Summary report retrieves its
data from the following OpenEdgeManagement Trend Database tables:Db_ActBuf, Db_ActSum, Db_ActRec,Db_ActLog, Db_ActAPW, Db_ActIdx,and Db_ActIOType.
Table 21: OpenEdge Management-provided reports (5 of 9)
Report name Template name Description
-
8/9/2019 OpenEdge Management: Reporting
38/90
Historical Reports
28
Database TableAnalysis
dbTabAnalysis Provides analysis of table informationgathered from the execution of thedatabase analysis job. This report
includes the maximum, minimum, andaverage for the record counts, thenumber of bytes in the table, the numberof record fragments in the table, and thescatter factor. The Database TableAnalysis report retrieves its data fromthe Db_TabAnalysis table.
Note: In order for the Database TableAnalysis report to display data, theDatabase Analysis job must first be runagainst the desired database. For moreinformation on the Database Analysis
job, see OpenEdge Management:
Database Management.
Database TableUsage
dbTableStat Provides performance details for eachtable in the schema, includinginformation related to the number oftable updates, creates, and deletes. Thisreport identifies which tables are themost active, allowing you to betterstructure your database areas by movingtables. The Database Table Utilizationreport retrieves its data from theDb_TableStat table in the OpenEdgeManagement Trend Database.
Note: OpenEdge Management reportson a default of 50 tables. Use the startupparameter -tablerangesizeto increasethis number, if necessary. Thisparameter must be set on the productiondatabase when it is started.
Resource Alert Detail alertIndividual Provides summary and detailinformation for alerts specific to aresource, including counts of thedifferent types of alerts that haveoccurred, details of all severe alerts, anddata entered when the alert was cleared.
The Resource Alert Detail reportretrieves its data from theCf_Alert_Detail table in the OpenEdgeManagement Trend Database.
Resource AlertSummary
alertGeneral Provides summary information about asites alerts, including informationsorted by the resource name. This reportshows which of a sites resources causethe most problems. The Resource AlertSummary report retrieves its data fromthe Cf_Alert_Detail table in theOpenEdge Management Trend
Database.
Table 21: OpenEdge Management-provided reports (6 of 9)
Report name Template name Description
http://../omdbg/omdbg.pdfhttp://../omdbg/omdbg.pdfhttp://../omdbg/omdbg.pdfhttp://../omdbg/omdbg.pdf -
8/9/2019 OpenEdge Management: Reporting
39/90
-
8/9/2019 OpenEdge Management: Reporting
40/90
Historical Reports
210
System Disk DeviceActivity
systemDisk Provides performance information fordefined disk devices, including therelationship between disk reads and
writes and the average queue length ofdisk activity. Use this report to identifydisk bottlenecks and a decline in diskperformance. The System Disk DeviceActivity report retrieves its data fromthe Sys_Dev table in the OpenEdgeManagement Trend Database.
System FilesystemUsage
systemFileSystem Provides usage information for definedlocal or remote file systems, includinghow fast disk space grows from allsoftware (including OpenEdge). Usethis report to debug actual or potential
file space problems where OpenEdgetemporary files reside. The SystemFilesystem Usage report retrieves itsdata from the Sys_Filesys table in theOpenEdge Management TrendDatabase.
System MemorySummary
systemMemory Provides a summary of the definedmemory resources performance. Bydetailing how much memory is used andhow much is available, this report helpsidentify growth in memoryconsumption. Combining the
information in this report with that ofthe Database Buffer I/O report providesviews of memory from the standpoint ofboth the system and OpenEdge. TheSystem Memory Summary reportretrieves this information from theSys_Mem table in the OpenEdgeManagement Trend Database.
WebSpeedApplication Profile
webSpeedProfile Provides information on procedures runby the broker, including how manytimes the procedure ran, the average andmaximum durations of each request, the
number of successful requests, thenumber of errors, and the number oftimes each request stopped. TheWebSpeed Application Profile reportretrieves its data from theOE_ActWSProc, OE_ActBrk,OE_ActSrv, and OE_APPService tablesin the OpenEdge Management TrendDatabase.
Table 21: OpenEdge Management-provided reports (8 of 9)
Report name Template name Description
-
8/9/2019 OpenEdge Management: Reporting
41/90
Historical report descriptions
211
For more information about OpenEdge Management Trend Database tables, see OpenEdge
Management: Trend Database Guide and Reference.
WebSpeedPerformance
webSpeedPerformance Provides performance information onbroker, client, and agent activity. Brokeractivity information returned includes
number of complete requests, number ofqueued requests, percentage of queuedrequests, average and maximum requestduration, average and maximum CPUuse, and average and maximum memoryuse. Client activity information returnedincludes average and maximum numberof active clients and average andmaximum number of client requests.Server activity information returnedincludes average and maximum CPUpool use, average and maximummemory pool use, average and
maximum number of busy servers,average and maximum number ofrunning servers, and average andmaximum number of locked servers.The WebSpeed Performance reportretrieves its data from the OE_ActBrk,OE_ActSrv, OE_APPService, andSys_Process tables in the OpenEdgeManagement Trend Database.
Table 21: OpenEdge Management-provided reports (9 of 9)
Report name Template name Description
http://../omtrd/omtrd.pdfhttp://../omtrd/omtrd.pdfhttp://../omtrd/omtrd.pdfhttp://../omtrd/omtrd.pdf -
8/9/2019 OpenEdge Management: Reporting
42/90
-
8/9/2019 OpenEdge Management: Reporting
43/90
Customizing graphical output
213
The graph report output example in Figure 21uses the values associated with the CPU
Summary reports default fields.
Figure 21: CPU Summary output
In contrast, the following code entered in the Environmentfield on the Create Reportpage
shows how you can customize the graph output of the report by defining a field:
When the CPU Summary report is run with this code, the data associated with the specified field
appears. Figure 22shows this customized output.
Figure 22: Customized graph output for CPU Summary
GRAPH1COLUMNS=CPU_Idle
-
8/9/2019 OpenEdge Management: Reporting
44/90
-
8/9/2019 OpenEdge Management: Reporting
45/90
Customizing graphical output
215
Figure 24, Figure 25, and Figure 26show this customized output.
Figure 24: Request duration graph
Figure 25: Return code success graph
Figure 26: Run count graph
-
8/9/2019 OpenEdge Management: Reporting
46/90
Historical Reports
216
Report output field and column headings
This section identifies the fields or column headings associated with each historical report
template.
Note: Fields and column headings in this section that are identified with an asterisk (*) are
also the OpenEdge Management-supplied defaults associated with each report type.
AppServer Application Profile
Table 22identifies the AppServer Application Profile column headings.
AppServer Performance
Table 23, Table 24, and Table 25identify the column headings for an AppServer
Performance graphical report.
Table 22: AppServer Application Profile column headings
Run Count* Request Duration (avg) Request Duration (max)
Return Code Success Return Code Error Return Code Quit
Return Code Stop
Table 23: AppServer Client Activity column headings
Average Active Clients* Maximum Active Clients Client Requests
Average Client Requests Maximum Client Requests Sample Count
Table 24: AppServer Broker Activity column headings
Requests Completed Requests Queued Requests Queued %
*Average Request Duration(ms)
Average CPU Usage % Maximum CPU Usage %
Average Memory Usage(KB)
Maximum Memory Usage(KB)
Sample Count
Table 25: AppServer Activity column headings
Average Pool CPU Usage % Maximum Pool CPUUsage %
Average Pool MemoryUsage (KB)
Maximum Pool MemoryUsage (KB)
*Average Busy ServerCount
Maximum Busy ServerCount
Average Busy Server Time(ms)
Average Locked ServerCount
Maximum Locked ServerCount
Average Locked ServerTime (ms)
Sample Count
-
8/9/2019 OpenEdge Management: Reporting
47/90
Customizing graphical output
217
Database After-imaging
Table 26identifies the column headings for a Database After-Imaging graphical report.
Database Area Status
Table 27identifies the column headings for a Database Area Status graphical report.
Database Before-imaging
Table 28identifies the fields for a Database Before-Imaging graphical report.
Database Checkpointing
Table 29identifies the column headings for a Database Checkpointing graphical report.
Table 26: Database After-Imaging column headings
AI Busy Buffer Waits AI Bytes Written AI No Buffers Available
AI Partial Writes AI Records Written Total AI Writes*
AIW AI Writes*
Table 27: Database Area Status column headings
Sample Count Total Blocks Hi Water Mark*
Free Blocks RM Blocks Blocks Available*
Pct. Blocks Available
Table 28: Database Before-Imaging fields
BI Busy Buffer Waits BI Bytes Read BI Bytes Written
BI Empty Buffer Waits BI Partial Writes BI Records Read
BI Records Written Total BI Reads Total BI Writes
BIW BI Writes BI Reads BI Writes
Table 29: Database Checkpointing column headings
Sample Count Avg. Checkpoint Length(sec.)*
Avg. Buffer Scanned
Avg. Buffers on Ckpt Queue Avg Buffers on APW Queue Avg Buffers Flushed atCkpt*
-
8/9/2019 OpenEdge Management: Reporting
48/90
Historical Reports
218
Database Details
Table 210identifies the fields for a Database Details graphical report.
Table 210: Database Details fields
APW Queues APW Queue Writes Buffers Checkpointed
Buffers Scanned Checkpoint Queue Writes Checkpoints
APW DB Writes Marked at Checkpoint Scan Cycles
Scan Writes Total DB Writes Writes Deferred
Flushed at Checkpoint Logical Reads Logical Writes
O/S Reads O/S Writes Create Index Entry
Delete Index Entry Find Index Entry Free Block
Remove Locked Entry Split Block AI Reads
DB Data Block Reads Data Block Writes DB Index Block Reads
Index Block Writes AI Busy Buffer Waits AI Bytes Written
AI No Buffers Available AI Partial Writes AI Records Written
Total AI Writes AIW AI Writes BI Busy Buffer Waits
BI Bytes Read BI Bytes Written BI Empty Buffer Waits
BI Partial Writes BI Records Read BI Records Written
Total BI Reads Total BI Writes BIW BI Writes
Bytes Created Bytes Deleted Bytes Read
Bytes Updated Fragments Created Fragments Deleted
Fragments Read Fragments Updated Create Record
Delete Record Record Locks Read Record
Update Record Record Waits AI Writes
Allocated RM Space BI Reads BI Writes
Bytes Allocated Commits DB Acceses
Database Extends DB Reads DB Writes
RM Blocks Examined Allocated From Free Allocated From RM
Remove From RM Return Free Block Take Free Block
Undos
-
8/9/2019 OpenEdge Management: Reporting
49/90
Customizing graphical output
219
Database Disk Information
Table 211identifies the fields for a Database Disk Information graphical report.
Database Index Analysis
Table 212identifies the column headings for a Database Index Analysis graphical report.
Database Index Usage
Table 213identifies the column headings for a Database Index Usage graphical report.
Database Locking
Table 214identifies the fields for a Database Locking graphical report.
Table 211: Database Disk Information fields
Sample Count File Reads File Writes
Buffer Writes Unbuffered Writes Buffered Reads
Unbuffered Reads
Table 212: Database Index Analysis column headings
Sample Count Max Block Count Avg Block Count
Max Byte Count Avg Byte Count Max Util Percent
Avg Util Percent* Max Level Count Avg Level Count
Table 213: Database Index Utilization column headings
Index Reads* Index Splits Index Creates
Index Deletes
Table 214: Database Locking fields
Requests Cancelled Downgrade Excl Release
Exclusive Locks Exclusive Requests Exclusive Waits
Rec Get Grants Rec Get Requests Rec Get Waits
Shr Release Share Locks Share Requests
Share Waits Upgrade Locks Upgrade Requests
Upgrade Waits
-
8/9/2019 OpenEdge Management: Reporting
50/90
-
8/9/2019 OpenEdge Management: Reporting
51/90
Customizing graphical output
221
Database Summary
Table 218identifies the fields for a Database Summary graphical report.
Database Table Analysis
Table 219identifies the column headings for a Database Table Analysis graphical report.
Database Table Usage
Table 220identifies the column headings for a Database Table Usage graphical report.
CPU Summary
Table 221identifies the fields for a CPU Summary graphical report.
Table 218: Database Summary fields
Buffers Checkpointed Flushed at Checkpoint Logical Reads
Logical Writes O/S Reads O/S Writes
Create Index Entry Delete Index Entry Find Index Entry
Free Block Remove Locked Entry Split Block
DB Data Block Reads DB Index Block Reads Index Block Writes
Total BI Writes BIW BI Writes Read Record
Commits DB Acceses Database Extends
DB Reads DB Writes
Table 219: Database Table Analysis column headings
Sample Count Max Record Count Avg Record Count*
Max # of Bytes Avg # of Bytes Max # of Fragments
Avg # of Fragments Max Scatter Factor Avg Scatter Factor
Table 220: Database Table Usage column headings
Record Reads* Record Updates* Record Creates*
Record Deletes*
Table 221: CPU Summary fields
User Percent* System Percent* Wait Percent*
Idle Percent
-
8/9/2019 OpenEdge Management: Reporting
52/90
Historical Reports
222
File Summary
Table 222identifies the column headings for a File Summary graphical report. (Note that you
must have at least one file resource for OpenEdge Management to generate the report.)
Network Activity
Table 223identifies the column headings for a Network Activity graphical report.
System Disk Device Activity
Table 224identifies the column headings for a System Disk Device Activity graphical report.
System Filesystem Usage
Table 225identifies the column headings for a System Filesystem Usage graphical report.
System Memory Summary
Table 226identifies the column headings for a System Memory Summary graphical report.
Table 222: File Summary column headings
Sample Count Average File Size (k)* Minimum File Size (k)
Maximum File Size (k)
Table 223: Network Activity column headings
Passed Sample Count Average Response Time(ms)
Failed Sample Count
Table 224: System Disk Device Activity column headings
Sample Count Pct. Busy* Avg. Queue Length
Avg. Wait Time (ms) Avg. Serve Time (ms) Minimum Busy Pct.
Maximum Busy Pct.
Table 225: System Filesystem Usage column headings
Sample Count Maximum Capacity (kb) Pct. Used*
Average Available (kb) Maximum Available (kb) Minimum Available (kb)
Table 226: System Memory Summary column headings
Sample Count Average Physical MemoryUsed %
Average Physical MemoryUsed (MB)
Maximum Physical MemoryUsed (MB)
Average Virtual MemoryUsed %
Average Virtual MemoryUsed (MB)
Maximum Virtual Memory
Used (MB)
Pages In Pages Out
-
8/9/2019 OpenEdge Management: Reporting
53/90
Customizing graphical output
223
WebSpeed Application Profile
Table 227identifies the column headings for a WebSpeed Application Profile graphic