no worries
you can "bind" an instrument and labels for an optimized reference to a metric you want to be recording to
@irvingreid can you sign the CLA here? open-telemetry/opentelemetry-erlang-api#13
@tsloughter bah, sorry for going silent for so long - I had a bit of WIP that I was going to clean up over the holidays and ended up not getting to it. Looks like you're already past the point I got to with macros. I'll need to check with my management about getting the CLA signed, I'll dig into that on Monday.
now that we have some Elixir code does anyone else want to be official reviewers? @zachdaniel ? hm, I'd include Gregg in that but he doesn't appear to be in here. Spandex team :)
:)
I haven’t been able to give much, but I can do that at the bare minimum
🙂
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
I'm not satisfied with it yet but https://github.com/open-telemetry/opentelemetry-erlang-api/pull/13/files
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
created issues for what is needed to reach beta milestone (scheduled for March 16) https://github.com/open-telemetry/opentelemetry-erlang-api/issues based on https://docs.google.com/document/d/1eviggoIguOS89dgKL-8ntUOCfPP6FLWAoQkGoBDsld0/edit#
in case anyone is interested and has time to pick up one of those tasks so we can hit beta by the 16th :)
dammit, this is the wrong channel, haha
^ API and SDK published to Hex under an opentelemetry organization
honeycomb elixir integeration now available thanks to garth :) https://hex.pm/packages/opentelemetry_honeycomb
we have new meeting times. every thursday but switching between 7am PST and 15pm PST https://github.com/open-telemetry/community#erlangelixir-sig
OpenTelemetry Erlang SIG meeting in 30 minutes https://www.google.com/url?q=https://docs.google.com/document/d/1EbBiRjBc_cBf0T_B5OtNRPhbD4jdBrVYJAy8euCDrUI/edit?usp%3Dsharing&sa=D&source=calendar&usd=2&usg=AOvVaw1r5lcC0cCBmYr2HqTgW3-R
(and for the links)
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
I'm trying to grok the examples here https://github.com/opentelemetry-beam/opentelemetry-examples but I'm not sure I'm following
I tried to find in
opentelemetry-erlang and opentelemetry_exporter any mention of noproc but couldn't find it
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, []}]}}
}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