Files
securityonion/salt
Josh Patterson 52fc0cb828 Expose Logstash log.level and log.format in SOC
The Logstash log level was hardcoded to info in log4j2.properties, and
logstash.yml carried no log.level key, so the only way to raise verbosity
for troubleshooting was to hand-edit a file that the next highstate
overwrites. Add log_x_level and log_x_format to logstash:config so both
render into logstash.yml, annotated as advanced per-node settings with
the value sets Logstash 9.3.7 accepts.

log4j2.properties gains jinja, so it moves to log4j2.properties.jinja and
is rendered by a discrete lslog4j2 state rather than the lsetcsync
recurse, which cannot rename. The recurse exclude_pat now matches both
names so it neither copies the template verbatim nor lets clean: True
delete the rendered file, matching how pipelines.yml is already handled.

The appender layout is selected at render time so log.format actually
changes the log output instead of being a dead setting, keeping the
existing file name so nothing downstream moves. rootLogger.level now
follows ls.log.level rather than claiming info regardless of the
configured level.
2026-08-21 09:47:09 -04:00
..
2025-12-02 11:16:08 -06:00
2026-08-14 13:54:14 -04:00
2025-12-11 17:30:06 -05:00
2025-12-02 11:16:08 -06:00
2026-07-15 16:28:35 -04:00
2026-08-03 15:19:18 -04:00
2026-03-19 14:39:10 -04:00
2026-08-20 09:31:56 -04:00
2026-01-07 14:14:57 -05:00
2025-10-14 11:03:00 -04:00
2025-08-04 15:25:26 -04:00
2026-08-14 16:04:48 -04:00