Skip to content

Commit

Permalink
materialize: adjust loggers to use reasonable frequencies
Browse files Browse the repository at this point in the history
The 5 second and 15 second frequencies were just for testing, and the real
values should be in minutes.
  • Loading branch information
williamhbaker committed Oct 8, 2024
1 parent 391080d commit 35137b6
Showing 1 changed file with 8 additions and 3 deletions.
11 changes: 8 additions & 3 deletions materialize-boilerplate/logging.go
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 35137b6

Please sign in to comment.