Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tristan Sloughter
    @tsloughter
    oooh right, CODEOWNERS
    Irving Reid
    @irvingreid
    Unfortunately it's probably going to take a while to get PD to sign the corporate CLA. I'll do the individual form to get the current PR unblocked.
    Irving Reid
    @irvingreid
    Anyone going to Lone Star Elixir (aside from Greg Mefford and Samuel Mullen, who are speaking on OpenTelemetry and Telemetry, respectively...)? Unfortunately I have a conflict & can't make it to Code Beam.
    Tristan Sloughter
    @tsloughter
    thanks
    I'm not making it to shit this year :(. missing codebeam even. since I'm in Colorado I'll probably make it to ElixirConf for the first time, but that's not until September
    Tristan Sloughter
    @tsloughter
    trying our hauleth's idea of having named tracers in Elixir be modules like Ecto does with Repos
    I like that part, just not sure where some stuff goes
    Tristan Sloughter
    @tsloughter
    in case anyone is interested and has time to pick up one of those tasks so we can hit beta by the 16th :)
    Tristan Sloughter
    @tsloughter
    so with LibraryResource being the opentelemetry library are there resource attribute defined for the tracer name/version yet?
    Tristan Sloughter
    @tsloughter
    or wait, library resource is changed to telemetry? I must have really zoned out yesterday
    dammit, this is the wrong channel, haha
    Tristan Sloughter
    @tsloughter
    ^ API and SDK published to Hex under an opentelemetry organization
    Tristan Sloughter
    @tsloughter
    honeycomb elixir integeration now available thanks to garth :) https://hex.pm/packages/opentelemetry_honeycomb
    Tristan Sloughter
    @tsloughter
    we have new meeting times. every thursday but switching between 7am PST and 15pm PST https://github.com/open-telemetry/community#erlangelixir-sig
    Tristan Sloughter
    @tsloughter
    SIG meeting today at 3pm PST
    Gustavo Aguiar
    @gugahoa
    Thanks for pointing out the room, @tsloughter
    (and for the links)
    Gustavo Aguiar
    @gugahoa
    Would this be the proper channel for community support? I don't want to clutter the room with questions if it's not the proper place to ask
    I'm trying to grok the examples here https://github.com/opentelemetry-beam/opentelemetry-examples but I'm not sure I'm following
    Tristan Sloughter
    @tsloughter
    this is the proper channel but likely always be able to get more help on the erlang or elixir slack in the channels for observability just because people are in those more
    Gustavo Aguiar
    @gugahoa
    @tsloughter I'm trying to setup the opentelemetry_exporter to send data via gRPC to opentelemetry-collector, but I'm receiving the following error:
    I tried to find in opentelemetry-erlang and opentelemetry_exporter any mention of noproc but couldn't find it
    Gustavo Aguiar
    @gugahoa
    I did it :tada:
    Tristan Sloughter
    @tsloughter
    cool :)
    Gustavo Aguiar
    @gugahoa
    the problem was the protocol key, for some reason it's throwing a badmatch error
    Petr Stepchenko
    @Nitrino

    Hi guys. I'm trying to set up elastic apm with opentelemetry, but I see messages with NULL in the otel-collector logs, it seems that there is something missing in my settings?
    https://gist.github.com/Nitrino/77cd49acc3517290eb8d880caef7ef42

    I use:

          {:opentelemetry_api, "~> 0.3"},
          {:opentelemetry_exporter, "~> 0.4"},
          {:opentelemetry_ecto, "~> 0.1.0"},
          {:opentelemetry_plug, github: "opentelemetry-beam/opentelemetry_plug"},
          {:opentelemetry_phoenix, github: "opentelemetry-beam/opentelemetry_phoenix"},

    And set up a configuration:

    config :opentelemetry, :resource,
      service: [
        name: "qb_calls",
        namespace: "qb_calls"
      ]
    
    config :opentelemetry,
           :processors,
           ot_batch_processor: %{
             exporter: {:opentelemetry_exporter, %{protocol: :http_protobuf, endpoints: [{:http, 'localhost', 55681, []}]}}
           }
    Petr Stepchenko
    @Nitrino

    I tried to enable ot_exporter_stdout for debugging (:ot_batch_processor.set_exporter(:ot_exporter_stdout, [])) and seemingly correct output in the console.
    https://gist.github.com/Nitrino/3d7375d7c75f1be1352280f63fcd64aa

    I can't figure out what's wrong with my settings

    Petr Stepchenko
    @Nitrino
    Oh, it's has already been fixed in the opentelemetry_exporter master.
    Sorry to bother
    Tristan Sloughter
    @tsloughter
    @Nitrino no worries, good to hear it is working for you :)
    Tristan Sloughter
    @tsloughter
    lots to discuss in the Otel Erlang meeting this afternoon https://docs.google.com/document/d/1EbBiRjBc_cBf0T_B5OtNRPhbD4jdBrVYJAy8euCDrUI/edit#
    Tristan Sloughter
    @tsloughter
    new PR is open. this is the important change to take note of (when reviewing, it isn't touched by a user) https://github.com/open-telemetry/opentelemetry-erlang/pull/126/files#diff-8411ab5f399a2f02fad4d7808c21f1f3e1450fbbdf7b007b499e7f9de2b79024R56
    6:43
    the main erlang macro api and elixir api (now with macros only for start_span and with_span since the tracer isn't needed in many calls anymore) remain the same
    ioolkos
    @ioolkos
    Hello all, wouldn't something like this always get sampled? I don't see this exported at all (using otel_exporter_stdout)
    span_with_sleep_ms(Delay) ->
    Sampler = otel_sampler:setup(always_on, #{}),
    Tracer = opentelemetry:get_tracer(otel_example),
    otel_tracer:with_span(Tracer, <<"span_with_sleep_ms/1">>, #{sampler => Sampler}, 
      fun(SpanCtx) ->
        otel_span:set_attribute(SpanCtx, <<"Delay">>, Delay),
        timer:sleep(Delay)
        end).
    Tristan Sloughter
    @tsloughter
    yes. are you using the latest git repo or hex packages?
    ioolkos
    @ioolkos
    am using Github master branch
    and I'm seeing SPANS FOR DEBUG output in the Erlang console, but not the spans.
    so I wanted to explicitly set an always_on sampler. I'll have to explore this a little further then
    Tristan Sloughter
    @tsloughter
    ok
    ioolkos
    @ioolkos
    but it's good to know this should work
    Tristan Sloughter
    @tsloughter
    I guess make sure the Tracer isn't noop
    you can just print out the Tracer and it'll be the first element in the tuple is the module
    if it ends with noop then that explains this
    ioolkos
    @ioolkos
    I register an application tracer, so I think it will just be otel_default_tracer
    jep, it's the default tracer. Would the default tracer not sample a call as above?
    Tristan Sloughter
    @tsloughter
    ok. no, it should
    ioolkos
    @ioolkos
    ok, thanks