Home > Work & Tech > Where HTTP stats went in #Glassfish 3

Where HTTP stats went in #Glassfish 3

February 15th, 2012

It’s been awhile since I blogged and even longer since I posted something work related. I’ll hold off ranting about how bad Mac Lion sucks and post something that maybe some Googler will find useful 🙂

Glassfish logoIn my day job at ESPN, we have been using Glassfish V2 for awhile now. The performance kicks ass, they always have the latest EE features first and the open source community is pretty vibrant.

We are in the process of FINALLY upgrading to V3.

One of the things that came up was the HTTP stats / counts we traditionally monitor such as count2xx, count5xx, etc seemed to be missing. In V2.1, they were available under the mbean com.sun.appserv:type=GlobalRequestProcessor,name=http but that went bye-bye in V3.

Long story short, they just moved to a new place. Here’s how to find them:

asadmin enable-monitoring
asadmin set configs.config.server-config.monitoring-service.module-monitoring-levels.http-service=HIGH

Now look for this mbean: amx:pp=/mon/server-mon[server],type=request-mon,name=http-service/server/request

Or, and this is where V3 monitoring starts to get cool, you can hit the REST monitoring end point http://localhost:4848/monitoring/domain/server/http-service/server/request.json

Off to figure out how these probe thingys work as they look pretty powerful.

Categories: Work & Tech Tags:
Comments are closed.