[HPADM] RE: -SUMMARY-Getting Processes from Measureware
- From: "Naylor, Jim" <Jnaylor@xxxxxxxxxxxx>
- Date: Tue, 14 Feb 2006 10:27:15 -0600
Thanks to Daniel Copeland for his response. This gave me what I needed.
extract -xp -p -b date/time -e date/time -r report_file -f output_file
Man extract for more details but this will export processes from begin
to end time w/ the format defined in the report file (defaults in
/var/opt/perf) and send to output to the output file.
Attached is a sample report file for looking at processes -- giving
time, PID, name, CPU util, IO rt, and IO wait time for a process. Look
at reptall for total list of metric available.
I use this command daily, so let me know if you run into any issues.
Thanks,
Jim Naylor
Unix/Storage Systems Administrator
Schnuck Markets, Inc.
* Direct (314) 994-4784
))( Cell (314) 691-0186
Fax (314) 994-4684
* E-Mail jnaylor@xxxxxxxxxxxx
-----Original Message-----
From: hpux-admin-owner@xxxxxxxxxxxxx
[mailto:hpux-admin-owner@xxxxxxxxxxxxx]On Behalf Of Naylor, Jim
Sent: Monday, February 13, 2006 1:00 PM
To: Hpux-Admin@Dutchworks. Nl (E-mail)
Subject: [HPADM] Getting Processes from Measureware
Hello All,
I have been searching through documentation trying to find if there is a way to extract the actual process name and process ID from measureware as you would see if you were running glance but have not had much success. I am able to get all the CPU, I/O, Network, etc. but I would like to show which processes are using large amounts of resources. Any suggestions would be greatly appreciated.
Thanks,
Jim Naylor
Unix/Storage Systems Administrator
Schnuck Markets, Inc.
* Direct (314) 994-4784
))( Cell (314) 691-0186
Fax (314) 994-4684
* E-Mail jnaylor@xxxxxxxxxxxx
______________________________________________________________________
The information transmitted (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is intended only for the person(s) or entity/entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer.
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@xxxxxxxxxxxxx
Name: hpux-admin@xxxxxxxxxxxxx Owner: owner-hpux-admin@xxxxxxxxxxxxx
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
______________________________________________________________________
The information transmitted (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is intended only for the person(s) or entity/entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer.******************************************************************************
**
** This is the "reptall" report file. It is used as a sample template
** for constructing report definition files which are used by the
** HP MeasureWare Agent program "extract".
**
** All lines which begin with an asterisk "*" in the first column are
** considered comments.
**
** The first section selects overall report format parameters.
**
** REPORT sets the report title, keywords which begin with an
** exclamation point "!" are replaced by the actual values
** when the report is generated.
**
** FORMAT selects ASCII (normal "printable" type reports)
** DATAFILE (used for moving data to spread*** programs)
** WK1 or
** SPREAD*** (used by spread*** programs)
** or BINARY (non printable, must be read by a program)
**
** HEADINGS is either ON (Includes the report title and column headings)
** or OFF (Does not include the report title & headings)
**
** SEPARATOR is optional, but can be used to select a column separator character
** other then the default of blank.
**
** SUMMARY defines the number of minutes of data to be summarized for each
** summary record. (Summary may range from 5-1440 minutes, the
** default is 60 minutes, or one hour).
**
** MISSING defines what value is to be used when exporting a metric which
** is missing. A missing metric may arise when that metric was not
** collected by a particular version of the data collector. When
** exporting data with LAYOUT MULTIPLE, (see below), the data for
** an instance which was not logged will normally be missing.
** The default value for missing data is zero.
**
******************************************************************************
REPORT "MWA Export !DATE !TIME Logfile: !LOGFILE !COLLECTOR !SYSTEM_ID"
FORMAT ASCII
HEADINGS ON
SEPARATOR="|"
SUMMARY=60
MISSING=0
*********************************************************************
**
** The rest of the file consists of specifics about the metrics to be
** exported for a single data type. Each exportable class may have one
** set of definitions in which the following lines lines appear.
**
** DATA TYPE specifies the type (class) of data. (required)
**
** OUTPUT specifies the name of the output file where the exported data is
** to be written. OUTPUT may be specified for each class named.
** (optional)
**
** LAYOUT selects SINGLE (one instance per record, i.e. a disk per record)
** MULTIPLE (multiple instances presented in a single record,
** for example, all disks exported in the same
** record)
** (optional)
**
** Individual metric names which belong to the class. Metrics will be exported
** in the order listed whenever possible. In order to be exported, metrics
** must not be commented out (that is, they must not contain an asterisk before
** the metric name).
**
** This sample report was generated with a section for each data type which
** is available in the currently open log file. Following the DATA TYPE
** line, each metric which is available for export for this data type is
** listed, but commented out. To select metrics for your report, delete
** the asterisk (*) in the first column.
**
*********************************************************************
*********************************************************************
*********************************************************************
DATA TYPE PROCESS
**............................... Process Record Identification Metrics
DATE
TIME
INTERVAL
**............................... Process Summary Metrics
PROC_PROC_ID
PROC_PROC_NAME
**............................... Process CPU Metrics
PROC_CPU_TOTAL_UTIL
**............................... Process Disk Metrics
PROC_DISK_PHYS_IO_RATE
PROC_OTHER_IO_WAIT_PCT
- Follow-Ups:
- [HPADM] Script to check the "cksum" of a file
- From: Neil Paniraj
- [HPADM] Script to check the "cksum" of a file
- Prev by Date: [HPADM] Restarting MoM [DATA Protector]
- Next by Date: [HPADM] RE: SOLUTION: Mailx Problem
- Previous by thread: [HPADM] RE: QUESTION: Mailx Problem
- Next by thread: [HPADM] Script to check the "cksum" of a file
- Index(es):