The basic issue is that for longer requests, the Splunk logger is not logging the HTTP headers.
We are using the splunk-1.5.0.0.jar and splunk-library-javalogging-1.5.2.jar -- https://github.com/splunk/splunk-library-javalogging. We are using log4j to push HTTP SOAP requests and responses to Splunk. The application itself is a very basic proxy running on Mule CE 3.8.1 – it simply wraps Soap calls and logs the request and responses. We add several custom headers that are critical to see in the logs.
We find when the requests are long, Splunk is not logging the headers. We know the headers are present because they do appear in the response log. HTTP Headers seem to always be present in the logged responses no matter the length. For small request bodies, the headers appear in the splunk logs correctly.
Is there a way to force Splunk to log the HTTP headers without regard to the request length? A trimmed example of what we see in the log is below.
10/9/17
8:23:34.572 AM
{ [-]
logger: org.mule.module.http.internal.HttpMessageLogger
message: LISTENER
severity: DEBUG
thread: [dmvproxy-1.0.0-SNAPSHOT].HTTP_Listener_Configuration.worker.43
}
Show as raw text
↧