Nightfall
Last updated
Was this helpful?
Last updated
Was this helpful?
The Nightfall filter scans logs for sensitive data and redacts any sensitive portions. This filter supports scanning for various sensitive information, ranging from API keys and Personally Identifiable Information (PII) to custom regular expressions you define. You can configure what to scan for in the.
This filter isn't enabled by default in version 1.9.0 due to a typo. To enable it,
set the flag -DFLB_FILTER_NIGHTFALL=ON
when building. This is fixed for
versions 1.9.1 and later.
The plugin supports the following configuration parameters:
nightfall_api_key
none
policy_id
none
sampling_rate
The rate controlling how much of your logs you wish to be scanned. Must be a float between (0,1]
. 1
means all logs will be scanned. Use this setting to avoid rate limits in conjunction with Fluent Bit match rules.
1
tls.debug
Debug level between 0
(nothing) and 4
(every detail).
0
tls.verify
When enabled, turns on certificate validation when connecting to the Nightfall API.
true
tls.ca_path
Absolute path to root certificates, required if tls.verify
is true.
none
The following is an example of a configuration file for the Nightfall filter:
After you configure the filter, you can use the it from the command line by running a command like:
Replace PATH_TO_CONF_FILE
with the path for where your filter configuration file
is located.
Which results in output like:
The Nightfall API key to scan your logs with, obtainable from the
The Nightfall developer platform policy to scan your logs with, configurable in the .