-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OtelExporter does not export Span Marks #1047
Comments
Did a quick check of the OTEL data model with respect to events. The event data model states
I'm assuming something in the lines of this would be the correct translation. private[otel] def toProtoEvent(mark:Span.Mark):ProtoSpan.Event = {
ProtoSpan.Event.newBuilder()
.setName(mark.key)
.setTimeUnixNano(toEpocNano(mark.instant))
.build()
} |
As for your company having a policy dictating you're not allowed to provide a PR I'd say it's a really crappy policy. I'm not affiliated with Kamon in any way more than having written a few tickets and provided a few PR's. |
I've added PR, @vishramachandran have a check and see if it's correctly mapped from Mark to Event |
@pnerg Looks great. Thanks much for taking the time. The restrictions in my company are legal barriers to ensure that copyright and trade secrets are not leaked. There is an approval process I need to go through for each repo, and it takes a while. As much as I would like to voice my opinion and discuss whether this is good or not, this is not the forum to do that, and I would like to respectfully bow out of that discussion. |
added missing span marks to otel exporter #1047
Fixed with v2.2.2. |
Thanks for adding the new OpenTelemetry exporter.
I was testing it for our use, and found that it does not propagate Kamon span's
Mark
events as OTel spanEvent
objects.This is an easy change. I would have sent a PR out, but I am restricted by my employer. Could this easy fix go in soon?
Backport into 2.1 release would be immensely useful. 🙏
cc @SimunKaracic @pnerg
The text was updated successfully, but these errors were encountered: