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
dbus-monitor(1) 					      General Commands Manual						   dbus-monitor(1)

NAME
dbus-monitor - debug probe to print message bus messages SYNOPSIS
dbus-monitor [--system | --session | --address ADDRESS] [--profile | --monitor] [watch expressions] DESCRIPTION
The dbus-monitor command is used to monitor messages going through a D-Bus message bus. See http://www.freedesktop.org/software/dbus/ for more information about the big picture. There are two well-known message buses: the systemwide message bus (installed on many systems as the "messagebus" service) and the per- user-login-session message bus (started each time a user logs in). The --system and --session options direct dbus-monitor to monitor the system or session buses respectively. If neither is specified, dbus-monitor monitors the session bus. dbus-monitor has two different output modes, the 'classic'-style monitoring mode and profiling mode. The profiling format is a compact for- mat with a single line per message and microsecond-resolution timing information. The --profile and --monitor options select the profiling and monitoring output format respectively. If neither is specified, dbus-monitor uses the monitoring output format. In order to get dbus-monitor to see the messages you are interested in, you should specify a set of watch expressions as you would expect to be passed to the dbus_bus_add_match function. The message bus configuration may keep dbus-monitor from seeing all messages, especially if you run the monitor as a non-root user. OPTIONS
--system Monitor the system message bus. --session Monitor the session message bus. (This is the default.) --address ADDRESS Monitor an arbitrary message bus given at ADDRESS. --profile Use the profiling output format. --monitor Use the monitoring output format. (This is the default.) EXAMPLE
Here is an example of using dbus-monitor to watch for the gnome typing monitor to say things dbus-monitor "type='signal',sender='org.gnome.TypingMonitor',interface='org.gnome.TypingMonitor'" AUTHOR
dbus-monitor was written by Philip Blundell. The profiling output mode was added by Olli Salli. BUGS
Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/ dbus-monitor(1)