Thanks, will do. And I’m deploying as a release, not with mix.
stevegrossi
odarriba
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)
5
ghannam80
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”
0
odarriba
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
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!
10
Wojciech
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
1
sevenseacat
Author of Ash Framework
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?
0
odarriba
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.
6
cgraham
- 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!
1
jaimeiniesta
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?
1