lawik
My expectation is that if you use a service you probably use Sentry. Seems like a very common choice. But I’d love to hear if the truth is more diverse.
I am thinking about possibilities for integrating error reporting with NervesHub. And while we could certainly build a NervesHubLink extension for sending errors up to NervesHub it may be more helpful and a lot more bang-for-the-buck if we can integrate with what people actually use and then correlate the device identifiers and show “hey, UND00234238 has reported 1000 errors today”.
So let me know how you detect problems, report errors, all that, if you don’t mind. If you feel the need to weigh in but don’t have production Nerves devices, please be clear about that 
Where Next?
Trending in Discussions
Other Trending Topics
Latest Nerves Threads
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
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.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
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)
Nezteb
I’ve been meaning to try out
:towerfor this: tower | HexRegardless of specific implementation, I love the idea of error reporting providers as a behaviour.
amclain
We’ve used Sentry, DataDog, custom Grafana stuff…
The Redwire Labs Nerves project generator comes with Sentry commented out in the template because it’s the simplest one we’ve integrated with. If I recall, the Sentry library doesn’t report GenServer crashes during
initby default, but we have some code that catches and reports those.I do wish NervesHub handled the error reporting. It would be great for consolidating SaaS services, and one less connection we have to instruct users to whitelist.
lawik
Yeah, NervesHub directly taking in error reports might be the result. I have a hunch that Sentry is quite common among existing systems. But I could also see a variant of ingesting errors via Sentry for those cases, assuming our error handling is something compatible enough.
The neat thing with error reporting is that it is additional signal for deployments to be smarter about devices misbheaving after an update.
Over time we can consider metrics vs user’s configured thresholds, error reports, log lines at error level. It becomes a very multi-faceted “health” concept. And it lets us determine when a deployment should back off.