Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tristan Sloughter
    @tsloughter
    yes this is one of the places to discuss it, the main place would be the weekly Spec SIG meeting and github spec issues
    those have more ppl involved
    Andrew Hsu
    @andrewhsu

    Thanks to @bogdandrutu @jgals @justinfoote @mtwo @jmacd for joining the otel spec issue scrub 🧽 on Friday. We were able to triage the new issues in the spec repo. We also went over the open issues in oteps, and proto repos.

    Currently there are 3 issues identified as P1 that are not metrics related:

    In addition, we went over remaining high level GA planning items. We’ll discuss tracking these issues at the maintainers sig mtg.

    1 reply
    Ritick Gautam
    @riticksingh
    Can anyone know how to check if collector is receiving span ?
    Tristan Sloughter
    @tsloughter
    what are people doin gfor the description of a "parent bsaed" sampler?
    are you doing like ParentBased{TraceIdRatioBased{0.001.0}}? what about all the other options, maybe ParentBased{root=TraceIdRatioBased{0.001.0}, remoteParentSampled=AlwaysOn{}, ...}
    Tristan Sloughter
    @tsloughter
    Tyler Yahn
    @MrAlias
    @tsloughter in Go we pass options to the sampler to override defaults for all the different situations: https://github.com/open-telemetry/opentelemetry-go/blob/23e32b19ec227702d6f9d62b1b8aec69c075d21b/sdk/trace/sampling.go#L135-L149
    Tristan Sloughter
    @tsloughter
    Tyler Yahn
    @MrAlias
    Ah, gotcha :+1:
    John Watson
    @jkwatson
    [just musing out loud here] I wish that TraceState & TraceFlags were propagated via the Context, rather than hanging off the Span.
    Tristan Sloughter
    @tsloughter
    I may hav emissed it but while samplers have a "get description" function there isn't a way to get the sampler that is in use?
    and since samplers are in the SDK not API maybe there should be an API function like "TracerProvider.toString"? for use in logs that includes the sampler description
    Andrew Hsu
    @andrewhsu

    Friendly reminder we have otel spec issue scrub 🧽 mtg on Friday morning 8:30a PDT.

    We also have 2 outstanding P1 trace issues:

    Tristan Sloughter
    @tsloughter
    so invalid spans/span ctxs are used in place of having shit return like Maybe(Span), right?
    I'd been basically doing the "maybe span" but now as I'm updating how propagation works am moving to how others do it but don't think it is clear in the spec that is what is going on
    Tristan Sloughter
    @tsloughter
    hm, the Go impl generates a span id whether or not the span is recorded or sampled
    Tristan Sloughter
    @tsloughter
    python does too... I guess that is the expected way, will find it in the spec
    Tristan Sloughter
    @tsloughter
    the span creation spec doesn't say to generate a span id
    Tristan Sloughter
    @tsloughter
    I wasn't making a Span when Sampled was false and IsRecord was true, but it appears we do have to in order to call the Processors on it.
    Tristan Sloughter
    @tsloughter
    ah duh, others do since Span.set_attributes(Attributes) has to work even if Span isn't recorded and thus nothing is actually happening in that call
    Andrew Hsu
    @andrewhsu
    fyi i’ve created 11 new issues for high-level tracking of OTel GA related issues with label area:ga-tracking. i left out a priority label on purpose so it does not muck with reports of existing issue tracking of changes to the spec. essentially, i copied the line items from google sheet OpenTelemetry GA Planning to github project OpenTelemetry GA High Level Items so they can be tracked in github with assignees and status across linked github issues to other language SIGs. i’ll take a few minutes at the spec sig mtg tomorrow to give quick summary about these issues and how they will be tracked, but i’ll go over more detail in depth at the next maintainers meeting.
    Andrew Hsu
    @andrewhsu

    @tigrannajaryan @bogdandrutu from the topic of our last collector SIG mtg, i’m looking for a timeslot to triage the 148 collector issues. to keep friendly with european timezone, trying for early morning pacific time. i can suggest 2 windows of times:

    1. wed (nov 4) 7:30a - 8:00a PST; and/or
    2. thu (nov 5) 8:00a - 8:30a PST

    we’ll likely need several sessions to make a dent in the number of issues. do either/both of these times work? if so, i can setup a zoom call. else, propose an alternative time to work towards.

    11 replies
    Tristan Sloughter
    @tsloughter
    damn, could have swore everything was an hour later.. missing the spec meeting
    Ted Young
    @tedsuo
    ^ we be time shifting like doctor strange.
    Tristan Sloughter
    @tsloughter
    hah
    Jakub Malinowski
    @jtmalinowski
    hey all, I'm working on the implementation of env vars in JS as part of GA burndown, and there's one thing unclear for me, what's our (from the perspective of specification) general approach to invalid numbers in configuration, e.g. OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT being set to -1? I gave myself a reasonable amount of time to try to find it in the docs, but I couldn't find anything about it.
    Tristan Sloughter
    @tsloughter
    the spec says attribute values that are arrays must be homogeneous but the protobuf actually allows it to not be.
    not sure what to do in the case of erlang, would have preferred that the export could simply fail when it couldn't encode because it finds a string in a repeated int64 ..., but it won't. since that is the case it would be better for us to just send non-homogenous arrays in attributes because otherwise we have to scan every list of attributes added to a span and check the "type" (have no types, so also a pain)
    Andrew Hsu
    @andrewhsu

    Friendly reminder we have otel spec issue scrub 🧽 mtg tomorrow, Friday morning 8:30a PST.

    Not many spec issues to triage, so if we have quorum with collector maintainers, we’ll also continue triaging collector and collector-contrib issues

    Currently, our 3 outstanding P1 trace issues:

    Tristan Sloughter
    @tsloughter
    wait what, semantic conventions are yaml now... are they published anywhere as not yaml?
    4 replies
    and http status no longer maps to any span status, right? it is only set by the user?
    Tyler Yahn
    @MrAlias

    After a Span is ended, it usually becomes non-recording and thus IsRecording SHOULD consequently return false for ended Spans. Note: Streaming implementations, where it is not known if a span is ended, are one expected case where IsRecording cannot change after ending a Span.

    When implementing this and writing the End method to set the recording state, how do I tell if the span is in a streaming implementation or not?

    Tristan Sloughter
    @tsloughter
    from the semantic convention for http
    Don't set the span status description if the reason can be inferred from http.status_code.
    I assume this means like if its 404 you don't set the description (status message), but it doesn't make sense since any http status code you can infer the reason...
    what status codes are supposed to have a status.message set
    Justin Foote
    @justinfoote
    I assumed it means that the status message is not necessary if it’s the normal expected message, but if the customer is sending a custom status message, it should be included as an attribute.
    (I’ve worked in a codebase that used these messages to control flow in the client. It was... awful.)
    Tristan Sloughter
    @tsloughter
    I guess I was thinking about this wrong because I was thinking about it as if it were part of the SDK
    instead of up to each instrumentation. I'm instrumenting a simple web server, so it just doesn't put anything for message. but a more specific HTTP application might set something special as the message for a 404 or whatever
    thanks
    Andrew Hsu
    @andrewhsu

    Following on from our collector SIG issue scrub meetings from last week, we’ve completed:

    Thanks to those who attended (see sig mtg doc).

    Keeping the momentum, I propose 2 more sessions this week:

    • wed 8:30a - 9:00a PST (just before the collector sig mtg)
    • fri 9:00a - 9:30a PST (just after otel spec issue triage mtg)

    Which I’ll add to the otel calendar tomorrow with same people as invitees unless there is a more suitable time slot I should schedule.

    1 reply
    Carlos Alberto Cortez
    @carlosalberto
    Hey, the Spec SIG document has private access. Does anybody has a clue on this? We already had this problem in the past...
    Marcin Grzejszczak
    @marcingrzejszczak
    hi am I correct that there is a spec meeting in 4 minutes?
    John Watson
    @jkwatson
    yes!
    Marcin Grzejszczak
    @marcingrzejszczak
    :+1: will join
    John Watson
    @jkwatson
    Now if only someone will make the meeting notes document public
    Andrew Hsu
    @andrewhsu
    i seem to still have editor access. i’ve changed the doc to be public editable