Viewing Monitoring Data

Example 3

Attempt to get a specific attribute from a subsystem:

asadmin> get --user admin-user--monitor server.jvm.uptime-lastsampletime

Returns:

server.jvm.uptime-lastsampletime = 1093215374813

Example 4

Attempt to get an unknown attribute from within a subsystem attribute:

asadmin> get --user admin-user--monitor server.jvm.badname

Returns:

No such attribute found from reflecting the corresponding Stats interface: [badname]

CLI137 Command get failed.

To Use the PetStore Example

The following example illustrates how the asadmin tool might be used for monitoring purposes.

A user wants to inspect the number of calls made to a method in the sample PetStore application after it has been deployed onto the Enterprise Server. The instance onto which it has been deployed is named server. A combination of the list and get commands are used to access desired statistics on a method.

1Start the Enterprise Server and the asadmin tool.

2Set some useful environment variables to avoid entering them for every command:

asadmin> export AS_ADMIN_USER=admin AS_ADMIN_PASSWORD=admin123 asadmin>export AS_ADMIN_HOST=localhost AS_ADMIN_PORT=4848

3List monitorable components for instance server: asadmin> list --user adminuser --monitor server*

Returns (output will be similar to):

server server.applications server.applications.CometEJB server.applications.ConverterApp server.applications.petstore

Chapter 18 • Monitoring Components and Services

199

Page 199
Image 199
Sun Microsystems 820433510 manual To Use the PetStore Example, Attempt to get a specific attribute from a subsystem