Registering objects for monitoring using qpreg


QPREG is a utility program used to register objects with a monitoring extension. It can be found in the same directory as the extensible agent.

Objects are defined as a topic consisting of two paths; a type path and an instance path. Each path is delimited by an exclamation mark and the same number of elements exist in each. Together they form a hierarchy of nodes where each node has a type name and instance name; the next node is the child of the preceding node. You can see this hierarchy when you view the objects in the Management Console and expand each item in the tree which is either a type or instance name.

When using the qpreg tool, you specify the topic paths omitting the top level node consisting of the agent host which is added for you.

SYNTAX:

qpreg [-u] [-l] <ExtensionName> <type path> <instance path>

-u unregisters instead of registering
 -l causes qpmon to recycle, reading the new definitions

There are several ways to begin monitoring, although some depend on the type of technology and extension being monitored. These processes can also be used if, for some reason, discovery of objects has been disabled.

For objects monitored by one of the Performance and Availability extensions the following methods exist:

  • Polices: policies can be defined for those extensions that discover objects on their own and add them to the object repository. These policies can apply actions that cause those objects to be registered for monitoring. Refer to Defining-policies for more details.
  • The objects in the object repository can be viewed using the Object Repository tab of the Management Console. Objects can be registered for monitoring using this tab. Refer to Working-with-the-Object-Repository for more details.
  • The repomgr command line tool run from the services installation directory can also be used to register an object or set of objects for monitoring. Refer to Using the Repomgr Command Line Tool for more details.
  • The qpreg command line tool run from the TMTM extensible agent installation directory can also be used to register an object for monitoring. Additionally, there are shell scripts to make it easier to register MQ objects for monitoring. Refer to  for more details.
  • Additionally, some extensions handle registration for monitoring themselves. Refer to Running-performance-and-availability-monitoring-extensions for extension details.

For more information about transaction tracing, refer to Defining-transaction-pathways-to-monitor-your-infrastructure.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*