From 94b86ef11acf8844ae7037b44ba67a6c56c37d23 Mon Sep 17 00:00:00 2001 From: Michael Panzlaff Date: Wed, 14 Jan 2026 16:06:35 +0100 Subject: [PATCH] Mismatched event types are not something to be concerned about If a different CCMessage type was sent over the same subject as requested, that shouldn't raise a warning. This may happen in production instances, but in order to ease debugging, lower it to 'debug' level. --- internal/api/nats.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/api/nats.go b/internal/api/nats.go index 48c6449b..9fdfbbb2 100644 --- a/internal/api/nats.go +++ b/internal/api/nats.go @@ -152,14 +152,14 @@ func (api *NatsAPI) handleJobEvent(subject string, data []byte) { } if !m.IsEvent() { - cclog.Warnf("NATS %s: received non-event message, skipping", subject) + cclog.Debugf("NATS %s: received non-event message, skipping", subject) continue } if m.Name() == "job" { api.processJobEvent(m) } else { - cclog.Warnf("NATS %s: unexpected measurement name '%s', expected 'job'", subject, m.Name()) + cclog.Debugf("NATS %s: unexpected measurement name '%s', expected 'job'", subject, m.Name()) } } }