Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expose WebJob Context Information To Custom TraceWriters
See original GitHub issueIn an attempt to make reviewing/querying WebJob logs easier, I took advantage of the JobHostConfiguration.Tracing.Tracers collection and added a custom SqlTraceWriter to my WebJob project (sample code here).
This works pretty well but can get somewhat confusing due to WebJobs being executed in parallel.
Would it be possible to expose some of the WebJob Context information to the TraceWriter?
Either via a static class or by passing it into the TraceWriter.Trace() method perhaps?
The various *InstanceIds could be added to the SQL Table to help identify logs from the same job.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
TraceEvent.Propertieswill now include function information – available properties found here: https://github.com/Azure/azure-webjobs-sdk/blob/master/src/Microsoft.Azure.WebJobs.Host/Loggers/TraceEventExtensions.cs@brettsam can get it up on our myget feed for you to access. We won’t be doing nuget.org update for a while.