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
niff(7) 						 Miscellaneous Information Manual						   niff(7)

NAME
niff - Network Interface Failure Finder (NIFF) introductory information. DESCRIPTION
The Network Interface Failure Finder, NIFF, is a facility for detecting and reporting possible failures in network interface cards (NICs) or their connections. Detection is done by monitoring device counters and attempting to generate traffic to NICs suspected of having failed. Reporting is done using the Event Manager subsystem (EVM). NIFF does not drive failover operations; that is the responsibility of the application that subscribes to NIFF's EVM events. Appropriate courses of action may include selecting another network interface for communication or if it is a clustered environment, migrating an application. See nr(7) for further information. At the heart of NIFF is the traffic monitor thread. The traffic monitor thread tracks changes in the network device's counters, and notes if the received packet counter remains unchanged since the previous snapshot. As long as the counter continues to increase, the traffic monitor thread assumes the NIC is functioning. See nifftmt(7) for further information. The traffic monitor thread can monitor any network interface. The configuration utility, niffconfig, is used to activate and administer the traffic monitor thread. See nifftmt(7) and niffconfig(8) for further information. The Network Interface Failure Finder daemon, niffd, is a traffic generator for network interfaces that have been classified inactive by the kernel traffic monitor thread. The purpose of niffd is to get the interface packet counters to increment, signifying the interface is still alive and well. See niffd(8) for further information. SEE ALSO
: nifftmt(7), nr(7), niffconfig(8), niffd(8) delim off niff(7)