Configuring using TrueSight console

You can define the monitoring criteria in policies and then apply them to the PATROL Agents. When you modify a policy, all the changes are automatically pushed to the PATROL Agents on which the policy is already applied. 

When a monitoring policy is applied to a PATROL Agent, the device or server that hosts the Agent is automatically added to the list of monitored devices. 

To create a monitoring policy

  1. Log on to the TrueSight console.
  2. In the navigation pane, expand Configuration and select Infrastructure Policies.
  3. In the Infrastructure Policies page, ensure that the Monitoring tab is selected and click Create Policy.
  4. In the Create Monitoring Policy page, specify the monitoring policy properties:

    monitoringpolicy_config.png
    1. Define the general properties.

The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.

    1. Select PATROL Agents.

The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.

    1. Specify values in at least one of the configuration tabs and click Save.

The [expand] macro is a standalone macro and it cannot be used inline. Click on this message for details.

Add and configure monitor types to a monitoring solution

  1. Ensure that the Monitoring tab is selected. By default, this tab is selected. If not, click it.
  2. Click Add Monitoring Configuration.
  3. In the Add Monitoring Configuration dialog box, configure the following properties:The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
    The following figure shows the Add Monitoring Configuration dialog box.
    Sample TS config screen.png
  4. Provide details for configuring the Collection Agent and click OK. For more information, see ITDA monitor type configuration.
    The configured monitor type is added as a new row in the Monitoring page.
  5. To modify the monitoring configuration, click the action menu for that configuration and select Edit. Modify the configuration and click OK.
  6. To delete a monitoring configuration, click the action menu for that configuration and select Delete. After you save the policy, the deleted monitor type configuration is removed from the selected PATROL Agents.

After you save or update a policy, the monitor type configurations are pushed to the selected PATROL Agents.

Configure filters to include or exclude data and events

After you configure the monitor types in the PATROL Agents, they send the collected data to the Infrastructure Management server. You can configure filters to restrict or allow data to be sent to the Infrastructure Management server. 

You can configure filters for all data, or for the data from a specific Agent or from a specific monitor type.

Note: A PATROL Agent applies a filtering policy during the next scheduled discovery or collection of a PATROL object (monitor type or attribute). That is, filtering is applied when the first collection occurs on the PATROL object after filtering rules are applied. Due to this behavior, there might be a delay in the deployment of the filtering rules on the PATROL object.

To configure filtering options

  1. Click the Filtering tab.
  2. Select one of the following options:
    • Agent Level: Filters data and events from the PATROL Agent. Select an appropriate filtering option from the list.
    • Monitor Type Level: Filters information from a specific monitor type. To specify the monitor type:
      1. Click Add Monitor Type.
      2. In the Add Monitor Type dialog box, select a solution and its version.
      3. Select a related monitor type from the list.
      4. If you want to specifically filter data and events from an attribute, select an attribute from the list. The default value is All.
      5. Select one of the following filtering option:
        • No Filter (Send all data and all events.)
        • Filter out data (Send all events, but no data.)
        • Filter out events (Send all data, but no events.)
        • Filter out data and events (Send no data and no events.)
      6. Click OK. The selected monitor type row is added to the table in the Filtering page.

        To add multiple monitor types for filtering data and events, repeat the previous steps a-f.
  3. To modify the properties of an existing filter level for Monitor Type Level option, click the action menu for that filter and click Edit.
  4. To delete a configured monitor type level for Monitor Type Level option, click the action menu for that level and click Delete.

Configure polling intervals

Specify the time interval between two consecutive data polls. You need to specify a separate poll interval for every parameter. 

  1. Click the Polling Intervals tab. 
  2. Add a polling interval:
    1. Click Add Polling Interval.

    2. Select values for the following options:

      - Monitoring Solution 

      - Version

      - Monitor Type

      - Parameter

      - Parameter Polling Interval

    3. Click OK. The polling interval is added to the table in the Polling Interval page.
  3. To add more polling intervals, repeat the previous step. 
  4. To modify the properties of a polling interval: Click the action menu associated with that polling interval, and select Edit.
  5. To delete a polling interval: Click the action menu associated with that polling interval and select Delete.

Define thresholds on PATROL Agents

Configure range-based thresholds for attributes of a monitor type on the PATROL Agents. You can specify whether the thresholds apply to a monitor type or to an instance of a monitor type.

Best practice
Define and specify global thresholds for KPIs and performance parameters in the Infrastructure Management server before you define server and Agent thresholds in the monitoring policies.  

  1. Click the Agent Threshold tab.

  2. Click Add Agent Threshold.  

    Specify values for the following properties:

  3. Click OK. The threshold is added to the table on the Agent Threshold page.

Create server-level instance thresholds

