Appendix B. Options for the redaction configuration file
The configuration file /etc/insights-client/remove.conf controls how the Insights for Red Hat Enterprise Linux client redacts data.
As of RHEL RHEL 6.10, 7.9, 8.3 and later, using remove.conf is deprecated and replaced by two YAML files.
The Insights client performs redaction on the archive file based on the information in remove.conf. Most redaction activity occurs before the archive file is generated and sent to the Red Hat Insights for Red Hat Enterprise Linux service.
B.1. Options for the Insights client redaction file
File name and location
The suggested name is /etc/insights-client/remove.conf for the redaction configuration file. You must have root permission in order to create this file. It is not created automatically as part of the Insights client deployment.
The /etc/insights-client/insights-client.conf configuration file specifies the name and location of the redaction configuration file.
File template for remove.conf
The following is an example template for the remove.conf file:
[remove] files=/etc/cluster/cluster.conf,/etc/hosts commands=/bin/dmesg,/bin/hostname patterns=password,username keywords=super$ecret,ultra$ecret+
- A single comma with no space separates each entered value.
- Do not include the line for data you do not want redacted.
-
Regular expressions and wildcard matching (
egrep) are not supported. - All entries are case-sensitive.
| Option | Description |
|---|---|
|
|
This must be the first line of the |
|
| The listed files are excluded from data collecting. |
|
| The output from commands listed here is excluded from data collecting. The command names must exactly match the command names in the collection rules. |
|
| Any line in the archive file that matches all or part of a pattern is deleted. |
|
|
The keyword is replaced with an actual value of
For example, if you define two keywords, |
