Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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?
    Kranti Vikram A
    @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.
    Tyler Benson
    @tylerbenson
    I hate to say it but Gitter mobile app is so horrible. I really wish we stuck with slack.
    I also just discovered I was kicked out of this room.
    Krzesimir Nowak
    @krnowak
    Everyone was kicked out of this room, because it was deleted.
    Bob Strecansky
    @bobstrecansky
    (inadvertently)
    Ted Young
    @tedsuo
    @tylerbenson we never actually switched to slack, but we still could if we resolve the issues that were raised last time.
    Tristan Sloughter
    @tsloughter
    isn't slack clamping down on publicly joinable slacks?
    or is there a paid cncf/linux foundation slack? since also if we did go to the trouble of moving I'd suggest doing so to a service we can keep history
    Ted Young
    @tedsuo
    There is a paid CNCF account, but we did not want to use a CNCF-wide shared account, as discoverability is bad enough given how many channels we need. K8s uses their own slack for this reason.
    The other issues are the ones you mentioned: a lack of message retention, and difficulty for new users to join.
    Tyler Benson
    @tylerbenson
    I’d argue that the tradeoff with gitter is difficulty for regular users to use every day.
    Ted Young
    @tedsuo
    I can’t remember if we determined whether a slack bot which archived everything was feasible or not.
    Sam Schlegel
    @samschlegel
    @davidbarsky :wave: I'd definitely be interested in something like an OpenTracing Rust SIG. I've been holding off on add tracing to our Rust services since nothing there exists yet, and might have some time in the coming quarters to spend on that (thanks to @akvanhar for calling this Gitter to my attention)
    David Barsky
    @davidbarsky
    @samschlegel i know someone implemented a mutex’d honeycomb subscriber a few days ago, and we just landed json support as well. it might be more than you’d expect!
    Sam Schlegel
    @samschlegel
    :eyes:
    David Barsky
    @davidbarsky
    exporter, sorry—terminology is hard to track :)
    should have a lock-free span registry Soon™
    (maybe this or next week, eliza’s fuzzing it)
    Alyson van Hardenberg
    @akvanhar
    :D
    Sam Schlegel
    @samschlegel
    Super cool!
    David Barsky
    @davidbarsky
    lemme track down the honeycomb one and point you at the JSON-based one.
    Sam Schlegel
    @samschlegel
    Thanks David!
    @tedsuo Also Byron says hello!
    Tristan Sloughter
    @tsloughter
    devs on the Rust impl might want to take part in the group to make the spec language agnostic. let me know if you do or know somone who would
    David Barsky
    @davidbarsky
    how so? the protobuf definition does seems pretty language agnostic
    David Barsky
    @davidbarsky
    (but i’d be happy to be cc’d and read the discussions and point out any gotchas)
    Tristan Sloughter
    @tsloughter
    @davidbarsky the spec language, not the protobufs