Replies: 3 comments 5 replies
-
Hm, I wonder if its the lack of CA's.. but the fallback says it is happening. I thought this was resolved with #547 but maybe its not fully solved. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Having same issue, with the following setup: Dependencies: [
{:opentelemetry_api, "~> 1.2.2"},
{:opentelemetry_cowboy, "~> 0.2.1"},
{:opentelemetry_ecto, "~> 1.2.0"},
{:opentelemetry_exporter, "~> 1.6.0"},
{:opentelemetry_liveview, "~> 1.0.0-rc.4"},
{:opentelemetry_oban, "~> 1.0.0"},
{:opentelemetry_phoenix, "~> 1.2.0"},
{:opentelemetry_tesla, "~> 2.3.0"},
{:opentelemetry_semantic_conventions, "~> 0.2.0"},
{:opentelemetry, "~> 1.3.1"}
] Using:
In a Have tried the following:
Still receiving the same message. |
Beta Was this translation helpful? Give feedback.
0 replies
-
We are facing the same error - any workarounds thought about it? 15:46:26.213 [debug] OTLP exporter failed to initialize: exception error: no match of right hand side value {error,inets_not_started}
in function opentelemetry_exporter:start_httpc/1 (/app/deps/opentelemetry_exporter/src/opentelemetry_exporter.erl, line 239)
in call from opentelemetry_exporter:init/1 (/app/deps/opentelemetry_exporter/src/opentelemetry_exporter.erl, line 210)
in call from otel_exporter:init/1 (/app/deps/opentelemetry/src/otel_exporter.erl, line 44)
in call from otel_batch_processor:init_exporter/2 (/app/deps/opentelemetry/src/otel_batch_processor.erl, line 327)
in call from otel_batch_processor:idle/3 (/app/deps/opentelemetry/src/otel_batch_processor.erl, line 200)
in call from gen_statem:loop_state_callback/11 (gen_statem.erl, line 3113)
in call from proc_lib:init_p_do_apply/3 (proc_lib.erl, line 329)
15:46:26.214 [warning] OTLP exporter failed to initialize with exception :error:{:badmatch, {:error, :inets_not_started}}
15:46:26.262 [info] Loading 129 CA(s) from :otp store
{exit,terminating,[{application_controller,call,2,[{file,"application_controller.erl"},{line,511}]},{application,enqueue_or_start,6,[{file,"application.erl"},{line,380}]},{application,ensure_all_started,3,[{file,"application.erl"},{line,359}]},{elixir,start_cli,0,[{file,"src/elixir.erl"},{line,195}]},{init,start_it,1,[]},{init,start_em,1,[]},{init,do_boot,3,[]}]} |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to deploy Phoenix application with OpenTelemetry tracing in a Docker container.
Dockerfile
I was using so far (sucessfully) is a typical one (i.e. generated bymix phx.gen.release --docker
). Following versions are used:So, the image is
hexpm/elixir:1.15.4-erlang-26.0.2-debian-bullseye-20230612-slim
.(I'm running the same versions locally for development, the only difference I'm working on Ubuntu 22.04 via WSL2.)
(But I've confirmed the same happens on Ubuntu image)
The problem is that then running this container, a following message is produced which indicates that OTLP exporter fails (with
MIX_ENV=prod
):This doesn't happen when running code in (both in
dev
andprod
) locally, outside container.My OTLP config is almost the same as in https://opentelemetry.io/docs/instrumentation/erlang/getting-started/, namely:
mix.exs
:application.ex
:config/runtime.ex
:I've figured out that the problem only occurs in a release, that's why I only see it in a container, not when starting via
mix phx.server
oriex -S mix phx.server
. | I've figured out that the problem only occurs in a release, that's why I only see it in a container, not when starting viamix phx.server
oriex -S mix phx.server
.When run with lower log level I also get:
Does anyone have any idea why this problem occurs?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions