Your InfoHub distribution comes with a GT.M Monitoring Reference Implementation that can monitor GT.M messages in the system log and GT.M databases V6.0-002 and above. It is possible to monitor any GT.M version prior to V6.0-002 with some modifications. Modifications are necessary because the format and content of file header listings, messages, and gleaning techniques vary from release to release. For example, to monitor an earlier release which lacks the $ZPEEK() function, you would have to use other techniques, such as parsing DSE output for example, with a program such as the %DSEWRAP utility.
The following table contains information about the files that are used with the GT.M Monitoring Reference Implementation. These files reside in an InfoHub installation. You can view the configuration files from the samples subdirectory of your InfoHub distribution or download them from the links in the table. You can also click 
to download all files of the GT.M Monitoring Reference Implementation together or open directly from http://tinco.pair.com/bhaskar/gtm/applications/infohub/GTM_Monitoring_RI.zip.
|
Component |
Name |
Description |
Download |
|---|---|---|---|
|
InfoHub Configuration File |
|
Configuration file used to configure a server. It includes InfoDict files gtmmessages.conf, gtmfields.conf, gtmdbregions.conf and gtminstances.conf for monitoring database instances. gtmmessages.conf and gtmfields.conf are user created files and are subsets of IHRegionReplInfoDict.conf and IHGtmSyslogMessages.conf respectively. gtmdbregions.conf and gtminstances.conf are created and updated by the routine gtmConfigGenerator, described below. |
|
|
GT.M Sylog Messages InfoDict |
|
Provides the SyslogInstances InfoDict which is used to define GT.M messages to be monitored. Use this file as the basis for gtmmessages.conf. |
|
|
Limited InfoDict of GT.M Sylog Messages |
|
Provides a sample SyslogInstances InfoDict that defines a small subset of GT.M messages to be monitored. This is a simple starting point for testing InfoHub's syslog monitoring capabilities. |
|
|
Full Region and Replication InfoDict |
|
Defines region and replication fields of a GT.M region and groups them in the following categories (InfoDict Domains)– |
|
|
Full Region and Replication InfoDict |
|
Defines a subset of region and replication fields of a GT.M region and groups them in the following categories (InfoDict Domains)– |
|
|
Syslog FileLine Gleaner |
|
A gleaner whose InfoExpr function reads /var/log/messages line-by-line and converts GT.M only messages in the form of key:value pairs and files them in the InfoHub Database. A set of GT.M version specific routines are provided (in the plugins subdirectory of the distribution) that assist the gleaner, e.g., messages60002.m. |
|
|
GT.M Application Instance Configuration Extraction Script |
|
Use this script to source your GT.M application configuration and output the relevant pieces of information to monitor the GT.M application. The output file is processed by gtmConfGenerator (described below) to generate an publisher configuration and InfoDict entries for the GT.M instance to be monitored. This standalone script does not require any part of the InfoHub to be present. The script will not extract GT.M encryption settings. Those must be defined after gtmConfGenerator generates the Publisher configuration for the GT.M application. |
|
|
InfoHub Configuration generator for GT.M application instances |
|
Creates and/or updates InfoHub configuration files, gtmdbregions.conf and gtminstances.conf, and instance specific gleaners named IdMapFor<PublisherNameHere>.m. dbinstances.conf includes gtmdbregions.conf and gtminstances.conf. You should not need to edit these files by hand. After each execution of this routine, be sure to reload the InfoHub configuration file. gtmdbregions.conf contains unique InfoDict entries for each newly discovered GT.M database region and replication instance. gtminstances.conf contains the publisher configuration for the to be monitored GT.M application instance. IdMapFor<PublisherNameHere>.m gleaners should be placed in $ihsrcdir by default. If the routine cannot find that directory, the user will be directed to copy the files there. |
|
|
SNMP daemon sample configuration |
|
A sample configuration for the Net-SNMP daemon |
|
|
SNMP trap daemon sample configuration |
|
A sample configuration for the Net-SNMP trap daemon |
|
The following illustration shows how the GT.M Monitoring Reference Implementation sets up an InfoHub framework for monitoring your GT.M database.
