Guidelines for Using the list and get Commands for Monitoring

The underlying assumptions for using the list and get commands with dotted names are:

• Any list command that specifies a dotted name followed by a wildcard of the form .* lists a hierarchical tree of child nodes from the specified node. For example, the following command lists all children of the applications node, their subsequent child nodes, and so on:

  list --monitor=true server.applications.*

• Any list command that specifies a dotted name preceded or followed by a wildcard of the form *dottedname or dotted * name or dottedname * lists all nodes and their children that match the regular expression created by the specified matching pattern.

• A get command followed by a .* or a * gets the set of attributes and their values that belong to the node specified.

The following tables show the command, dotted name, and corresponding output at the top level (server) of the tree.

Table 10–4 Server-Level Monitoring Commands Output

Command	Dotted Name	Output
list --monitor=true	server.*	Hierarchy of child nodes below server node
get --monitor=true	server.*	Data for all monitorable objects under the top-level server

The following table shows the command, dotted name, and corresponding output for the JVM level.

Table 10–5 JVM-Level Monitoring Commands Output

Command	Dotted Name	Output
list --monitor=true	server.jvm.*	Monitorable objects under the JVM node
get --monitor=true	server.jvm.*	Attributes and values corresponding to JVM attributes

The following table shows the command, dotted name, and corresponding output for the web level.

Table 10–6 Web Container-Level Monitoring Commands Output

Command	Dotted Name	Output
list --monitor=true	server.web.*	Monitorable objects under the web service node
get --monitor=true	server.web.*	Attributes and values that correspond to web attributes