From 9fc93a9f6e5a42fec04e41d8770979dcc755a05e Mon Sep 17 00:00:00 2001 From: brodowski Date: Fri, 31 Jul 2026 10:56:37 +0000 Subject: [PATCH] featurecontrol: log auto-gomemlimit activation at INFO auto-gomemlimit is not experimental in effect: it is how the Go heap learns about a container memory limit, and running without it inside a limited container is the worse choice. Logging its activation at WARN announces the safer configuration as a caution, so a deliberately configured start-up emits a warning line with nothing wrong. Log that one activation at INFO. Every other branch is left at WARN, including the unbounded-cardinality metrics flags, whose message does carry an operational caution. The message text is unchanged. Fixes #5412 Signed-off-by: brodowski --- featurecontrol/featurecontrol.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/featurecontrol/featurecontrol.go b/featurecontrol/featurecontrol.go index 3b5e65680d..32168a7e1a 100644 --- a/featurecontrol/featurecontrol.go +++ b/featurecontrol/featurecontrol.go @@ -160,7 +160,7 @@ func NewFlags(logger *slog.Logger, features string) (Flagger, error) { logger.Warn("UTF-8 strict mode enabled") case FeatureAutoGOMEMLIMIT: opts = append(opts, enableAutoGOMEMLIMIT()) - logger.Warn("Automatically set GOMEMLIMIT to match the Linux container or system memory limit.") + logger.Info("Automatically set GOMEMLIMIT to match the Linux container or system memory limit.") case FeatureEventRecorder: opts = append(opts, enableEventRecorder()) logger.Warn("Experimental event recorder enabled")