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

ghannam80 · August 5, 2024, 8:39am

I just installed it in one of the application and this project is very promising .

Testing the UI a quick feature came to my mind to have some integration with the service management tool used for error/bugs tracking such as github to follow related SDLC processes for bug fixing

stevegrossi · August 5, 2024, 2:17pm

Thanks, will do. And I’m deploying as a release, not with mix.

belaustegui · August 6, 2024, 1:41pm

We have just released v0.1.2 which solves this issue. Thanks for the detailed error reports and stacktraces.

odarriba · August 7, 2024, 9:47am

Update on notifications!

We are working right now on adding Telemetry events (we love Telemetry, is the base of this project), so anyone can attach handlers to send notifications on their preferred way (email, slack, text messages, etc.).

It may not be as plug and play as many expect, but it is the most flexible way we could find without building a full notification system (which is complex), and it lets the developer to build their own rules and use their preferred notification channels.

It doesn’t mean that we will never build notifications in the library, just not now. But the options to be able to get notifications will arrive soon (hopefully next version)

ghannam80 · August 7, 2024, 10:22am

hopefully it will be possible to integrate from the current UI where you select the error and decide to send this error to your notification channel “Could be a bug tracking system like github”

odarriba · August 12, 2024, 5:30pm

Version 0.2.0 is out!

This update includes several improvements to the library:

SQLite 3 compatibility (including a better way to track database schema versions)
Telemetry events - can be used to integrate your own notifications
UI improvements - more refined styles and UX
A better test suite, including testing in both RDBMS and different Elixir/Erlang versions in the CI

GitHub release
Hex.pm release

If you are already using the library: there is a new version of the DB schema, so you need to create a new migration to migrate to version 2.

We hope this version fixes some of the issues reported any feedback is welcome!

Wojciech · August 12, 2024, 9:48pm

Amazing work!

I’m trying to build a website and i don’t want to connect it to any external services so your project is really useful to me

sevenseacat · August 14, 2024, 2:54am

I’ve been using this and I really like it, it’s great

A bit confused about needing to generate a new migration after updating to v0.2.0 though. I’ve already been running it in prod without doing so, and creating an ew migration with the same migration functions of:

def up, do: ErrorTracker.Migration.up()
def down, do: ErrorTracker.Migration.down()

Doesn’t make any changes to the schema when running them again after updating.

Additionally, having the same function ErrorTracker.Migration.down() in two diffirent migrations can’t be rolled back twice - the second raises an error because the tables were already dropped from the first down.

Do we need to put migration version numbers in the up/down calls, like Oban does I think when migrating between versions?

odarriba · August 14, 2024, 1:56pm

That makes sense, because V02 in PostgreSQL systems creates a new table to store meta information and moves the information about which migration version is the latest to that table.

Tables and structures used by ErrorTracker are not changed - we may use the new error_tracker_meta table in the future, but not now - so the system will work without that migration but it is really recommended to stay up to date.

As we migrated how the schema version number is stored - and it is an important information to take into account on the migration process - that migration is different to others, but we have tested it and should work as expected.

That’s the issue! We should have included that in the release message, but the idea is to have it like:

defmodule MyApp.Repo.Migrations.UpdateErrorTrackerToV02 do
  use Ecto.Migration

  def up, do: ErrorTracker.Migration.up(version: 2)
  def down, do: ErrorTracker.Migration.down(version: 2)
end

which produces this output when migrating:

15:42:49.730 [info] == Running 20240814134232 MyApp.Repo.Migrations.UpdateErrorTrackerToV02.up/0 forward

15:42:49.764 [info] create table if not exists public.error_tracker_meta

15:42:49.800 [info] execute "COMMENT ON TABLE \"public\".error_tracker_errors IS ''"

15:42:49.801 [info] execute "INSERT INTO public.error_tracker_meta (key, value)\nVALUES ('migration_version', '2'), ('migration_timestamp', '1723642969')\nON CONFLICT (key) DO UPDATE SET value = EXCLUDED.value\n"

15:42:49.807 [info] == Migrated 20240814134232 in 0.0s

in the way you created it works fine if you go up, but on the down it will remove all migrations, so reverting the other one will result in errors because tables don’t exist anymore.

Yes!

Hope it helps!! If you have more issues please feel free to open an issue and we can find a solution there.

cgraham · August 19, 2024, 4:42pm

- user error on the bug.

