PerformanceEngineer.com » Monitoring

Orbitz Open Sources Monitoring Tools ERMA and Graphite

charlie — Tue, 01 Jul 2008 16:36:31 +0000

I saw this recent article about some new tools from Orbitz: InfoQ: Orbitz Open Sources Monitoring Tools ERMA and Graphite Graphite looks particularly interesting as it has features overcoming some of the things I don’t like about RRDtool: Graphite is a Python web application that has been developed to provide scalable storage and visualization for numeric time-series [...]

dynaTrace

charlie — Wed, 16 May 2007 02:47:32 +0000

dynaTrace is a new company and tool that offers a robust java profiling solution that is actually easy to use and install.

AspectJ: Using AOP for Performance Monitoring

charlie — Fri, 30 Mar 2007 02:38:50 +0000

One of the great features of Java 5 (see: Pro Java 5 ) is Aspect technology. Here, I'll show you how you can use custom Aspects to instrument your application and monitor using AspectJ and Jamon.

Application Instrumentation with WebLogic Diagnostic Framework (WLDF)

charlie — Sat, 24 Mar 2007 03:18:57 +0000

The WebLogic Diagnostic Framework, while powerful, is not the easiest beast to work with. After a couple of days of messing around with it, I finally figured out how to instrument my application code's methods.

Dtrace with Solaris10

charlie — Mon, 19 Mar 2007 02:58:43 +0000

Dynamic Tracing (DTrace) is a debugging tool introduced in the Solaris 10 Operating System to help debug systemic problems that are difficult to diagnose using traditional debugging tools and mechanisms. This tool takes advantage of points of instrumentation in the Solaris OS to present information useful for debugging errors and investigating performance issues in applications running on the Solaris OS.

Glassbox

charlie — Sun, 18 Mar 2007 16:40:50 +0000

Glassbox - http://www.glassbox.com/ - looks promising. It's open source and easy to install.

From the glassbox.com website:

Glassbox is a valuable complement to load testing tools. When you drive load through the app, Glassbox will automatically pinpoint bottlenecks and report their complete stack traces. That means developers will see exactly where the problem lies, without having to recreate the conditions of your test.

Because Glassbox is designed to look for specific problems rather than to collect profiling data for human analysis, it introduces negligible performance overhead. It can even be used in production apps.

Monitoring WebLogic using JMX

charlie — Fri, 16 Mar 2007 21:29:00 +0000

It's not as straightforward as you might think or expect, but once setup, gives a lot more insight into the behavior of your applications. Use your favorite JMX client (jconsole, jManage, SiteScope, MC4J, etc.) to monitor thread pools, database connections, memory usage and any other MBean attributes.

There are two ways (that I know of) to enable a WebLogic application for monitoring using JMX.

Enable IIOP and default user for the WebLogic server
Use the Java 5 JMX remote capabilities

Mercury Diagnostics

charlie — Wed, 14 Mar 2007 03:41:08 +0000

The Mercury Diagnostics profiler can be a great tool to use for identifying bottlenecks and performance problems in your J2EE application. It offers many of the features you'd find on more expensive tools (i3, PerformaSure, etc.). Unfortunately, all of the features may or may not work, depending on your application.

InfraRED

charlie — Wed, 14 Mar 2007 03:40:30 +0000

When I first stumbled upon InfraRED (http://infrared.sourceforge.net/ I thought it was great, but the more I used it, the more bugs I found. Still, it is an open source tool, so if I was so inclined (or had the ability) I could try to fix the bugs. The original project owners appear to have abandoned the project, however.