Linux-UNIX: Discovery parameters
The discovery parameters define the behavior of the auto-discovery feature, for discovering database instances and sending the results to the current active S-TAP.
Attention: These are advanced parameters and should be
modified only by IBM Technical Support.
GIM | guard_tap.ini | Default value | Description |
---|---|---|---|
STAP_DISCOVERY_INTERVAL | discovery_interval | 24 | The time interval at which auto-discovery runs. Valid values:
|
STAP_DISCOVERY_DBS | discovery_dbs | oracle:db2:informix:mysql:postgres:sybase:hadoop:teradata:netezza:memsql | Colon (':') separated list of database types to attempt to discover. Can be set when pushing to a group of DB servers via GIM. |
STAP_DISCOVERY_DEBUG | discovery_debug | 0 | Output debug information from discovery. The log is
guard_discovery.stderr.log located in the directory specified by the parameter
tap_log_dir (by default: /tmp/guard_stap).
Can be set when pushing to a group of DB servers via GIM. |
STAP_DISCOVERY_ORA_ALT_LOCATIONS | discovery_ora_alt_locations | Alternate locations to look for listener.ora files. Can be set when pushing to a group of DB servers via GIM. |
|
STAP_DISCOVERY_ORA_USE_PORT_RANGES | discovery_ora_use_port_ranges | 0 | Enable
S-TAP
discovery of Oracle databases to combine discovered instances based on port ranges. This setting
works with a single unix_domain_socket_marker. Multiple
unix_domain_socket_marker configurations require separate
instances. Valid values:
|
STAP_DISCOVERY_PORT | discovery_port | 8443 | S-TAP Discovery uses this port to connect to the Guardium® system. |