Thanks for making this! I have had sentry on my to do list but will do this first. Just got it working and already it is reporting an error! Will have to remember to keep checking it

Thanks again! So far so good!

jaimeiniesta · August 21, 2024, 11:12am

Hey, this looks awesome and I’m willing to try it!

My only concern is whether this can be used in an app where I’m already using AppSignal or Sentry. Can you think of any incompatibilities?

belaustegui · August 21, 2024, 11:33am

ErrorTracker just attaches to some Telemetry events and does its own thing. There shouldn’t be any problems when using it along AppSignal or Sentry. (We haven’t tested it, though)

jaimeiniesta · August 21, 2024, 12:30pm

Thanks, that sounds great, there shouldn’t be any problem but I’ll report if I find any.

ivanhercaz · August 22, 2024, 12:41pm

I am already working on the suggestion I did some days ago:

github.com/elixir-error-tracker/error-tracker

Notificate errors by email or Telegram

opened 08:33AM - 19 Aug 24 UTC

closed 01:30PM - 19 Aug 24 UTC

ivanhercaz

Hi! First of all, just to say thank you all for this awesome and really great p…roject that ease to track errors without building a heavy infrastructure and a lot of configuration. Congratulations! It works really nice just installing it and with the initial configuration steps you give in the documentation. I am really interested in the notification of errors, because it can be really useful. I will implement it in a project handling the events emitted by [`ErrorTracker.Telemetry`](https://hexdocs.pm/error_tracker/ErrorTracker.Telemetry.html). I just want to know if you are interested in having it implemented in ErrorTracker or if you prefer to keep it out by the moment: 1. If you want it implemented in ErrorTracker, I can directly fork the project and start from there following your conventions, etc. 2. If you want it outside of ErrorTracker, I will probably create a simple and easy package that implement this feature. In case of 2, I would like to confirm if you agree with naming the package using `error_tracker_` prefix. In any case, 1 or 2, my idea and the roadmap in my head (I have not draw it yet!) is: 1. Implement the handling of events. 2. Let the user the possibility to send notifications by email. 3. ... and then by Telegram. I really prefer 3, because I use it more than the email, but I think it I will need to research and study more the implementation of that part. Of course, any advice you can give is more than welcome! So I am going to wait for you answers ❤️, I am no in any hurry, so I can do it with calm in any of the cases. Again, thank you very much for free and maintain this project! Regards

If everything goes well, I think I could release a first release of the package this weekend. I will notice you!

jaimeiniesta · August 24, 2024, 9:49am

Hey ErrorTracker team, thanks a lot for your effort in putting this together! I already fixed an error thanks to your library

Please consider adding a way to sponsor the project, it will surely be well-received by the community.

belaustegui · September 2, 2024, 4:19pm

Hi all!

We’ve just pushed a new release that includes support for reporting LiveComponent errors. Get it while it is fresh!

cgraham · September 5, 2024, 10:09pm

Any way you can support have error_tracker support liveview 1.0.0 and its RCs?

Thanks!

odarriba · September 5, 2024, 10:49pm

The spec is currently prepared for 1.0.0 final release. We can take a look at supporting RC, but in the meanwhile you can use override: true to ignore the requirements.

I will look into this to see if we can solve it for the next release to avoid having to override a dependency

odarriba · September 8, 2024, 10:41am

Hello!

We have just released v0.2.6.

It includes some exciting new features:

Ignorer: you can now create a custom module to decide if you want the ErrorTracker to store a given exception or not.
Pruner: a plug-in that automatically prune errors from the database after they have been resolved for some time.
Global enable configuration flag: set to true by default, it allows to enable or disable error tracking globally. It is perfect to avoid populating your database with errors in development, for example.

Note: this release includes a new schema migration that improves pruning performance (the new schema version to migrate is version: 3), so you need to migrate your system to perform this update! It applies to both PostgreSQL and SQLite systems.

Thanks to everyone who use the ErrorTracker and add issues with ideas and improvements

belaustegui · September 11, 2024, 3:44pm

Hi all!

We have just released v0.3.0 with a few exciting new features:

Support for MySQL and MariaDB. ErrorTracker now support all major open source relational database engines (PostgreSQL and SQLite were already supported).
Improved error grouping in the Oban integration. Previously errors from different Oban workers could be incorrectly grouped together.

Thanks to everyone who uses the ErrorTracker and improves it either by opening issues or pull requests