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)
belaustegui
jaimeiniesta
ivanhercaz
I am already working on the suggestion I did some days ago:
https://github.com/elixir-error-tracker/error-tracker/issues/54
If everything goes well, I think I could release a first release of the package this weekend. I will notice you!
7
jaimeiniesta
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.
10
belaustegui
Hi all!
We’ve just pushed a new release that includes support for reporting LiveComponent errors. Get it while it is fresh! 
4
cgraham
odarriba
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 
1
odarriba
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
trueby 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 
6
belaustegui
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
4
mxgrn
This would be a great start! Looking forward to this, so I could plug ErrorTracker to a Telegram bot for real-time alerts.
1