Troubleshooting monitoring policies

Where are performance and event data configurations stored?

Configuration of the performance and event data that is sent from the PATROL Agents to BMC ProactiveNet Performance Management or TrueSight Infrastructure Management is defined in policies. These policies are applied to specific Agents based on the Agent selection criteria that is defined in each policy. For more information, see Managing policies.

Configuration is applied to a PATROL Agent

First, a PATROL Agent reads the tag information from the /AgentSetup/Identification/Tags/Tag/tagName pconfig variable, where tagName is the name of the tag. The PATROL Agent then sends the information to the Integration Service, which passes the information to TrueSight Presentation Server. TrueSight Presentation Server evaluates which policies match the tags or the Agent properties, determines the final configuration to be applied, and sends the configuration information to the PATROL Agent.

When the configuration is applied to a PATROL Agent

PATROL Agent initiates a configuration request after certain events, such as Agent installation, Agent restart, Agent auto-connection with Integration Service, or changing a tag on the Agent. If no policy matches the Agent conditions, the configuration information is not shared. The Agent does not receive the configuration until a matching policy is created. If a policy is created or updated, changes are pushed from TrueSight Presentation Server, through the Integration Service, to PATROL Agents.

Where are the PATROL Agent configurations stored

The monitoring solutions configuration is stored in the /ConfigData pconfig branch. The pconfig variables received by PATROL Agent from TrueSight Presentation Server are applied with the REPLACE request. For the configuration under /ConfigData, only the difference between the configuration received and the configuration that the Agent contains is applied. If some configuration is not received for a particular class, it is considered to be deleted and is deleted from /ConfigData. For the configuration under /AgentSetup, it is applied directly. 

Note: If there are conflicts, for /AgentSetup configurations, the variables under the /ConfigData pconfig branch take precedence.

How to enable debugging in TrueSight Presentation Server?

The following table provides information about the steps to enable debugging in TrueSight Presentation Server in different versions of the product. After you enable debugging, enable the policy to reproduce the issue so that it writes the issue or information in logs.

How to use a different realm in a monitoring policy?

1. Export the policy using cmapolicymigration.bat and then edit the policy to change the realm as following:
   cmapolicymigration.bat export -p policyName -n newName -d outputDirectory

2. Change the realm from BmcRealm to default realm "*"

   Existing code	Change it to
   "tenant" : {   "name" : "BmcRealm",   "id" : "BmcRealm"   },	"tenant" : {  "name" : "*",  "id" : "*"  },

3. Save the policy and import the policies to TrueSight Presentation Server by running the following command:
   cmapolicymigration.sh import -f -d inputPoliciesDirectory

How to migrate BMC ProactiveNet Performance Management 9.6 CMA policies to TrueSight Presentation Server policies?

1. Export the policy from BMC ProactiveNet Performance Management by running the following command:
   Windows: C:\Program Files\BMC Software\ProactiveNet\pw\pronto\lib\DataMigrator\cmapolicymigration.bat
   UNIX: /usr/pw/pronto/lib/DataMigrator/cmapolicymigration.sh
   You can also use the following options with this command:
   -d <output_directory> - Output directory is the location where policy-related data files are saved after export. If -d option is not provided, the current directory is considered as the output directory. 
   -p <policyname> - Name of the policy to be exported. If the name contains spaces, enclose the policy name in parenthesis (""). 
   -n <newName> - You can use this option to save an existing policy with a new name. Use N/A when all policies are exported. The exported policies are saved with this new name (N/A when all policies are exported.) 
   For example: cmapolicymigration export -d <output_directory> [all] [-p policyName [-n <newName>]].
   The exported file has the extension .mo and the policies are defined in the json format. 
2. Open the .mo file in an editor.
3. At the bottom of each policy, there is a section that includes the following field names: name, id, type, agentSelectionCriteria, tenant, precedence, description, enabled.
4. Add the following fields to the policy json record: shared, associatedUserGroup, and owner (change the owner field to an LDAP user). 
   "shared" : false, 
"associatedUserGroup" : "Administrators", 
"owner" : "admin", 
   Here, owner is the username to which the ownership of this policy belongs, associatedUserGroup is one of the groups associated with the owner, and shared indicates if the policy is shared with other users in the group. 
5. In the policy, make sure that the values for tenant (name, id) point to the correct SSO realm like the following: 
   "tenant" : { 
"name" : "BmcRealm", 
"id" : "BmcRealm" 
}, 
   Click here for a sample of the policy section after the changes. 
6. Copy this file to the TrueSight Presentation Server server.
7. In the command prompt, go to the following directory <TrueSight Presentation Server_Install_Location>/truesightpserver/bin.
8. Invoke the following command.
   Note: Use the directory and do not specify a file. The utility imports all .mo files in the directory.
   cmapolicymigration.bat import -d <directory location of the bin directory>

Common issues