Ash Insights integration

[rabidpraxis]

No description provided.

[joshuap]

I took a look at this and compared the data that @rabidpraxis is getting from the telemetry ash.*.stop events to the data I was getting from the tracer implementation that I worked on with @joshprice (which currently sends two events instead of one). Is the tracer providing any extra info that we'd miss with telemetry?

Also (more a question for @rabidpraxis), I'm wondering if it would be useful in the future to have the parent/span ids (this may also be what the correlation id—which we added—was trying to do). :) I believe the span and parent ids in the tracer events come from Ash directly.

In either case, I think we'd still want to emit a single event per operation (instead of start/stop events).

Ash telemetry event

Ash tracer events

Start:

End: