andym
i’m trying to use open telemetry to send messages to aws x-ray from my elixir livewiew project. from an aws point of view i need to use aws distro, however what i’m not sure of is which libraries to use from the elixir side. i came across the following article Elixir, OpenTelemetry, and the Infamous N+1 · The Phoenix Files and from what i understand the flow of data is as follows
code -> collector (collects and exports) -> AWS Distro -> AWS X-Ray
Is this understanding correct, if its correct also how do i configure the collector to export the data to AWS Distro ?
also based on the articles mentioned above i need to use the following libraries
{:opentelemetry_exporter, "~> 1.0"},
{:opentelemetry, "~> 1.0"},
{:opentelemetry_api, "~> 1.0"},
{:opentelemetry_ecto, "~> 1.0"},
{:opentelemetry_liveview, "~> 1.0.0-rc.4"},
{:opentelemetry_phoenix, "~> 1.0"},
{:opentelemetry_cowboy, "~> 0.2"}
if the libraries are the correct ones its fine (i can upgraded to the latest version) or are there a different set of libraries i should be using ?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
At WyeWorks, we believe great software is built by combining technical excellence with genuine human connection
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Raees678
From my understanding your diagram is partially correct. You can send traces to a collector, which can forward to AWS Distro (or any number of other collectors). However AWS Distro is a collector as well, so you can forward directly to it from your application bypassing any other collectors in between if you don’t need them .
Those libraries do seem correct though. This ElixirConf talk: https://www.youtube.com/watch?v=4OBtc_eIKIE shows a working demo of forwarding to an otel-collector. He uses Grafana Tempo instead of AWS Distro, but technically it should be possible to switch out one otel-colelctor from another, since they are all using the same protocol to collect distributed traces.
andym
thanks, i saw the video as well, with regards to your statement of sending directly to AWS Distro, how do i do that ?
Raees678
I think the default otel-collector port is 4318 for http recievers. AWS Distro might have a similar port open to send your traces to. When configuring opentelemetry-exporter you can specify the port to export to in your elixir app’s config.