Configuring a text file for multiple search criteria by using pconfig variables
In addition to using the Graphical User Interface (GUI), you can use pconfig variables to configure multiple search criteria for a text instance.
This topic describes the pconfig variables that you must define to configure multiple search criteria for a text file instance.
pconfig variable | Required? | Description | Type |
---|---|---|---|
actName | y | Specify the name of the log file to be monitored | text |
actLogicalName | y | If the instance is a static instance and the logical name is provided through the GUI, the logical name is stored in this pconfig variable. | text |
actContainEnv | n | Specify whether the monitored file contains environment variables.
| Boolean |
actFileType | y | Specify the type of monitored log file.
| integer |
actFileFilter | n | Specify a filter program. |
|
actFileBegin | y | Specify the log file read position indicator.
| boolean |
actFileTreatment | y | Specify the log file treatment indicator.
| boolean |
actAlertEventTime | n | If the log file is not modified in the last specified minutes, an event is generated and the LOGStatus parameter goes into an alarm state. | integer |
ActFileTimestampChange | n | If you set the /PMG/CONFIG/actFileTimestampChange pconfig variable to 1, | integer |
actRegexType | y | Use the variable to look for the search strings:
| instance |
actStateEventCount1 | y | Specify the number of monitoring matches per scan before the state change. | integer |
actStateEventCount2 | n | Specify the number of monitoring matches per scan before the state change. | integer |
actStateEvent1 | y | Specify the state associated with actStateEventCount1.
| integer |
actStateEvent2 | n | Specify the state associated with actStateEventCount2.
| integer |
actAlertEventMessage | n | Specify a custom event message. | text |
actAlertEventOrigin | n | Specify a custom event origin. | text |
actNullifyString | n | Add a regular expression to nullify the alarm condition. | text |
actNoMatch | n | Specify whether an event is generated if no matches are found.
| Boolean |
actPriority | y | Specify the monitoring priority.
| integer |
customEvtMatchCount | n | If set to 1, only one event is generated per search criterion independent of number of matches found. | Integer |
searchIdentifierLabel | y | Describes the label for a search criterion that you define | String |
actSearchList | y | Stores the entire configuration information of an XML instance | Text |
InstOnFileNotExist | n | Allows an instance to get created on file that does not exist | Boolean |
Related topics
- Configuring-the-search-criteria-for-a-text-instance
- Defining-multiple-search-criteria-by-using-the-pconfig-branch
- Mapping-search-criteria-pconfig-variables-to-TrueSight-console