3 ms·

I didn't really get this. Spans in other frameworks are already DAGs; and easy to reason about them as such. Sounds like they just made the API "more generic"

I didn't really get this. Spans in other frameworks are already DAGs; and easy to reason about them as such. Sounds like they just made the API "more generic" by removing request oriented nomenclature ?

solumos 6y ago
Agreed - this definitely has some "Not Invented Here" baked into it. Seems like they didn't like some of the nomenclature associated with Jaeger/Zipkin, even though both are pretty extensible . . . > In the future, we plan to build on this success by adding a more powerful query language for querying trace data. Now they just need a custom DSL!
mansu1 6y ago
Post author here. Yes, existing span formats also represent DAGs. But there are additional details in the spans, that trip up developers. Also, most developers don't think about using spans to represent DAGs in their applications Regular Span - Annotations(nested structures) = SpanEvent. Yes, we made the API much more simpler. As a result you can consume the spans in the format you produce them.