Use glitchtip instead of sentry

config/config.exs

@@ -158,6 +158,7 @@ config :sasl, sasl_error_logger: false
 # Configures Elixir's Logger
 config :logger, :console,
   format: {Sanbase.Utils.JsonLogger, :format},
+  backends: [:console, Sentry.LoggerBackend],
   metadata: [:request_id, :api_token, :user_id, :remote_ip, :complexity, :query, :san_balance],
   handle_otp_reports: true,
   handle_sasl_reports: true

lib/sanbase/application/application.ex

@@ -46,6 +46,10 @@ defmodule Sanbase.Application do
     # Note: Sentry.LoggerBackend now allows to send non-exception errors to sentry, too.
     # This is not enabled yet.
     {:ok, _} = Logger.add_backend(Sentry.LoggerBackend)
+
+    # Glitchtip handler: This library comes with a :logger handler to capture error messages coming from process crashes. To enable this, add the handler when your application starts:
+    :logger.add_handler(:sentry_handler, Sentry.LoggerHandler, %{})
+
     Supervisor.start_link(children, opts)
   end
 

lib/sanbase_web/router.ex

@@ -1,6 +1,7 @@
 defmodule SanbaseWeb.Router do
   # credo:disable-for-this-file Credo.Check.Refactor.ModuleDependencies
   use SanbaseWeb, :router
+  use Sentry.PlugCapture
 
   pipeline :admin_pod_only do
     plug(SanbaseWeb.Plug.AdminPodOnly)

lib/sanbase_web/sanbase_web.ex

@@ -57,6 +57,8 @@ defmodule SanbaseWeb do
         layout: {SanbaseWeb.Layouts, :app}
 
       unquote(html_helpers())
+
+      on_mount Sentry.LiveViewHook
     end
   end