From 5da8990053e2c87eaf837da61cd63e687c43aae0 Mon Sep 17 00:00:00 2001 From: Brian Brazil Date: Fri, 6 Mar 2020 00:46:03 +0000 Subject: [PATCH] Log scrape append failures as debug rather than warn. (#6852) This is most likely due to an endpoint not producing valid metrics output, which we should treat the same as a failed scrape, and thus not spam the application logs with it. Signed-off-by: Brian Brazil --- scrape/scrape.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scrape/scrape.go b/scrape/scrape.go index 3c33900bc..e0077e9fa 100644 --- a/scrape/scrape.go +++ b/scrape/scrape.go @@ -965,7 +965,7 @@ mainLoop: // we still call sl.append to trigger stale markers. total, added, seriesAdded, appErr := sl.append(b, contentType, start) if appErr != nil { - level.Warn(sl.l).Log("msg", "append failed", "err", appErr) + level.Debug(sl.l).Log("msg", "append failed", "err", appErr) // The append failed, probably due to a parse error or sample limit. // Call sl.append again with an empty scrape to trigger stale markers. if _, _, _, err := sl.append([]byte{}, "", start); err != nil {