$('a[name]').remove(); $('#ic-homepage__footer').before('

'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('

'); $("#ic-homepage__feed-tips").wrapInner('

'); });

IBM Tivoli Monitoring > Version 6.3 > User's Guides > Log File Agent User's Guide > Requirements and agent installation and configuration > Agent-specific installation and configuration IBM Tivoli Monitoring, Version 6.3


Configuration Files

The configuration (.conf and .fmt) files tell the agent what log files to monitor, where to find them and what formatting to use to read them.


About the Configuration Files

Agent configuration indicates the naming, the mode of agent operation, and the location of the configuration (.conf) file and the format (.fmt) file. The two configuration files control the file monitoring, and their location must be specified during the IBM Tivoli Monitoring configuration process. Subsequent configuration is drawn from these files.

If you use the subnode feature to create monitoring profiles, you can have more than one pair of configuration (.conf), and format (.fmt) files. See Subnodes.

Example configuration and format files are provided with the agent, for example regex1.conf and regex1.fmt are configuration and format files for use with regular expressions. The example files can be found in the examples directory on the agent media image.

The path and file names of the (.conf), and (.fmt) files must be ASCII only. A useful convention is to name your configuration and format files to match the application or log file you want to monitor.

Configuration file Filter statements apply only to EIF. The Filter statements that can be used in the .conf file, apply to any EIF events that are sent to an EIF receiver, but do not apply to events sent to a Tivoli Enterprise Monitoring Server. Therefore, if filtering of events to the Tivoli Enterprise Monitoring Server is important, use the format file. For example, assigning events in the format file to the special "*DISCARD*" class causes them to be ignored. This mechanism is honored through either event channel.


Parent topic:

Agent-specific installation and configuration

Related concepts:

Format file
Format file specifications

Related tasks:

Configure from the configuration panel

Related reference:

Configuration file


+

Search Tips   |   Advanced Search