v1.0.0 Released!
I’m excited to announce the release of DiscoLog v1.0.0! This update introduces two optional features:

• Presence Status – Allows your bot to appear online, representing your node in Discord.
• Go To Repo – Provides a direct link to GitHub (or a similar platform) to check the code where an error was triggered.

Additionally, it’s now possible to use the Discord client for ad hoc usage, though examples are not yet available.

New Demo: I’ve created a YouTube video showcasing the Presence Status and Go To Repo features

Huge thanks to @martosaur for implementing the Presence Status feature and refactoring the code to support ad hoc usage

I released disco_log v0.5.1:

• it fixes an issue that was crashing the logger handler because some elixir type can’t be serialized as is

Meanwhile I have been using it in production on multiples side projects.
I’m very satisfied with the error tracking !

Next features on my list are:

• Go to code the idea is to be able to click the occurrence and to go to the relevant github code on the specfic branch / tag
• Active presence message to make the bot display some info about the node

Wow that’s amazing, thanks for putting it together!

I’m not sure what value integrating with Tower brings. DiscoLog already has a logger handler, so after configuring the Logger backend, doing Logger.error(some_exception) reports the error to the Discord backend. For telemetry, I also hook them and report separately. Adding DiscoLog to your app only requires modifying the config, with no additional code changes. Additionally, we have duplicate logic in event.ex, which I need for error tracking.

I’ve only started using it but it’s been great so far. I like how setting up logging for multiple projects/environment is a matter of configuring category_id/channel_id.

I think I may have preferred starting DiscoLog under the application’s supervision tree and explicitly configuring logger handlers, but it might be too early to say