We need to watch requests/failures through response to the client. We've determined that using a uniquely generated correlation id is best.
As an entry point to one or more API's, our .NET Web API 2 application receives requests via IIS 7+. To track a request (whether it failed OR succeeded), we need for the IIS log files to include unique GUID (assuming an ActivityID). We know once we are within the Web API, we can gather the ActivityId from CorrelationManager.ActivityId but at the host/server level, we need this to be reported.
... For all requests, successful or failed, how do we get IIS to start with including its own unique correlation identifier in logs it touches?