zuul, nodepool fb loggers: increase timestamp precision

The default timestamp precision is up to the second. Increase precision to nanosecond. Change-Id: Ieb7549d5c86be25f2ba892fe99684c078a844fe7
softwarefactory-project · Oct 16, 2024 · 00243db · 00243db
1 parent ca94665
commit 00243db
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 0 deletions.
diff --git a/controllers/static/nodepool/logging.yaml.tmpl b/controllers/static/nodepool/logging.yaml.tmpl
@@ -28,6 +28,7 @@ handlers:
     host: {{ .LoggingParams.ForwardInputConfig.Host }}
     port: {{ .LoggingParams.ForwardInputConfig.Port }}
     tag: {{ .LoggingParams.Tag }}
+    nanosecond_precision: True
 {{ end }}
 loggers:
   nodepool:

diff --git a/controllers/static/zuul/logging.yaml.tmpl b/controllers/static/zuul/logging.yaml.tmpl
@@ -28,6 +28,7 @@ handlers:
     host: {{ .LoggingParams.ForwardInputConfig.Host }}
     port: {{ .LoggingParams.ForwardInputConfig.Port }}
     tag: {{ .LoggingParams.Tag }}
+    nanosecond_precision: True
 {{ end }}
 loggers:
   zuul.GerritConnection.ssh:

diff --git a/doc/reference/CHANGELOG.md b/doc/reference/CHANGELOG.md
@@ -12,6 +12,8 @@ All notable changes to this project will be documented in this file.
 ### Changed
 ### Fixed
 
+- log forwarding - nodepool and zuul logs were being stamped with a low precision (to the second), making verbose
+  deployments hard to exploit. Logs forwarded with the python-fluent-logger library use the "nanosecond_precision" setting.
 - logserver not restarted when zuul-ssh-key change
 
 ### Security