From 35137b63f5d3b4d9dcabe9dbcdc8dc339e1f4231 Mon Sep 17 00:00:00 2001 From: Will Baker Date: Fri, 4 Oct 2024 14:50:25 -0400 Subject: [PATCH] materialize: adjust loggers to use reasonable frequencies The 5 second and 15 second frequencies were just for testing, and the real values should be in minutes. --- materialize-boilerplate/logging.go | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/materialize-boilerplate/logging.go b/materialize-boilerplate/logging.go index ad9e8dfff..1ae69136e 100644 --- a/materialize-boilerplate/logging.go +++ b/materialize-boilerplate/logging.go @@ -9,13 +9,18 @@ import ( ) const ( - // How often various the various async loggers will report their status. - loggingFrequency = 5 * time.Second + // How often the various async loggers will report their status. When + // "extended" logging is enabled, transitions of interest will always be + // logged immediately, and only after loggingFrequency will status updates + // be logged if nothing else has happened. When extended logging is not + // enabled, there will be a more generic status update logged out at this + // frequency. + loggingFrequency = 5 * time.Minute // When the "basic" logger is being used, how long a commit must be in // progress or how long the connector must be waiting for documents from the // runtime before it logs something about that. - slowOperationThreshold = 15 * time.Second + slowOperationThreshold = 15 * time.Minute ) // loggerAtLevel wraps a logrus logger to always log at the configured level.