Sponsored Content
Full Discussion: Monitoring Unix systems
Top Forums UNIX for Dummies Questions & Answers Monitoring Unix systems Post 302099737 by rhfrommn on Wednesday 13th of December 2006 12:52:39 PM
Old 12-13-2006
The company I work for now uses Nagios, Tivoli, and Splunk. At my previous job we used Sysedge in my department and I believe Openview in others.

I'm sure any of those tools could do what you are asking with some effort on your part even if they can't straight out of the box. They all use SNMP for handling events and communication. You can write scripts defining exactly what you want monitored, then let the tool take care of the alerting, logging, etc. using SNMP. Of course, all come with plenty of pre-built monitors for things many people want to see. But if you want to monitor something they don't have built-in you can always write your own script. For example, with Sysedge at my previous job we wrote a script that listed exact text strings we wanted to monitor in our /var/adm/messages file on Solaris to catch errors specific apps we used generated even though Sysedge couldn't monitor those apps out of the box. You could do the same thing, or hire a consultant or pay the company to write them for you as part of the implementation.

As mentioned before, you could also do it yourself. At my current job we also have a home-grown tool that generates graphs of just about any performance parameter you can see with standard Unix commands. It collects data on each server then runs a lightweight http server so you can use a web browser to see tables or generate graphs. Specific to your needs, it can do pages in and out per second, pagefaults per second and similar data. I don't think it can do it per process though. Although again, since we wrote it ourselves if we needed that data we could adjust the data collection scripts to implement that.

I guess that's just more details in support of my original point. The tools exist to get what you want. But it will probably require modifying a commercial app or writing pieces on your own to get some of the specific things you requested.

As a minor digression - that's part of the difference in philosophy between Unix and Microsoft. Unix tends to give you lightweight but powerful tools. You can do just about anything with them, but you need to do some work to get what you want. Microsoft on the other hand gives you more "complete" and finished tools, but if they don't do exactly what you want them to you're probably out of luck.
 

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
PERF-TRACE(1)							    perf Manual 						     PERF-TRACE(1)

NAME
perf-trace - strace inspired tool SYNOPSIS
perf trace DESCRIPTION
This command will show the events associated with the target, initially syscalls, but other system events like pagefaults, task lifetime events, scheduling events, etc. Initially this is a live mode only tool, but eventually will work with perf.data files like the other tools, allowing a detached record from analysis phases. OPTIONS
-a, --all-cpus System-wide collection from all CPUs. -e, --expr List of events to show, currently only syscall names. Prefixing with ! shows all syscalls but the ones specified. You may need to escape it. -o, --output= Output file name. -p, --pid= Record events on existing process ID (comma separated list). -t, --tid= Record events on existing thread ID (comma separated list). -u, --uid= Record events in threads owned by uid. Name or number. -v, --verbose= Verbosity level. -i, --no-inherit Child tasks do not inherit counters. -m, --mmap-pages= Number of mmap data pages. Must be a power of two. -C, --cpu Collect samples only on the list of CPUs provided. Multiple CPUs can be provided as a comma-separated list with no space: 0,1. Ranges of CPUs are specified with -: 0-2. In per-thread mode with inheritance mode on (default), Events are captured only when the thread executes on the designated CPUs. Default is to monitor all CPUs. --duration: Show only events that had a duration greater than N.M ms. --sched: Accrue thread runtime and provide a summary at the end of the session. -i --input Process events from a given perf data file. SEE ALSO
perf-record(1), perf-script(1) perf 06/30/2014 PERF-TRACE(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