1

Closed

HttpResponseException should not trace as Error

description

The tracing layer currently uses TraceLevel.Error for all exceptions thrown or associated with faulted tasks. This means simple client errors such as misspelled controller names will generate Error traces, defeating attempts to use tracing for general error reporting (e.g. ELMAH).

The tracing layer should be modified to trace at Warn level whenever an HttpResponseException is observed. Moreover, it should also update TraceRecord.Status whenever it finds HttpResponseException.
Closed Mar 25 at 11:33 PM by HongmeiG
I think it is ok to trace exception as Error, including HttpResponseException.

comments

HongmeiG wrote Aug 11, 2012 at 12:51 AM

If the httpresponseexception's response is 500, we should trace it as error; otherwise, we can trace it as warning.