A Giant Leap For Span.Kind
At Embrace, we've been excited about meeting and growing the OpenTelemetry specification for some time now. We also have a ton of domain-specific knowledge about how mobile telemetry should be collected and processed. This led to a decision point while rebuilding our mobile SDKs to emit OpenTelemetry primitives: how can we quickly inform the data ingest layer about the types of telemetry we're sending, to make its life easier?