filetrace config works with the configuration file: show prints every setting with the value in effect, validate checks a file and reports what is wrong with it, and path prints which file is read. It reads the file itself and does not need a running agent.
Usage
Which file is read
The file is/etc/filetrace/config.toml, or $FILETRACE_CONFIG, or the one named with the global option --config, which config also accepts after its action. The agent reads the file when it starts, and its own command-line options override it. The other commands take their default output format, [output] format, and the socket to reach the agent on, [agent] socket, from it.
If the default file, or the one $FILETRACE_CONFIG names, does not exist, the built-in defaults apply. A file named with --config must exist.
A setting that asks for something this build cannot do, such as [storage] enabled = true, is reported as a warning and ignored. An unknown setting or a value of the wrong kind is an error. Configuration file reference describes every setting.
show
config show prints every setting in the format of the configuration file, preceded by a comment that says where the values come from. Without a file, these are the defaults:
[file], [correlation], [storage], [limits], [output], [filters], [prometheus], [otlp] and [grpc] sections. With a file, the first line names it:
validate
config validate checks a file without starting anything. Without a file argument, it checks the file that would be read.
path
config path prints the path of the file that would be read, whether or not it exists:
Options
string
default:"/etc/filetrace/config.toml"
The configuration file to show, validate or locate. Accepted before
config, as a global option, or after the action. A file argument of validate overrides the global option.