Structured Log File Policies (Events, Metrics, and Generic Output)

This policy type reads entries in a log file and matches the desired text against the log file structure fields defined by using the OM pattern-matching language. When the policy finds a match and certain conditions apply, the policy responds by sending event, metrics, or generic output data to OMi. You can define the details of the data sent to OMi based on information in the log file.

You must have the format and syntax of the log file that the policy reads. You must define a log file structure to match on the entries in the log file that contain the data you want to read and forward to OMi. For examples of how the log file structure is defined, see Defining a log file structure by using OM pattern-matching language topic.

What Data Is Collected

The structured log file policy sends to Operations Connector data that is extracted from any log file row that matched against the log file structure fields defined by OM pattern-matching language.

Before setting up the structured log file policy, you should be clear about the purpose and usage of the data in OMi.

The specific data that is forwarded to OMi (for events), stored on the Operations Connector system (for metrics), or forwarded to a consumer application (generic output) is controlled by the type of policy (event, metrics, or generic output policy) and by the defaults and rules that the policy applies to the data (events and metrics only).

Related topics

Defining a log file structure by using OM pattern-matching language