-
Notifications
You must be signed in to change notification settings - Fork 274
Default Throttle Logging #1
Comments
Here is a possible example of what I envision it could look like:
|
Hello Craig, I don't want to create more dependencies for WebApiThrottle by adding WebApi.Tracing reference. Your ITraceWriter implementation is best suited in the Demo project, I will provide there an working example and I will update the documentation accordingly. Thanks for your feedback, I appreciate it. |
What do you think about instead of using ITraceWriter, using System.Diagnostics.Trace instead? I have a Trace Listener that forwards messages from the trace to my logging framework. This might accomplish my desire to not have to create/manage a throttle logger implementation and not introduce a dependency to the package. |
Seems that ITraceWriter doesn't need a reference to System.Web.Http.Tracing, this interface is part of System.Web.Http. I think that the TracingThrottleLogger you've added covers all logging needs. |
What kind of timeframe is there on the publish to NuGet? On Dec 18, 2013, at 11:11 AM, Stefan Prodan <notifications@github.commailto:notifications@github.com> wrote: Seems that ITraceWriter doesn't need a reference to System.Web.Http.Tracing, this interface is part of System.Web.Http. I think that the TracingThrottleLogger you've added covers all logging needs. — |
I have a TeamCity server that deploys to Nuget, it's running now. |
Provide a default implementation of the IThrottleLogger that logs to Diagnostic Trace or provide a default implementation of the ITraceWriter. This will allow the throttle messages to dump straight to the logging pipeline that might already be in place.
The text was updated successfully, but these errors were encountered: