Share This:

When objects (queue managers, queues, etc.) are associated with a history template, event template or a logical type those associations remains regardless of whether the object is registered for monitoring.

 

Once associated, the intent is that history will be collected and events trigger whenever the object is registered for monitoring.   However, sometimes that object shouldn’t have been unregistered from monitoring.   This can lead to gaps in an object’s data in trend charts or reports.   It can also lead to event triggers failing to trigger as expected.

 

There a couple different ways to watch for this issue with BMC TrueSight Middleware and Transaction Monitor 8.0.00 or later.   An object that is not registered for monitoring is not presented on the Operations tab.   Noticing a missing object can be hard to do.   The Object Repository tab shows all objects and the objects in the tree that are not registered for monitoring are displayed in blue by default.   You may change the color, font and tooltip via Tools->Preferences->Unmonitored Objects so the objects stand out even more.

 

Whenever a list of associations is displayed (History Tab, Event Tab, Logical Types Tab) the object is also displayed with this same blue color (or the color and font you set in the preferences).   This will help identify why a particular event template may not be working as expected, why history is not available or why the object’s attributes are not showing values on a logical view.

 

Tip: You may register individual objects from the Object Repository Tab by right clicking and selecting Register Object for Monitoring.   Note, all ancestors of that object are also registered for monitoring.   Conversely, you may unregister an object by selecting Unregister Object from Monitoring.   All descendants of that object are also unregistered for monitoring.    The panels on the right side of the Object Repository Tab auto-refresh periodically.   However the tree coloring and fonts do not.   You only need to collapse and re-expand the parent of the object to see the changes.

 

Tip:  Now that object associations remain regardless of whether the object is registered for monitoring.   It is recommended policies be used to do that initial association.    There should be no need to use the maketmpltassoc utility to re-apply templates after a change in monitoring selection as is common for some customers where object monitoring is changed frequently.