You can create thresholds for the monitor instances on the Infrastructure Management server. For information about the types of thresholds, see Server-thresholds-KPIs-and-baselines.

Best practice

  • Ensure that you complete the monitoring configuration before you configure the Infrastructure Management server thresholds because thresholds cannot be applied to monitors that are not configured.
  • Define global thresholds for KPIs and performance parameters in the Infrastructure Management server before you define the server and agent thresholds.  Server thresholds override global thresholds.
  • Use server thresholds for instance-level thresholds.  

 
To configure the server thresholds:

  1. Click the Server Threshold tab.
  2. Click Add Server Threshold.    

  3. Specify values for the following properties:


  4. Click OK.  
  5. To modify parameters of a threshold, click the action menu for that threshold and select Edit.
  6. To remove a threshold, click the action menu for that threshold and select Delete. After you save the policy, the deleted threshold configurations are removed from the selected PATROL Agents.
    After you save or update a policy, the new threshold configurations are pushed to the selected PATROL Agents.

Configure PATROL Agents

You can configure the properties of a PATROL Agent and specify the action that the Agent must perform when the policy is applied.

For more information, see Specifying objects in an authorization profile.

  1. Click the Agent tab.
  2. Specify the following properties:

Property

Description

Agent Default Account

User Name

The user name that you want to use to run the PATROL Agent. The user name must have access permissions to the PATROL Agent directory.

Note: You need to provide an Agent user name and password only if they are different from what was previously configured.

Password

Password for the specified user name

Confirm Password

Password for the specified user name

Restart Agent

Select this check box if you want to restart the PATROL Agent after the policy is applied.

Notes:
You must select this check box if you want the user name change to take effect.

While editing a policy, if you select Restart Agent and provide the same default account information as what was provided while creating the policy, the PATROL Agent is not restarted. To restart the PATROL Agent, use the Query Agent screen. For more information, see Performing-actions-on-a-PATROL-Agent.

 

Tag

Tags that you want to assign to the PATROL Agent. The format of each tag is tagName:tagDescription. If the tag description contains spaces, enclose the description within double quotes. You can also provide multiple tags, separated by commas.
For example, tag1:"Brief Description",tag2:"Description".

Integration Service

An Integration Service or an Integration Service cluster that you want to set as the PATROL Agent phone home. The supported values are as follows:

  • Single Integration Service
  • Integration Service Cluster

Event Configuration Properties

Event Forwarding Destination

Destination where the events that are generated by the PATROL Agents must be sent to. The supported destinations are as follows:

  • Integration Service Settings: Enables you to use the settings on the Integration Service to which the PATROL Agent is connected
  • Cells: Enables to send the events to one or more cells. In the Event Cell List box, specify the cells to which you want to send the events, separated by commas. The format of each cell is cellHostName/cellPort, where cellHostName is the name of the host where the cell is installed and the cellPort is the port number through which the Agent communicates with the cell. For example, host1/3181,host2/3182
    Also, in the Event Cell Shared Key box, specify the shared key which is used for encryption. The default shared key is mc. 
  • Do not send events: Stops sending the events

Event Format Container

String to append to the name of the events that are generated by the PATROL Agents. The default string is BiiP3.

Configure actions performed by Infrastructure Management server

Specify actions to be performed on the Infrastructure Management server when the policy is applied. The actions apply to all devices that are associated with the PATROL Agent and all the monitor instances that the Agent monitors.

Best practice

  • Do not use the automated group creation functionality excessively. Plan the groups that you need and configure accordingly.
  • Use the copy baseline feature only when you know the existing baseline is appropriate for a new Agent or device. For example, if you are adding an additional server to an Apache web server farm behind a load balancer where the new server has exactly the same configuration as the other servers in the farm (OS version, machine sizing and type, Apache version, Apache configuration) and the new Apache web server processes exactly the same types of transactions for the same application. If you are not certain, do not use the copy baseline feature.
  1. Click the Server tab.
  2. Specify values for the following properties:

Property

Description

Add Agent Monitors to Group

Name of a group on the Infrastructure Management server under which you want to add the monitors that are created as a result of this policy.

You can provide multiple group names, separated by commas. If a group does not exist, a new group is created. Use a forward slash (/) to specify a group in a hierarchy. For example, server/device1/myGroup.

If more than one group exists with the same name and a distinct hierarchy is not specified, monitor instances are not added to the group. The group names are case sensitive.

Add Associated Devices to Group

Select the check box to add all devices associated with the Agent monitors to the group specified in the Add Agent Monitors to Group field. If multiple groups are specified in the Add Agent Monitors to Group field, all the associated devices are added automatically to all the groups.

Note

This field is applicable and is functional only when you have a TrueSight Infrastructure Manager Server 10.5 or later in your environment. The devices from TrueSight Infrastructure Manager Server 10.1 and 10.0 are not added to the group even if this flag is selected.

