aloukissas
Problem: I am trying to identify where a bunch of root spans e.g. myapp.repo.query:users come from (which essentially map to a SELECT * from "users" AS u0 WHERE (u0."id" = $1)).
This could e.g. be the MFA of the caller, that could appear as the db.operation.name.
One could do this explicitly, but this requires to pass the MFA in every call site.
Any ideas here? Anyone solved this before?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Supporting innovation across the BEAM ecosystem.
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
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
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!
Master modern tools, write cleaner code, and tackle real-world challenges.
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 1- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
RudManusachi
Hi, @aloukissas!
Seems like, that could be achieved by setting
stacktrace: truein the Repo config. (Look up “stacktrace” keyword on this page Ecto.Repo — Ecto v3.14.0)Then in the telemetry events in metadata there will be the stacktrace from where we could extract the caller’s MFA.
OpentelemetryEcto currently doesn’t provide with any option to support that integration. So will need to patch this