Map debug level to info

As the comment states, openbmc currently squashes DEBUG level messages.
After ee993dc systemd can see the log
levels, which has the unintended consequence of squashing DEBUG level
messages when enabled.

This is a temporary workaround to fix the regression.  Ulimately
implementing something like DEBUG_INVOCATION might be the way to go.

Tested: Enabled debug logging

journalctl -u bmcweb showed debug level messages.

Change-Id: I3c57a47282dbcbf34c58a12d2b7da54f1082fac1
Signed-off-by: Ed Tanous <[email protected]>

Author: edtanous

http/logging.hpp

@@ -55,7 +55,10 @@ constexpr int toSystemdLevel(LogLevel level)
          {LogLevel::Warning, 4},
          // NOTICE 5
          {LogLevel::Info, 6},
-         {LogLevel::Debug, 7}}};
+         // Note, debug here is actually mapped to info level, because OpenBMC
+         // has a MaxLevelSyslog and MaxLevelStore of info, so DEBUG level will
+         // never be stored.
+         {LogLevel::Debug, 6}}};
 
     const auto* it = std::ranges::find_if(
         mapping, [level](const std::pair<LogLevel, int>& elem) {
@@ -65,7 +68,7 @@ constexpr int toSystemdLevel(LogLevel level)
     // Unknown log level.  Just assume debug
     if (it != mapping.end())
     {
-        return 7;
+        return 6;
     }
 
     return it->second;