Agent.cfg - basic options

The Agent.cfg file contains the following basic options for configuration:

Basic options for agent configuration file

Option and default value

Description

CONTACT_MANAGING_NODE = 1

Agent contacting the managing node for alerts and notification. Options are:

  • 1 (contact managing node)
  • 0 (do not contact managing node)

SEND_EMAIL_AFTER_COLLECT_ END = 1

Agent sending a message at the end of collection request. Options are:

  • 1 (send email)
  • 0 (do not send email)

ENABLE_UMX_COLLECTION = 0

Enable UMX collection. Options are:

  • 0 (UMX collection disabled)
  • 1 (UMX collection enabled)

ENABLE_SCRIPT_ACTION = 0

Enable script actions. Options are:

  • 0 (script actions disabled)
  • 1 (script actions enabled)

ENABLE_SNMP_ACTION = 1

Enable SNMP trap actions. Options are:

  • 1 (SNMP trap actions enabled)
  • 0 (SNMP trap actions disabled)

ENABLE_EMAIL_ACTION = 1

Enable email actions. Options are:

  • 1 (email actions enabled)
  • 0 (email actions disabled)

UDR_CORRUPT_FILE_ BACKUP= 0

Use this option to control how corrupted UDR files are backed up. Options are:

  • 0 (remove the file)
  • 1 (back up the file)

UDR_CORRUPT_FILE_ REPAIR= 0

Use this option to enable automatic repair of the UDR file when the agent starts. Options are:

  • 0 (no repair)
  • 1 (agent will automatically repair the file)

UDR_CORRUPT_FILE_LOG_ EVENT= 0

Applies to Windows platforms only, use this option to control how corrupted UDR file events are recoreded.

  • 0 (do not record the event)
  • 1 (record the event in the Windows event log)

UDR_CORRUPT_FILE_NOTIFY_ USER= email_address

Use this option to specify the email address of the person you want notified in the event that the UDR file is corrupted. The default is no email generated.

UDR_TIME_BASED_SUMMARIZATION = 1

UDR time-based summarization option. Options are:

  • 0 (sample count based summarization)
  • 1 (time-based summarization)

AGENT_LOG_FILE_MAX_ LINES=500

The maximum number of lines in the agent log file. The default is 500.

On Windows systems, log files remain open if you use this option. Using this option speeds up response time by eliminating open, write, and close actions for each log file entry.

AGENT_LOG_WARNING_ LEVEL=0

The error level associated with the agent log file. Options are:

  • 0 (Error)
  • 1 (Warning)
  • 2 (Debug)

COLLECT_LOG_FILE_MAX_ LINES=500

The maximum number of lines in the Collect log file. The default is 500.

On Windows systems, log files remain open if you use this option. Using this option speeds up response time by eliminating open, write, and close actions for each log file entry.

COLLECT_LOG_WARNING_ LEVEL=0

The error level associated with the Collect log file. Options are:

  • 0 (Error)
  • 1 (Warning)
  • 2 (Debug)

SERVICEDAEMON_LOG_FILE_ MAX_SIZE=65536

The maximum size, in bytes, of the log file for service daemon applications (bgs_sdservice, bgssd, best1collect ). The default is 65536.

On Windows systems, log files remain open if you use this option. Using this option speeds up response time by eliminating open, write, and close actions for each log file entry.

SERVICEDAEMON_LOG_FILE_ MAX_LINES=0

The maximum number of lines in the service daemon log file. The default is 0.

On Windows systems, log files remain open if you use this option. Using this option speeds up response time by eliminating open, write, and close actions for each log file entry.

SERVICEDAEMON_LOG_ WARNING_LEVEL=0

The error level associated with the service daemon log file. Options are:

  • 0 (Error)
  • 1 (Warning)
  • 2 (Debug)

SEMAPHORE_FILE_PERMISSION = S_IRUSR|S_IWUSR|S_IRGRP| S_IWGRP|S_IROTH|S_IWOTH

(UNIX only) The access permissions of the semaphore files located in the monitor/tmp directory. These files are used for memory mapped files and locks and for shared memory keys and semaphore lock keys.

For definitions of these settings, see Agent.cfg - permissions for UNIX.

SHARED_MEMORY_ PERMISSION = S_IRUSR|S_IWUSR|S_IRGRP| S_IWGRP|S_IROTH|S_IWOTH

(UNIX only) The access permissions of the shared memory segments.

Note: If you change this default setting you must restart the b1mgrdmon, bgsagent, and the Perform collector in order for the new setting to take effect. Note also that a single shared memory segment and semaphore created by b1mgrdmon will not be changed. This segment must stay world readable to accommodate multiple Investigate alert users. There is no exposure in having this segment world viewable, because the information contained is a policy name and pipe number association.

For definitions of these settings, see Agent.cfg - permissions for UNIX.

Was this page helpful? Yes No Submitting... Thank you

Comments