'); $("#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

---

Configure from the configuration panel

Use the configuration panel to configure the agent from the Tivoli Enterprise Portal Server graphical user interface.

Procedure

Use a Tivoli Enterprise Monitoring Server

• To configure the agent from the Manage Tivoli Enterprise Monitoring Services graphical interface, select the agent from the list, right-click, and choose Configure on UNIX/Linux, or Configure Using Defaults on Windows. The configuration panel opens. The configuration panel has two tabs, one is named Log File Adapter Configuration and the other is named Log File Adapter Global Settings.

• In the Log File Adapter Configuration tab, the following configuration items must be specified:

  • Instance Name

    Enter an identifier string that is meaningful to you to uniquely identify this instance of the agent. It is possible to run more than one instance of the agent on a particular system, each with a separate configuration. For example, you might want to monitor logs from two different applications on one system. Because each application formats its log differently, you must provide separate format files for each of them. Provide a name here that identifies which of the two applications this instance of the agent is to monitor.

  • Conf file

    Full path name to the .conf file that contains the detailed configuration options. For example, if you were previously using the Tivoli Enterprise Console log file adapter, on a UNIX system, your configuration file might be /etc/Tivoli/tecad/etc/tecad_logfile.conf, and that is the value you provide here. For more information about the .conf file, see Configuration file.

    If you use the subnode feature to create monitoring profiles, you can have more than one configuration file. If you have more than one configuration file, do not enter a path name here. See Subnodes.

  • Format file

    Full path name to the .fmt file that contains the format string patterns that you want to match in the monitored log. For example, if you were previously using the Tivoli Enterprise Console log file adapter, on a UNIX system, your format file might be /etc/Tivoli/tecad/etc/C/tecad_logfile.fmt, and that is the value you would provide here. For more information about the .fmt file, see Format file.

    If you use the subnode feature to create monitoring profiles, you can have more than one format file. If you have more than one format file, do not enter a path name here. See Subnodes.

  • Send ITM Events

    If this option is set to Yes the agent sends event data to a Tivoli Enterprise Monitoring Server, and if the option is set to No the agent does not send the event data. The setting of this option is global and applies to all monitoring profiles.

  • Send EIF Events

    If this option is set to Yes the agent sends event data directly to a receiver through EIF, and if set to No it does not send the data. The setting of this option is global and applies to all monitoring profiles.

    The EIF receiver must consume events otherwise there can be problems when the agent cache fills. For more information about buffering of EIF events in the agent cache, see The following options apply only where events are being forwarded to EIF:.

  • Automatically initialize UNIX syslog

    If this option is set to Yes on UNIX and Linux systems, the agent automatically configures the syslog facility to write a standard set of events to a pipe that the agent monitors. By enabling this setting, you can monitor syslog events without maintaining and rolling-over log files. If set to USE_CONF_FILE_VALUE, the agent checks the configuration (.conf) file for the setting (AutoInitSyslog). If not set in the configuration file, it is the same as being set to No.

    This setting is ignored on Microsoft Windows. The default value is USE_CONF_FILE_VALUE.

• In the Log File Adapter Global Settings tab, the following optional configuration items can be specified:

  • Process Priority Class

    This setting is the operating system scheduler priority for the process. A is lowest, C is the operating system default, and F is the highest priority. The setting is one of the following values: A, B, C, D, E, F, "USE_CONF_FILE_VALUE". The default setting is USE_CONF_FILE_VALUE. This setting is associated with the CPU throttling feature.

  • Process maximum CPU percentage

    This setting is the maximum allowable percentage of all system CPU that the agent can use over a 1-minute interval. Valid values are from 5 - 100. The default value is 100. This setting is associated with the CPU throttling feature. If you specify a value less than 5, the minimum value of 5 is used.

  • Configuration file autodiscovery directory

    This setting is a string value that sets the point of the file system directory tree to scan for autodiscovery of configuration (.conf) files. There must be a format (.fmt) file with the same base name in the same location. A monitoring profile is created for each such pair of files found. The default setting is ${CANDLE_HOME}/config/lo. This setting is associated with the subnodes (monitoring profiles) feature. Only one directory path can be specified, you cannot for example enter multiple directory paths separated by commas.

    To avoid impacting system resources, do not set this path at too high a level in your directory tree. The agent searches recursively from the point specified. For example, if you set the path to / the agent attempts to search your entire file system every minute.

Not using a Tivoli Enterprise Monitoring Server

• On the Configuration panel described previously, set the Send ITM Events option to No.

  On non-Windows systems, the Manage Tivoli Enterprise Monitoring Services interface also provides a panel for configuring the connection to a Tivoli Enterprise Monitoring Server. The panel has a check box labeled No TEMS. Select this option, and the TEMS Hostname field is disabled.

Parent topic:

Agent-specific installation and configuration

Related concepts:

CPU throttling
Subnodes

Related tasks:

Forwarding events to Tivoli Netcool OMNIbus ObjectServers
Configure from the command line

Related reference:

Configuration Files

---

+

Search Tips   |   Advanced Search