08-24-2011
Nagios is another good option. GroundWork is actually based on Nagios.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
2. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
3. Shell Programming and Scripting
I have two processes that I need to keep running. The first process is a server, the second is basically a canvas for creating images which get saved to a directory. So I plan on using launchd (Mac OS 10.5) on a server to check every minute or so to make sure two things are true:
1) Both apps... (3 Replies)
Discussion started by: Solerous
3 Replies
4. AIX
we have several deamon processes which were killed for some unknown reasons. we have to bring the deamon back manually everytime. Deamons running on 2 identical instances. It is ok on one instance but be killed 3 or 4 times a day on another. Any idea how to monitor it? like who/how the processes be... (3 Replies)
Discussion started by: hamiltonhall
3 Replies
5. Infrastructure Monitoring
snmpget -v 1 -c COMMUNITYSTR hostname OID
what OIDs would I use to get information on all the processes and disk space information that are on a particular host.
where can i find out information on all of this?
thanks (3 Replies)
Discussion started by: SkySmart
3 Replies
6. Shell Programming and Scripting
GM,
Can you pls help how to write a script to monitor different processes on different unix servers and send the output to a /tmp/report file, earlier my boss asked me to write a script to monitor just one process running on different servers and send the output to a file so I wrote this
exec... (0 Replies)
Discussion started by: baders
0 Replies
7. Hardware
Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies
8. Linux
Hi Guys,
Monitoring 'Total Processes' on Linux servers has been always something you 'should' do.
My question is - why? Is it relevant anymore?
If you monitor memory and cpu params, you have a pretty good idea about what's going on.
Is the number of processes really matter?
Thanks (1 Reply)
Discussion started by: DjDeaf
1 Replies
9. Infrastructure Monitoring
Sorry if this is the wrong forum
Searching for Saas Monitor service which monitor my servers which are sitting in different providers .
This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard.
The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
LEARN ABOUT DEBIAN
mailping-latency
2004-04-16
mailping
0.0.4
MAILPING-LATENCY(1) Mailping MAILPING-LATENCY(1)
NAME
mailping-latency - Munin plugin to graph latency of mail deliveries
SYNOPSIS
/usr/share/mailping/munin-plugins/mailping-latency {[config] | ['']}
DESCRIPTION
mailping-latency is a Munin plugin that monitors the time spent between email submit and it's delivery.
Configuration output
When passed config, it outputs Munin configuration information. If there are no circuits defined (no subdirectories in /etc/mailping), it
specifies that Munin should draw no graph either.
If configuration files /etc/mailping/circuit/warnlatency and /etc/mailping/circuit/faillatency exist, the values in them are passed on to
Munin, for use in Nagios alert integration.
Value output
When passed an empty string '', mailping-latency outputs latency of last successful probe message, for each configured circuit.
FILES
/etc/mailping/
List of circuits that exist; each subdirectory is a circuit.
/etc/mailping/circuit/warnlatency
If latency is greater than this many seconds, a Nagios warning is triggered by Munin (assuming it has been configured to do that).
Default: no warnings.
/etc/mailping/circuit/faillatency
If latency is greater than this many seconds, a Nagios alert is triggered by Munin (assuming it has been configured to do that).
Default: no alerts.
/var/lib/mailping/state/circuit/latency
Amount of latency in seconds of the last successful probe for circuit.
ENVIRONMENT
MAILPING_CONFIGDIR
Override the location of the configuration directory. Default: /etc/mailping
MAILPING_STATEDIR
Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories
named after the circuit name. Default: /var/lib/mailping
SEE ALSO
mailping-success(1), mailping-cron(1), mailping-store(1), munin-run(8), munin-node(8)
AUTHOR
Tommi Virtanen <tv@havoc.fi>
Havoc Consulting
Author.
COPYRIGHT
Copyright (C) 2004 Havoc Consulting
mailping 0. 2004-04-16 MAILPING-LATENCY(1)