Copy Baseline from Device

Display name of the device from which you want to copy the baseline.

Baseline for the monitor instances that are created on the child servers as a result of the policy are copied from the baseline of the corresponding monitor instances on the specified device. Baseline can be copied from the specified device only if the device is available on the child server.

The device names are case sensitive.

Associate Authorization Profiles with Devices

Name of the user group on the child servers to associate with the devices that are created as a result of the policy.

Devices are associated with the specified user group only if the user groups are available on the child server. The user groups are given both read and write permissions to the Authorization Profile.

You can provide multiple group names, separated by commas. The user group names are case sensitive.

Enables you to manually create Agent configuration rules such as Agent history retention, Agent run queue schedule settings, disabled Knowledge Modules, and so on.

Define and manage configuration variables

You can define individual configuration variables or import them from a ruleset file (.cfg).The PATROL Agent configuration is saved in a set of configuration variables that are stored in the Agent's configuration database. You can control the PATROL Agent configuration by changing the values of these configuration variables. Also, you can define a configuration variable, and the definitions are set on PATROL Agent when the policy is applied. Configuration variables that are defined on PATROL agents are retained even after disabling the policy. To delete the configuration variables, you must purge the PATROL Agent by using the following command:pconfig +PURGE -p <port> -host <hostname>By using this command, the configuration variable values of the PATROL Agent are restored to the default state, and the PATROL agent does not retain the previous configuration after an installation or an upgrade.You can also remove the variables by using the Add Configuration Variable dialog box.
NoteTo view the configuration variables that are available in the previous PATROL Agent versions, use the Query Agent functionality.If you are modifying the default Agent configuration, you must restart the PATROL Agent to reflect the changes. 
Best practice
  • Avoid creating a policy with both monitoring configuration and a configuration variable. You can create separate policies for monitoring configuration and configuration variables.
  • To keep the PATROL Agent in sync with the policy configuration, change an existing configuration variable's operation to DELVAR, instead of deleting it. After a configuration variable is deleted from the policy, you cannot perform any actions on it.

To import existing configuration variables

  1. In the Configuration Variable page, click the common action menu in the table and select Import.
    monpolicy_importcv.png
  2. Browse for and select the configuration file (.cfg) to be imported.
  3. Click Open. The variables from the file are added to the table.
NoteThe import operation supports only REPLACE, DELETE, and DELVAR operators. If the .cfg file contains the MERGE or APPEND operators, the file cannot be imported. You must delete these operators before importing the file.
 

To add new configuration variables

  1. Click Add Configuration Variable.
  2. In the Add Configuration Variable dialog box, specify values for the following properties and click OK:
    Property
    Description
    Variable
    Name for the configuration variable.
    Important: The variable names are case sensitive and must start with slash (/). You must enter the complete path for the variable, not just the name. If the intermediate variables do not exist, the variables are created.
    Operation
    Operation that you want to perform on the configuration variable. The supported operations are as follows:
    • REPLACE: Replaces the current value of the variable on the PATROL Agent if the variable already exists. Otherwise, a new variable is created with the specified value.
    • DELVAR: Deletes the variable from the PATROL Agent.
    • DELETE: Deletes the value of the variable, and the variable remains empty.
    Value
    Value that you want to configure for the variable and click OK. The configuration variable is added as a new row in the Configuration Variables table.
  3. To add another configuration variable, repeat the earlier steps.
    NoteFor the defaultAccount configuration variable, specify the value in the userName/password format. Note that the password can be a plain text or a PATROL Agent-encrypted string.
    Examples:patrol/patAdm1n
    patrol/FA4E70ECEAE09E75A744B52D2593C19FFor the SecureStore configuration variable, specify the value in the context/data format. Note that the context and data can be a plain text or a PATROL Agent-encrypted string.
    Examples:MY_KM1;MY_KM2;MY_KM3/mysecretdata“EDC10278901F8CB04CF927C82828595B62D25EC355D0AF38589CE4235A246F8C63F24575073E4ECD”where “EDC10278901F8CB04CF927C82828595B62D25EC355D0AF38589CE4235A246F8C63F24575073E4ECD” is the encrypted form of "MY_KM1;MY_KM2;MY_KM3/mysecretdata"
  4. To modify any value in a variable, click the action menu for the variable and select Edit.monpolicy_editdelcv.png
  5. In the Edit Configuration Variable dialog box,  modify the properties and click OK.
  6. To remove a variable, click the action menu for the variable and select Delete. 
Back to top

Related topics

Creating-a-deployable-package

Deploying-packages-to-PATROL-Agents

Configuring-in-a-BMC-ProactiveNet-environment

 

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