Morgan McLean

Yep, this is the equivalent to #151 for clients. I agree about not wanting clients to make the sampling decision, as client-only traces have very little value. _However_, we do...

Did we end up implementing this or is it still under discussion. If it's still under discussion, then I suspect that the simplest method of achieving this is through a...

I see your point, but feel like there's still a need to remove certain endpoints. For example, seeing traces of Profiler requests to Stackdriver drive me nuts: they're high latency...

That's right, sorry! I'll create a separate issue

+1 for making the default behavior to drop spans and reduce functionality rather than slow down the host app

@c24t @dinooliva @SergeyKanzhelev @bogdandrutu FYI For HTTP we have the W3C spec, but you're correct that in other formats things are less clear. For example, @SergeyKanzhelev is looking into formats...

Yes, though we don't have a formal design ready. We (Google) have a new member joining our team in a few weeks who will be picking this up.

The majority of complaints that have been relayed to me are about metrics. There are a few things that I think we can do: - Reduce the number of metrics...

Cool! This is very much along the same thinking that we (Google, others) have had with TraceContext (as @mabn and @yurishukro pointed out, and which we just posted an update...

+1 for common binary ingestion and context formats, etc.