Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Bob Strecansky
    @bobstrecansky
    Woohoo! Thanks Morgan!
    Armin Ruech
    @arminru
    Thanks @mtwo!
    Currently every GH org member is a Gitter admin and every Gitter admin is a room admin who, in turn, can delete the room, edit permissions, ban people and the like.
    We could (and probably should) switch the permission setting to make only specific people Gitter admins so that accidents like these are less likely to happen in future :)
    Ted Young
    @tedsuo
    @arminru good to know that is possible!
    Tristan Sloughter
    @tsloughter
    is anyone from Elastic APM involved in opentelemetry?
    Morgan McLean
    @mtwo
    @arminru done! I didn't know that was possible on Gitter yet
    @bhs @bogdandrutu @SergeyKanzhelev I made you admins
    and @yurishkuro
    didn't add sarah as I don't think that she subs here and I've forgotten her github handle
    Armin Ruech
    @arminru
    Yeah I didn't want to believe there was no option to prevent room purging by everyone in the org so I clicked around a bit :smile:
    Thanks Morgan!
    Manos Ragiadakos
    @mragiadakos
    Hi everyone! I am new to distributed tracing and I am trying to create tests over the logs.
    However I have hard time on how to make the agent and the collector send the logs to my server.
    Is there a documentation for that kind of work ?
    What would you recommend me to do ?
    Ben Sigelman
    @bhs

    Hi everyone – if you are a “member of standing” (TL;DR “a member of the OpenTelemetry GitHub organization), please endorse candidates for the governance committee election that’s taking place this month:

    The form: https://forms.gle/3nrPt9HTsNBFdeku7

    More detail: https://lists.cncf.io/g/cncf-opentelemetry-community/message/33

    Thanks!

    Tristan Sloughter
    @tsloughter
    is there a list of involved vendors? so I don't keep bothering everyone with questions like the one I'm about to ask, is InfluxData involved? :)
    Liz Fong-Jones
    @lizthegrey
    there's no formal concept of "organization membership" iirc, unlike Linux Foundation which does have org memberships
    as far as whether anyone is a contributor who's employed by InfluxData... let's see
    Tristan Sloughter
    @tsloughter
    gotcha. opencensus had a loose definition and had a list on the front page https://opencensus.io/
    and a "users" page https://opencensus.io/community/users/ -- but I guess it is too early for that :)
    Liz Fong-Jones
    @lizthegrey
    Jacob Marble has attended a few spec SIG meetings
    Tristan Sloughter
    @tsloughter
    ok, thanks
    hopefully Elastic is involved. the response I got from one of them was that they'd implement the API and really hope vendors can be convinced to support the SDK :(
    David Barsky
    @davidbarsky
    hi! this is a bit of a reply-all/broadcast: i'm involved with Rust's https://github.com/tokio-rs/tracing, which has really similar semantics to OpenTelemetry's Trace. A colleague and I are working on getting an subscriber (an exporter, in tracing's terminology) from tracing to OpenTelemetry once we've fuzzed a lock free-free hashmap sufficiently. i'd love to share the end product once it's in a decent state!
    (I also didn't see any mention of this in the docs/issues, but is there an intention to have a standardized zpage package with opentelemetry?)
    Ted Young
    @tedsuo
    Nice! @bogdandrutu might know about the plan for zpage.
    @davidbarsky is there interest in porting your work over to seed an OpenTelemetry Rust project?
    David Barsky
    @davidbarsky
    @tedsuo probably, yeah—I'm just worried about the stability of the interfaces this exporter would be relying on; it might make sense (for the time-being!) for this code to live in tracing's repository until we solidify the stuff this would be relying on
    it's not "no you can't have this!", it's more of a "oh jeez, we're probably gonna be making breaking changes soon-ish and we should have a short cycle" :)
    Ted Young
    @tedsuo
    @davidbarsky no problem, whenever you feel ready; there isn’t a group currently pushing to start a Rust SIG. (Though I imagine there will be breaking changes anyway, as surely there are some differences between tokio tracing and OTel.)
    David Barsky
    @davidbarsky
    @tedsuo there are differences, yes, but in reading the specification tracing’s span felt like a superset of opentelemetry’s trace—it’s more of also needing to support in-process tracing which tends to have different performance goals than distributed tracing :)
    Ted Young
    @tedsuo
    @davidbarsky gotcha :)
    David Barsky
    @davidbarsky
    but thanks, i'll probably open issues/ask questions here if anything comes up :). i'd love to have zpages in tracing via opentelemetry—would be super great for local debugging!
    apologies, might be a bit over-excited :)
    Ted Young
    @tedsuo
    exactly excited enough! :)
    Hey @/all, some comments about spec work: I’ve been getting regular questions about how to implement certain items in the spec. Especially new concepts, like named tracers. Just to be clear, if something feels unclear in the spec, that does not mean you are dumb or missing something. It may well be unclear. So don’t be afraid to raise questions, or propose changes to the spec to clarify things once you have an answer. If you'r actively working on implementing the spec, then you are completely in your rights to make these changes!

    Going forwards, I would like make sure that we are not leaving unanswered questions until the end. Over the next week, I will assist in rounding up working groups to pay active attention to the spec – possibly by spiking on implementations early while we are discussing RFCs and Spec PRs – to make sure that we aren't leaving implementation concerns unaddressed until after the work is merged. If people are interested in this, please let me know. We want to have the current set of v0.3 issues finished by kubecon.

    Personally, I'm excited for the final bits of spec work, like separating out context propagation from observability. But I am also concerned that some changes may be too much, or are going to slow us down significantly. If that's the case, I'm going to suggest that better is the enemy of good enough, and move to cut scope so that we can reach our original goal of merging OT/OC and quickly achieving parity.

    So, again, I'd like to see a big push to finish the last round of spec work in the next four weeks. I don't think we can do that without active and early participation from SIG members!

    Please let me know you have thoughts or questions, either here or via DM.
    Tristan Sloughter
    @tsloughter
    :thumbsup:
    Ted Young
    @tedsuo
    Created a room for discussing context propagation separation (https://github.com/open-telemetry/oteps/pull/42/) here: https://gitter.im/open-telemetry/context-prop-spec
    Bob Strecansky
    @bobstrecansky
    We have a contributor that is having some trouble with the CLA. Is there anyone who is able to help him? He mentioned he reached out to the
    hellosign and the Linux foundations to no avail.
    Sergey Kanzhelev
    @SergeyKanzhelev
    @bobstrecansky what kind of a trouble? Cannot sign or PR wouldn’t be recognized as signed?
    Bob Strecansky
    @bobstrecansky
    @SergeyKanzhelev - I believe he has signed but it has not been recognized as being signed. PR in question: open-telemetry/opentelemetry-php#18
    Dmitry Krokhin
    @nekufa
    @SergeyKanzhelev i wrote to hellosign support and they told me that "something unknown went wrong". I need cncf to resend the agreement, but cncf support is not answering me, i can't find a way to do it through web interface. Is there a way to reach somebody who can resend me the agreement?
    vikrambe
    @vikrambe
    Hi All, I need your views on open-telemetry/opentelemetry-collector#407
    Juraj Michálek
    @jmichalek132
    Hi is this a good place to ask for recommendation on implementing tracing in a company?
    Daniel Khan
    @danielkhan
    @jmichalek132 - this is a big question but feel free to ask. There are many experts here indeed :)
    Juraj Michálek
    @jmichalek132
    In our company we are debating how to start instrumenting applications, whether to start with few business operation and instrument them end to end or start by instrumenting at the application level (i.e. one span for a application) but for all methods
    any recommendation?
    Daniel Khan
    @danielkhan
    Which technologies / languages?
    Juraj Michálek
    @jmichalek132
    languages python,javascript,c,c++,java,scala,..
    as for the technologies that would be a lot longer list
    Daniel Khan
    @danielkhan
    I would see - whatever you choose to use - if it supports auto instrumentation keeping the amount of monitoring code in your application as low as possible.
    OpenTelemetry is currently moving in that direction. Node.js already auto-instruments http and grpc ootb for instance.