Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tigran Najaryan
    @tigrannajaryan
    @/all feel free to invite anyone else who is interested.
    Preliminary slots for the first meeting: Tue, Mar 17, 9AM Pacific Time or 2PM Pacific Time
    Does anyone remember that service that allows to vote for meeting slots?
    Morgan McLean
    @mtwo
    was it doodle.com ?
    I can do 2:00 but not 9:00
    Tigran Najaryan
    @tigrannajaryan
    @/all here is the Doodle to vote for the bootstap meeting slot: https://doodle.com/poll/sthbvs8niwwimpec
    Morgan McLean
    @mtwo
    voted, thanks Tigran!
    Tigran Najaryan
    @tigrannajaryan

    Bootstrap meeting vote complete, confirmed meeting time: Mar 18, 10am Pacific Time / 1pm Eastern Time.

    Meeting added to OpenTelemetry calendar.

    Zoom: https://zoom.us/j/8203130519

    Agenda: https://docs.google.com/document/d/1cX5fWXyWqVVzYHSFUymYUfWxUK5hT97gc23w595LmdM/edit#heading=h.lro8kgalys10a

    Przemek Maciolek
    @pmm-sumo
    Hi All, I am working on embracing Open Source tools more within my company, especially on the collection front. Huge fan of what OpenTelemetry achieved so far and the speed of development. If you don't mind, I would love to join the SIG meeting (maybe my colleague could join as well) and see if there's anything we can do to support the initiative
    Morgan McLean
    @mtwo
    @tigrannajaryan I missed two things when we set the time: it conflicts with the community meeting (including next week) and won't work for Leo and his team at Google
    so we'll need to shift to a later time or alternate times for Asia / Europe / NA
    for future meetings
    Tigran Najaryan
    @tigrannajaryan
    @/all based on what Morgan said here is a Doodle for the next SIG meeting shifted to later time: https://doodle.com/poll/pta9dhiscb93nf6i
    For future meetings we will use this for alternate weeks.
    Tigran Najaryan
    @tigrannajaryan
    @/all an OTEP to add Log-related concepts to our vocabulary: open-telemetry/oteps#91
    Wesley Pettit
    @PettitWesley

    Hey all, based on our discussions, I've started a document for housing agent evaluations and debating concerns for logging/telemetry agents.

    https://docs.google.com/document/d/15EMUKw-dv4z-oF28CKh5CZXYJO-5a-dMoev7_Ka-u10/edit#heading=h.6bp9stv65rh3

    I will bring this up in the Log SIG meeting today
    Is there an easy way to add all relevant individuals as editors of a google doc?
    Tristan Sloughter
    @tsloughter
    in case it is useful, I poked the person at Postmates who has been responsible for our logging infrastructure:
    A basic summary on our experiences with logging agents:
    * fluentd: Too slow, couldn't handle our volume at any reasonable resource usage
    * fluentbit: Buggy. They've since fixed their broken JSON handling but there's probably other issues
    * filebeat: Doesn't handle rotation and deletion properly
    All but filebeat also had the issue where it would buffer internally if its sink went down, rather than backpressuring to its source.
    ie. if you're reading from a file, but you can't send the data right now, you read from the file and put it in a new file instead of just...waiting before reading more from the file
    
    IMO agents should be as simple as possible and do the bare minimum to get the data off the node into somewhere more robust (eg. message queue). Then any transforms or extra cross-referencing should be a seperate processing step.
    Wesley Pettit
    @PettitWesley

    fluentbit: Buggy. They've since fixed their broken JSON handling

    That was fixed quite a while ago, so I suspect this experience is a bit old

    I have a large number of enterprise customers at AWS who are using Fluent Bit, for the specific features that we use, I've not heard of any significant complaints.
    Tristan Sloughter
    @tsloughter
    good to know
    I guess it stated with fluent/fluent-bit#1278
    Gregor Zeitlinger
    @zeitlinger
    is there a date for the next zoom meeting already?
    Tigran Najaryan
    @tigrannajaryan
    Yes, Log SIG meetings are on Wednesdays. See OpenTelemetry calendar (time alternates every week).
    Ted Young
    @tedsuo
    Perhaps a naive question, but what’s wrong with syslog? I am old, explain to me why my trusty tools are no longer sufficient.
    8 replies
    Tristan Sloughter
    @tsloughter
    speaking of protocols like syslog. is journald being considered?
    last I knew there was no official publishing support for journald, but it is a structured, compact, binary log format that is already used by most servers these days I'd assume
    2 replies
    Tigran Najaryan
    @tigrannajaryan
    @/all Logs vision is now published. I believe this is very important and a must read for OpenTelemetry Logs contributors: https://github.com/open-telemetry/oteps/blob/master/text/0092-logs-vision.md
    Reiley Yang
    @reyang
    :thumbsup:
    Binary Logic
    @binarylogic

    @tsloughter that reflects our evaluations as well. By the way, Brian Troutwine (creator of cernan) has been advising us on Vector. I'm not sure if you worked with him at Postmates:

    • fluentbit: Buggy. They've since fixed their broken JSON handling but there's probably other issues

    The JSON issues! For a little bit of context, and to not repeat it here, see:

    https://github.com/timberio/vector/issues/727#issuecomment-561004676

    Fluentbit reached 1.1 with those issues 👀.

    That was fixed quite a while ago, so I suspect this experience is a bit old

    @PettitWesley we are still able to produce JSON parsing issues, but I agree, the major ones are fixed!

    8 replies