Sponsored Content
Full Discussion: Monitoring Unix systems
Top Forums UNIX for Dummies Questions & Answers Monitoring Unix systems Post 302099606 by gen4ik on Wednesday 13th of December 2006 05:55:41 AM
Old 12-13-2006
Monitoring Unix systems

I am looking for a commercial tool that will give me -UNIX Monitoring performance solution+ reports on CCV format. (as perfmon on windows machines).



The tool must have following counters per PROCESS:

Page Faults/sec
Virtual Bytes
% Processor Time
Handles count
Threads count
Pages/sec
Working Set
Average Disk queue length

Thanks.
 

5 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

eBay Unix systems

I should add a disclaimer: I am not affiliated with the sellers in any way, nor do I have any more knowledge than any other person reading the description about the item. This is simply for your reference. I see a good number of people wanting a SPARC system to play with, and even more that... (1 Reply)
Discussion started by: LivinFree
1 Replies

2. UNIX for Dummies Questions & Answers

distributers of unix systems

Well i've been looking for some unix systems to download but with all the technical stuff they talk about on the sites i think that it would be betterif i just bought oneat a store so it comeswith directions and stuff, but is there any unix system that will coincidentally run with MS-dos mode? and... (1 Reply)
Discussion started by: shag134
1 Replies

3. SCO

Sharing unix drives from two unix systems

I have two SCO openserver systems, 1 in the US and 1 in the UK. I am setting up a vpn to connect the two local networks that also have windows pc's on them. Is there a way that either unix system can see the hard drive on the other unix system so that I can share data between them. I run a cobol... (1 Reply)
Discussion started by: rongrout
1 Replies

4. UNIX for Dummies Questions & Answers

file systems for unix

please someone give me 3 file systems for unix HP-UX version !!! thnks (2 Replies)
Discussion started by: androc
2 Replies

5. Infrastructure Monitoring

Monitoring file systems backup

Hello, I have some questions. There are some File systems which are located on a SAN. There are two scenarios: 1) Some file systems are permanently mounted on certain servers 2) Others are part of a high availability cluster In case of a cluster the needed file... (1 Reply)
Discussion started by: frhling
1 Replies
IOPING(1)							   User Commands							 IOPING(1)

NAME
ioping - simple disk I/O latency monitoring tool SYNOPSYS
ioping [-LCDRq] [-c count] [-w deadline] [-p period] [-i interval] [-s size] [-S wsize] [-o offset] device|file|directory ioping -h | -v DESCRIPTION
This tool lets you monitor I/O latency in real time. OPTIONS
-c count Stop after count requests. -w deadline Stop after deadline time passed. -p period Print raw statistics for every period requests. -i interval Set time between requests to interval (1s). -s size Request size (4k). -S size Working set size (1m). -o offset Offset in input file. -L Use sequential operations rather than random. This also sets request size to 256k (as in -s 256k). -C Use cached I/O. -D Use direct I/O. -R Disk seek rate test (same as -q -i 0 -w 3 -S 64m). -q Suppress human-readable output. -h Display help message and exit. -v Display version and exit. Argument suffixes For options that expect time argument (-i and -w), default is seconds, unless you specify one of the following suffixes (case-insensitive): us, usec microseconds ms, msec milliseconds s, sec seconds m, min minutes h, hour hours For options that expect "size" argument (-s, -S and -o), default is bytes, unless you specify one of the following suffixes (case-insensi- tive): s disk sectors (a sector is always 512). k, kb kilobytes p memory pages (a page is always 4K). m, mb megabytes g, gb gigabytes t, tb terabytes For options that expect "number" argument (-p and -c) you can optionally specify one of the following suffixes (case-insensitive): k kilo (thousands, 1 000) m mega (millions, 1 000 000) g giga (billions, 1 000 000 000) t tera (trillions, 1 000 000 000 000) EXIT STATUS
Returns 0 upon success. The following error codes are defined: 1 Invalid usage (error in arguments). 2 Error during preparation stage. 3 Error during runtime. EXAMPLES
ioping . Show disk I/O latency using the default values and the current directory, until interrupted. ioping -c 10 -s 1M /tmp Measure latency on /tmp using 10 requests of 1 megabyte each. ioping -R /dev/sda Measure disk seek rate. ioping -RL /dev/sda Measure disk sequential speed. SEE ALSO
Homepage <http://code.google.com/p/ioping/>. AUTHORS
This program was written by Konstantin Khlebnikov <koct9i@gmail.com>. Man-page was written by Kir Kolyshkin <kir@openvz.org>. July 2011 IOPING(1)
All times are GMT -4. The time now is 05:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy