13/03/2024 14:51:55.178 Log_Level=INFO Process=list-recon-preprod-mesh-fetch-message-chunk internalID=20240313145151643530_297F8A logReference=MESHMBOX0006 - Acknowledging message_id='{message_id}' http_status='{http_status}' - No substitution due to KeyError, missing keys: ['http_status'], dictionary of {'message_id': '20240313145122009567_4818F3', 'internalID': 'NotProvided', 'sessionid': 'NotProvided'}
Because the definition of MESHMBOX0006 in src/cloudlogbase.cfg has an http_status placeholder, but the logger is not providing it.
Suspect this is not an issue for most people, but is a distracting noise when tracing with Splunk. I think it will be simplest/easiest to just remove the http_status from the log template.
We see logs like this in Splunk Cloud:
Because the definition of
MESHMBOX0006insrc/cloudlogbase.cfghas anhttp_statusplaceholder, but the logger is not providing it.Suspect this is not an issue for most people, but is a distracting noise when tracing with Splunk. I think it will be simplest/easiest to just remove the
http_statusfrom the log template.I will submit a PR.