Chapter 10. Using Collector runtime configuration
You can use the Collector runtime configuration to modify some collector behaviors without restarting Collector. Set the Collector runtime configuration by using a ConfigMap object called collector-config. When you create or update the ConfigMap object, Collector refreshes the runtime configuration. When you delete the ConfigMap object, the settings revert to the default runtime configuration values.
You can control the following settings using the Collector runtime configuration:
-
networking.externalIps.enabledcontrols if the visualizing external entities feature is enabled or disabled. The default isDISABLED. In release 4.6, this setting wasnetworking.externalIps.enableand was a boolean. For more information, see Visualizing external entities. -
networking.externalIps.directionspecifies the direction for collecting external IPs. The values areINGRESS,EGRESS, orBOTH(default). For example, when you selectEGRESSit provides details for all outgoing connections while aggregating the incoming ones. -
networking.maxConnectionsPerMinuteis the maximum number of open networking connections reported by Collector per container per minute. The default value is 2048.
The following example enables the visualizing external entities for outgoing connections only and sets maxConnectionsPerMinute to 2048.
apiVersion: v1
kind: ConfigMap
metadata:
name: collector-config
namespace: stackrox
data:
runtime_config.yaml: |
networking:
externalIps:
enabled: ENABLED
direction: EGRESS
maxConnectionsPerMinute: 2048
where:
data.runtime_config.yaml-
Specifies whether RHACS mounts this file at
/etc/stackrox/runtime_config.yaml. data.runtime_config.yaml.networking.externalIps.direction-
Specifies whether to collect ingress connections, egress connections, or both. If you do not specify a value, it defaults to
BOTH.