manukall
What metrics about your Phoenix app would you like tracked?
Hey everyone,
I’m working on a Phoenix monitoring project and I’m wondering what Elixir / Erlang specific metrics people are interested in, besides of the usual “how long did that controller take” and “how long did that database query need”.
I’m thinking of basically what recon’s node stats function returns:
- process count
- run queue and error_logger queue size
- memory by processes, atoms, binaries, and ets tables
- bytes in and out of the node
- number of reductions
- scheduler usage
Does that make sense? Would you like to track anything else?
Thanks,
Manuel
Most Liked
OvermindDL1
AstonJ
I like the idea of Awstats in a Phoenix app too ![]()
manukall
The project is currently in a closed alpha (you can sign up for the waitlist at https://pryin.io) and it’s not actually phoenix-only. You could still use it to keep track of beam metrics like how much memory is used and by what (ETS, atoms, binary, …), data about garbage collection, processes (number of processes, reductions, scheduler usage, …).
If you connect your phoenix app, you get metrics about how long controller and channels take, which ecto queries are run (and how long they take), and a lot more ![]()
Popular in Discussions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









