ErrorTracker - an Elixir-based built-in error tracking solution

[odarriba]

@frankdugan3

Very nice! Are there plans to add a JS package to handle catching client-side errors?

For now that’s outside the scope, as the schemas used are thought to store Elixir/Erlang exceptions, and some features may not work as expected with JS exceptions. It is not impossible but not on the roadmap as for now.

@cmo

Can/will it handle errors from other applications or is it just for the single node?

As long as they are Elixir/Erlang applications and have the library installed, they can technically share the same database, at least in it’s current state. It may not be the recommended setup as you are going to see errors from other applications, but it can be done.

@jan-mb-me

I think it would be great to be able to delete errors, too, since they might contain data one doesn’t want to keep forever (f.i. due to GDPR and the like).

That’s definitively on the roadmap and will be released in a new version soon.

@shahryarjb

is there any security consideration to use lib for tracking the log especially any malicious command or XSS for example?

The library uses Phoenix and Ecto, and we are not using unescaped values anywhere, so the only thing to take care about is to put some protections on the UI to avoid anonymous people accessing it.