Login or Register to Ask a Question and Join Our Community


OS X OpenSource RSS

Hyperic HQ 4.0

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X OpenSource RSS Hyperic HQ 4.0
# 1  
Old 11-12-2008
CPU & Memory Hyperic HQ 4.0
ImageAbout Hyperic HQ
The award-winning monitoring software designed specifically for web applications, whether hosted in the cloud or on premise. Its unique ability to automatically discover, monitor and manage software services, regardless of type or location, enables companies to easily create a unified view of the performance and health of their applications. Its multi-platform approach to monitoring and management helps pinpoint, correct, and prevent problems at every major layer, including hardware, networks, virtualization, and applications.

With fast deployment, enterprise security, and extensibility, organizations will save time and money scaling their business. Designed to support both virtualized and non-virtualized infrastructure at scale, Hyperic is the standard for web operations teams of all sizes, including CBS Interactive, hi5 Networks, Mosso and more.

More from Apple...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT CENTOS

dbus-monitor

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)