Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Juraci Paixão Kröhling
    @jpkrohling
    @tigrannajaryan are the next releases going to be published under the opentelemetry namespace ?
    Ben Sigelman
    @bhs

    kind of misc, but I wanted to direct some attention towards open-telemetry/community#163

    TL;DR, I would like OpenTelemetry to have some “soft” guidelines on how we treat each other (as well as newcomers to the project). This is not about harrassment and other “bannable” / code-of-conduct infractions, but more about our aspirations for communication and how we treat each other. Happy to take any and all feedback, including “this is a bad idea for <reason>”.

    Juraci Paixão Kröhling
    @jpkrohling
    @tigrannajaryan, @owais, do you have any news about the operator for opentelemetry? open-telemetry/opentelemetry-service#274 -- I really want to kick start this, but if you have started some work on that already, I'd love to collaborate instead of creating something new...
    Dan Bentley
    @dbentley_twitter
    (This is my first time in gitter, so sorry if I have the wrong room) I asked a question about recording span events, and Liz Fong-Jones pointed me at https://github.com/open-telemetry/rfcs/pull/24/files , but I realized my question is less about sampling and more about when things are recorded. With OpenTelemetry, is there any way to record/export (not sure about terminology!) a span when it's started, in addition to when it's finished?
    Krzesimir Nowak
    @krnowak
    @dbentley_twitter : I'd say it's up to SDK that implements the opentelemetry API. For example, in opentelemetry-go, there is an experimental streaming SDK that records a bunch of events (https://github.com/open-telemetry/opentelemetry-go/blob/master/experimental/streaming/exporter/observer/observer.go)
    Dan Bentley
    @dbentley_twitter
    Perfect! Thank you.
    Jack Lindamood
    @cep21
    Hi, I left some comments on open-telemetry/opentelemetry-go#83 about concerns with the current open telemetry API limiting correct implementation of metrics collection for some providers. I would love to get more clarification on if CloudWatch is intended to be accepted under the open telemetry umbrella and how that is able to best happen. Thanks!
    Ted Young
    @tedsuo
    @jpkrohling that’s great, though I hope we can keep the standard OTel deployment as simple as possible!
    Paulo Janotti
    @pjanotti
    @jpkrohling regarding dockerhub for the Service we need to setup a opentelemetry org in dockerhub, ideally we should do it under the umbrella of CNCF. I'm creating an issue on the Service repo to track that open-telemetry/opentelemetry-service#281
    Juraci Paixão Kröhling
    @jpkrohling
    @tedsuo not sure what you mean -- the deployment itself would probably just be similar to the current kubernetes resources (examples/k8s.yaml)
    if you mean that it could be more complex for a user to try it out, I agree, and we can keep the current examples/k8s.yaml there. An operator is really helpful for a production deployment though, especially if it's able to handle day 2 operations
    at least, that's what our experience with the jaeger operator shows :)
    we need to setup a opentelemetry org in dockerhub
    @pjanotti there seems to exist one already, just without images published
    Paulo Janotti
    @pjanotti
    @jpkrohling hum, I didn't find that org, can you send me a link to it? We will need to work with whom is managing that so we can publish it there.
    Juraci Paixão Kröhling
    @jpkrohling
    it's not visible, but if you try to create one with that name, it indicates that it exists already
    for the record: I created opentelemetry on quay.io and added @pavolloffay and @objectiser as admins as well. I'm happy to add others
    Paulo Janotti
    @pjanotti
    thx, now we need to find who created it, hopefully someone on this room...
    Ted Young
    @tedsuo
    @jpkrohling I’m glad to see day 2 operations being thought about.
    @jpkrohling Besides a working kubernetes manifest, it would be great to see OpenTelemetry deployment toplology and day 2 operations (upgrades, basically) explained as a blog post, which we could turn into documentation.
    Juraci Paixão Kröhling
    @jpkrohling
    comprehensive readme + blog post, and later documentation ?
    Ted Young
    @tedsuo
    @jpkrohling exactly; a blog post could be a little hand-wavy, but it would give users a sense of what a telemetry deployment and operations should look like.
    Juraci Paixão Kröhling
    @jpkrohling
    +1
    Ted Young
    @tedsuo
    Btw, this stale app might be useful, to easily find issues in need of reply: https://github.com/marketplace/stale
    Glen Mailer
    @glenjamin

    :wave: Hello everyone!

    to what extent will the spec be recommending or mandating common attribute names?

    If you think of the name as the instance of a span, does anyone have a recommendation they use as the name for the type or class of a span? eg. name: DB select-todo-items vs type: postgresql-query, or name: GET /user/:userId vs type: http-request

    Christian Neumüller
    @Oberon00
    Hi @glenjamin! The spec does have recommendations on this: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/data-semantic-conventions.md. E.g. for HTTP you would have "component": "http" and a spanName of "/user/:userId".
    Liz Fong-Jones
    @lizthegrey
    I know that one pattern I'm particularly fond of is distinguishing application developer fields from automatically instrumented fields
    e.g. using "app.foo" instead of the root namespace
    but that isn't in the semantic conventions as is
    Austin Parker
    @austinlparker
    it might be interesting to consider that as a part of distributed context; i.e., can we make a place for people to declare their own semantic values/prefixes and automatically prefix user-set fields with those
    Liz Fong-Jones
    @lizthegrey
    I would really love prefixing user-set fields with "app." with the understanding that some folks would want to "no really put this in the root namespace"
    the question is whether to enforce this at the API level...
    Austin Parker
    @austinlparker
    i guess i’m thinking of the case where you might want to be picky-choosy about the value ot app
    *of
    maybe i have a service that’s part of a lot of different applications, can i set the app prefix to svc.app1, svc.app2
    /shrug
    Liz Fong-Jones
    @lizthegrey
    there are some occasions where I might want the same shared fields, but sometimes diverge, for sure
    Juraci Paixão Kröhling
    @jpkrohling
    @bogdandrutu , @SergeyKanzhelev, could any of you please create a repository named opentelemetry-operator and concede me push rights?
    Ben Sigelman
    @bhs

    :wave:

    Just wanted to let everyone know that I’ve merged the PR that adds https://github.com/open-telemetry/community/blob/master/COMMUNICATION.md

    The purpose of this doc/artifact is to serve as an informal “sign on the wall” about the way we wish to communicate with each other. If you see people demonstrating great communication skills that aren’t already in that doc, please submit a PR to add something; and if you see people demonstrating not-so-great communication skills, feel free to gently/respectfully point that out and refer to COMMUNICATION.md as a reminder of what we aspire towards.

    (And thanks to everyone who made comments and suggestions during the review process)

    Liz Fong-Jones
    @lizthegrey
    hey, @iredelmeier and I just finished another OTel Tuesdays (https://www.twitch.tv/videos/473144796), they're video on demand but also live at 11am pacific every Tuesday, and we're looking for guests to come on every now and then ;)
    Constance Caramanolis
    @ccaraman
    @lizthegrey I'd love to be a guest!
    Glen Mailer
    @glenjamin
    @Oberon00 thanks - my initial instinct is that component seems too broad for what i had in mind, but i might be overthinking it. I was imagining something in-between component and name. It's less clear in generic terms, but in application-specific code I can see wanting to have a few different flavours of events from the same logical component
    Glen Mailer
    @glenjamin
    On a different note: are there any plans to incorporate exception-tracking services as exporters into OpenTelemetry? rollbar / airbrake / sentry etc?
    Tarun Pothulapati
    @Pothulapati
    Hello Everyone,
    Is there a OT all-in-one installation? something like jager-all-in-one, like without OT-Agents?
    Thanks
    Yusuke Tsutsumi
    @toumorokoshi
    @glenjamin I don't believe there are any plans, but I for one support that idea. I presume since that's not a milestone effort at the moment, development on how that will work would require an RFC to start
    Juraci Paixão Kröhling
    @jpkrohling
    @Pothulapati join the opentelemetry-service room, but I understand that the service is already the all in one, as both the collector and the agent are the same binary -- they only differ in how they are deployed
    Tarun Pothulapati
    @Pothulapati
    sure! Maybe in that case we will only want to have the collector deployed.
    Ted Young
    @tedsuo
    Hmmm, looks like some calendar events are missing for today?
    Python, Go, and Data Formats