rec: do not use "message" as key, it has a special meaning to systemd-journal

Fixes #12466

A more fundamental approach would be to make sure to not use keys that
have special meaning to systemd-journal in the structured logging backend code.

diff --git a/pdns/recursordist/secpoll-recursor.cc b/pdns/recursordist/secpoll-recursor.cc
index 91774af85cf5aeabb167a91571ed58b310db2659..0c8d7b869edf1b023d01583ded171fc1452929c9 100644 (file)
--- a/pdns/recursordist/secpoll-recursor.cc
+++ b/pdns/recursordist/secpoll-recursor.cc
@@ -85,7 +85,7 @@ void doSecPoll(time_t* last_secpoll, Logr::log_t log)
 
   g_security_message = security_message;
 
-  auto rlog = vlog->withValues("message", Logging::Loggable(g_security_message), "status", Logging::Loggable(security_status));
+  auto rlog = vlog->withValues("securitymessage", Logging::Loggable(g_security_message), "status", Logging::Loggable(security_status));
   if (g_security_status != 1 && security_status == 1) {
     SLOG(g_log << Logger::Warning << "Polled security status of version " << pkgv << ", no known issues reported: " << g_security_message << endl,
          rlog->info(Logr::Notice, "Polled security status of version, no known issues reported"));