TrueSight Operation Management (TSOM) Data & Event Filtering  Best Practices

Use Case 1: Disabling Logical Disk Monitoring 
 
Instance filtering is applied to the Parent Container node, therefore only the parent node goes Marked for Deletion (MFD). Child instances are still monitoring data and are showed at the root level and parent hierarchy is not shown. 
 
We are using the following versions in this example: 
 
• Version 10.7 PATROL Agent • Version 11.x TSIM Server  
 
Instance Filtering applied to the Monitor Type “Logical Disk Performance” - > SID NT_LOGICAL_DISKS_CONTAINER: 


After applying the instance filtering, parent instance i.e. Logical Disks (Logical Disk Performance) goes into MFD: 




Use Case 2: Removing Monitor Instance (Parent Container) for Logical Disk  
 
In this example we demonstrate that a customer can, if required, remove the parent container of the attributes that reside within in. 
 
We are using the following versions in this example: • PATROL Agent version: 10.7 • TSIM Version: 10.7 FP3


Instance filtering applied to the “Logical Disk Performance” Monitor Type: 


The Parent Hierarchy (Container) is not shown as configuration applied removed the Monitored Instance. However, as per design the attribute (Child) is still collecting.  

If you have instances in a parent-child hierarchy, you must configure instance-level filters separately for each sub-node of the parent and child: 


Please follow below links for more details:

Description	Version	Location
Filtering and refining PATROL agent data collection in TrueSight Operation	N/A	https://communities.bmc.com/events/1288
TrueSight Best Practices Webinar Calendar	N/A	https://communities.bmc.com/docs/DOC-107967
TSOM Documentation	11.3	https://docs.bmc.com/docs/TSInfrastructure/113/defining-amonitoring-policy-774797086.html
Health Check Tool	N/A	https://communities.bmc.com/docs/DOC-122750
TSOM Release Notes for Service and Fix Packs	11.3.03	https://docs.bmc.com/docs/TSOperations/113/release-notes-andnotices-843619555.html