fredr
Is there some way in Phoenix to see what path was used to match a route?
This would be very useful for metrics and logging (and probably other things). We would like to have the match path as a label in prometheus and as a log field so we can aggregate on that in kibana.
In Plug this was added a while ago in this PR Add router path to Plug.Conn by mgartner · Pull Request #630 · elixir-plug/plug · GitHub
I’ve check that there are no equivalent field in conn.private from Phoenix, but is it accessible in some other way?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
The deployment platform built for Elixir: PaaS ease, VPS control.
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 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
NobbZ
What version of plug are you using according to mix.exs and mix.lock?
NobbZ
In general that field should only get accessed through
Plug.Router.match_path, which is available since 1.5 as far as I can tell.fredr
Plug is version
1.7.1, but I don’t think the Phoenix.Router uses the Plug.Router to match under the hood.It works fine in a regular Plug.Router outside of Phoenix.
NobbZ
I always thought
Phoenix.Routerwhere just wrappingPlug.Router.