Adrian Cole

You may also have noticed language compiler docs aren't well written or written for backend stuff. wazero is starting to compile our notes here https://wazero.io/languages/ We also cut our first...

This field is too important to be relegated to a tag, and even if it weren't, the opentracing peer convention is not widely used and not consistently either. You should...

PS if it helps, here's our dependency linker code, which covers a bunch of edge cases as well. For example, people making circular links etc. https://github.com/openzipkin/zipkin/blob/master/zipkin/src/main/java/zipkin2/internal/DependencyLinker.java https://github.com/openzipkin/zipkin/blob/master/zipkin/src/test/java/zipkin2/internal/DependencyLinkerTest.java Since haystack data...

> > My concern in putting remoteServiceName in data model is about ownership > and uniformity. I will illustrate this with an example of two services A > calling B....

yep: the key here will be likely a decision of.. span.serviceName and span.tags[] where key = "peer.service" * nested query and only valid in opentracing, not zipkin, census, etc vs...

at least in java, stack trace is expensive to attain. Also different backends accept different data, so adding that overhead might be in vain. Best I can muster is to...

> > I was thinking about holding string stack trace rather than a reference to > the exception object. We will be serializing exceptions anyway for ocd and > for...

so ways to proceed could be to survey the tracing (and metrics!) consumers of exceptions, how they process and store things today. If any would be able to consume a...

(and logging and whatever other apis that census wants to have apis for)

> Wasm functions can return multiple values now. Yep, but that isn't a part of a REC spec. Right now, [2.0 which supports that is still a draft](https://webassembly.github.io/spec/core/intro/introduction.html). It doesn't...