Adrian Cole

in brave we have an unmerged on account of not enough popularity "localRoot" thing which would allow consistent squashing of intermediate spans. We also have a completion hook which allows...

agree

yes we also used this in testing aggregation techniques with expedia haystack/adaptive alerting last week. in cases where you want to reduce volume to just remote spans this can be...

FWIW the reason we said localRoot is to imply this isnt likely useful in remote (propagated) contexts. so it is a library concern but not likely in scope for headers...

so your question is whether to add more scope than the id? specifically names are problematic as they change over time where the id does not. That said, I wonder...

hi Sergey. having implemented this feature I can assure there is zero api surface area. the first entry is implicit and can be done internal to the tracer. in brave...

I think the target is exporters not end users. I don't expect end users to employ this data. it could seem fine to wait for more people to ask here...

To make a design that does this in the Span, assumes the context in process is tightly coupled with the span anyway (a single object w/1-1 relationship). It also assumes...

by the way, this is actively desired by zipkin users. I'm not sure why people are theoretical about this. It exists in multiple APMs systems and there seems to be...

Meanwhile here's a workaround thanks to @nacx for the help. Somewhere, you define your embedded reference ```go //go:embed migrations/sqlite/* var migrations embed.FS const migrationPath = "migrations/sqlite" ``` Somewhere else, you...