David realparadyne

Tracing with Application Insights

Application logging is ubiquitous and invaluable for troubleshooting. Structured logging enables you to log formatted messages and the data fields separately so that you can see the messages but also filter on the data fields. Tracing takes this a step further, where you can correlate many log entries together as you follow a trace of execution through an application. Traces also include additional information about the execution process, such as the sequence of calls to dependencies and how long any given call may take.

Application Insights lets you see all of this data correlated together in an application. You can search for an error log and then see in the execution flow that the log entry was added right after a failed call to another service. Or you can see that a certain web request is slower than others because it spends a lot of time on many redundant data access calls.

	type AsyncBuilder with
	member inline __.Bind(t : Task<'a>, cont) = async.Bind(t \|> Async.AwaitTask, cont)
	member inline __.Bind(t : Task, cont) = async.Bind(t \|> Async.AwaitTask, cont)
	member inline __.ReturnFrom(t : Task<'a>) = async.ReturnFrom(t \|> Async.AwaitTask)
	member inline __.ReturnFrom(t : Task) = async.ReturnFrom(t \|> Async.AwaitTask)

	member inline __.Bind(t : ValueTask<'a>, cont) = async.Bind(t.AsTask() \|> Async.AwaitTask, cont)
	member inline __.Bind(t : ValueTask, cont) = async.Bind(t.AsTask() \|> Async.AwaitTask, cont)
	member inline __.ReturnFrom(t : ValueTask<'a>) = async.ReturnFrom(t.AsTask() \|> Async.AwaitTask)
	member inline __.ReturnFrom(t : ValueTask) = async.ReturnFrom(t.AsTask() \|> Async.AwaitTask)

	namespace AddFSharpType

	module AddFSharpType =
	open System.IO
	open FSharp.Compiler.CodeAnalysis
	open System
	/// This is basically the compiler so we name it that way
	let compiler = FSharpChecker.Create()

	let AddFromFile (sourceFile : string) =

David realparadyne

Tracing with Application Insights

What about OpenTelemetry?