Four winning ways to monitor machines through Web interfaces


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Four winning ways to monitor machines through Web interfaces
# 1  
Old 11-04-2008
Four winning ways to monitor machines through Web interfaces

11-04-2008 02:00 AM
System administrators need to keep an eye on their servers to make sure things are running smoothly. If they find a problem, they need to see when it started, so investigations can focus on what happened at that time. That means logging information at regular intervals and having a quick way to analyse this data. Here's a look at several tools that let you monitor one or more servers from a Web interface.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Programming

Application behaving in 3 different ways on 3 different machines

Hello. During the holidays I've been developing an application on my desktop computer at home. I setup a repository on github, so when I got back to work I cloned the repo to my laptop. It wouldn't work. The app is comprised of a client and a server, strangely enough the server would segfault... (10 Replies)
Discussion started by: erupter
10 Replies

2. Linux

Routing via several interfaces for hosted virtual machines

My setup consists of a hardware node, which hosts several virtual machines (OpenVZ, to be precise). The hardware node has two network interfaces (<ifA>, <ifB>) connected to different subnets (<networkA>, <networkB>). I want to route the traffic of certain VEs over <ifB> while routing the other VEs... (0 Replies)
Discussion started by: bakunin
0 Replies

3. UNIX for Dummies Questions & Answers

Ways to Access Files on Unix Server via Web

Hi all! I'm a web developer with a question. We have a contractor that is working on a project that requires the user to access a ton of files on the clients Unix server. He has plans to built a VB interface for on site windows users to access those files and wants us to develop a web based... (4 Replies)
Discussion started by: Imhotep1963
4 Replies

4. Shell Programming and Scripting

how to monitor 25 different digitalUnix and Sunsolaris machines

Hi I am a new Junior System Administartor..currently in our team we have around 25 different machines comprising of Sun-Solaris and digital Unix machines...and every morning we telent into the system to check 1)all demons are workin fine 2)all cpus are up 3)the memory is okay But... (4 Replies)
Discussion started by: xiamin
4 Replies
Login or Register to Ask a Question
niffconfig(8)						      System Manager's Manual						     niffconfig(8)

NAME
niffconfig - Configuration program for the Network Interface Failure Finder (NIFF) SYNOPSIS
/usr/sbin/niffconfig [-a] [-m] [-r] [-s] [-u] [-v] [-d num] [-o num] [-t num] [interface1 interface2...] OPTIONS
Adds an interface or interfaces, specified by the interface parameter. You cannot specify the -a option with the -m, -s, -r, or -u options. Specifies the time period, in seconds, that the traffic monitor thread uses between reads of the interface counters when it suspects there is a connectivity problem. This number must be smaller than the number given for the -t option. The default time period is 5 seconds. If num is not specified, niffconfig uses the default. Specifies the total number of traffic-free seconds that must elapse before the traffic monitor thread determines that a network interface has failed. This number must be at least the sum of the -d option and two times the -t option. That is, given the default time period for -d and -t, the -o option must be at least 20 seconds. The default time period for this option is 60 seconds. If num is not specified, niffconfig uses the default. Modifies the timing parameters of an interface that is already being monitored. Typically, this option is specified along with one or more of -t num, -d num, or -o num options. If none of these parame- ters are specified, the default value is used. You cannot specify the -m option with the -a, -s, -r, or -u options. Stops monitoring the specified interface. Obtains the status of the specified interface. Specifies the time period, in seconds, that the traffic monitor thread delays between reads of the interface counters when the network is running normally. The default time period is 20 seconds. If num is not specified, niffconfig uses the default. Displays the status of all interfaces currently being monitored to standard out (stdout). Displays the status, timer values, and description (verbose mode) of all interfaces currently being monitored to standard out (stdout). DESCRIPTION
The niffconfig command arranges for one or more network interfaces to be monitored for possible loss of connectivity. Timing parameters that govern how quickly an interface can be declared suspect or dead may be manipulated with this command. You can specify multiple inter- faces, separated by a space, on the command line. Note, you must be superuser to use the niffconfig command. Except for the -u and -u options, all niffconfig options require one or more network interfaces to be specified. EXAMPLES
To add the tu0 and tu1 interfaces to the list of monitored interfaces, enter: # niffconfig -a tu0 tu1 To change the time it takes to declare failure on the tu1 interface to 90 seconds, enter: # niffconfig -o 90 tu1 To display the status of all interfaces that are being monitored: # niffconfig -u To stop monitoring the tu0 interface: # niffconfig -r tu0 SEE ALSO
Daemons: niffd(8) Information: EVM(5), nifftmt(7) niffconfig(8)