defmodule ErrorTracker do @moduledoc """ En Elixir-based built-in error tracking solution. The main objectives behind this project are: * Provide a basic free error tracking solution: because tracking errors in your application should be a requirement for almost any project, and helps to provide quality and maintenance to your project. * Be easy to use: by providing plug-and-play integrations, documentation and a simple UI to manage your errors. * Be as minimalistic as possible: you just need a database to store errors and a Phoenix application if you want to inspect them via web. That's all. ## Requirements ErrorTracker requires Elixir 1.15+, Ecto 3.11+, Phoenix LiveView 0.19+, and PostgreSQL, MySQL/MariaDB or SQLite3 as database. ## Integrations We currently include integrations for what we consider the basic stack of an application: Phoenix, Plug, and Oban. However, we may continue working in adding support for more systems and libraries in the future if there is enough interest from the community. If you want to manually report an error, you can use the `ErrorTracker.report/3` function. ## Context Aside from the information about each exception (kind, message, stack trace...) we also store contexts. Contexts are arbitrary maps that allow you to store extra information about an exception to be able to reproduce it later. Each integration includes a default context with useful information they can gather, but aside from that, you can also add your own information. You can do this in a per-process basis or in a per-call basis (or both). There are some requirements on the type of data that can be included in the context, so we recommend taking a look at `set_context/1` documentation. **Per process** This allows you to set a general context for the current process such as a Phoenix request or an Oban job. For example, you could include the following code in your authentication Plug to automatically include the user ID in any error that is tracked during the Phoenix request handling. ```elixir ErrorTracker.set_context(%{user_id: conn.assigns.current_user.id}) ``` **Per call** As we had seen before, you can use `ErrorTracker.report/3` to manually report an error. The third parameter of this function is optional and allows you to include extra context that will be tracked along with the error. ## Breadcrumbs Aside from contextual information, it is sometimes useful to know in which points of your code the code was executed in a given request / process. Using breadcrumbs allows you to add that information to any error generated and stored on a given process / request. And if you are using `Ash` or `Splode` their exceptions' breadcrumbs will be automatically populated. If you want to add a breadcrumb in a point of your code you can do so: ```elixir ErrorTracker.add_breadcrumb("Executed my super secret code") ``` Breadcrumbs can be viewed in the dashboard on the details page of an occurrence. """ @typedoc """ A map containing the relevant context for a particular error. """ @type context :: %{(String.t() | atom()) => any()} @typedoc """ An `Exception` or a `{kind, payload}` tuple compatible with `Exception.normalize/3`. """ @type exception :: Exception.t() | {:error, any()} | {Exception.non_error_kind(), any()} import Ecto.Query alias ErrorTracker.Error alias ErrorTracker.Occurrence alias ErrorTracker.Repo alias ErrorTracker.Telemetry @doc """ Report an exception to be stored. Returns the occurrence stored or `:noop` if the ErrorTracker is disabled by configuration the exception has not been stored. Aside from the exception, it is expected to receive the stack trace and, optionally, a context map which will be merged with the current process context. Keep in mind that errors that occur in Phoenix controllers, Phoenix LiveViews and Oban jobs are automatically reported. You will need this function only if you want to report custom errors. ```elixir try do # your code catch e -> ErrorTracker.report(e, __STACKTRACE__) end ``` ## Exceptions Exceptions can be passed in three different forms: * An exception struct: the module of the exception is stored along with the exception message. * A `{kind, exception}` tuple in which case the information is converted to an Elixir exception (if possible) and stored. """ @spec report(exception(), Exception.stacktrace(), context()) :: Occurrence.t() | :noop def report(exception, stacktrace, given_context \\ %{}) do {kind, reason} = normalize_exception(exception, stacktrace) {:ok, stacktrace} = ErrorTracker.Stacktrace.new(stacktrace) {:ok, error} = Error.new(kind, reason, stacktrace) context = Map.merge(get_context(), given_context) breadcrumbs = get_breadcrumbs() ++ exception_breadcrumbs(exception) if enabled?() && !ignored?(error, context) do sanitized_context = sanitize_context(context) upsert_error!(error, stacktrace, sanitized_context, breadcrumbs, reason) else :noop end end @doc """ Marks an error as resolved. If an error is marked as resolved and it happens again, it will automatically appear as unresolved again. """ @spec resolve(Error.t()) :: {:ok, Error.t()} | {:error, Ecto.Changeset.t()} def resolve(error = %Error{status: :unresolved}) do changeset = Ecto.Changeset.change(error, status: :resolved) with {:ok, updated_error} <- Repo.update(changeset) do Telemetry.resolved_error(updated_error) {:ok, updated_error} end end @doc """ Marks an error as unresolved. """ @spec unresolve(Error.t()) :: {:ok, Error.t()} | {:error, Ecto.Changeset.t()} def unresolve(error = %Error{status: :resolved}) do changeset = Ecto.Changeset.change(error, status: :unresolved) with {:ok, updated_error} <- Repo.update(changeset) do Telemetry.unresolved_error(updated_error) {:ok, updated_error} end end @doc """ Mutes the error so new occurrences won't send telemetry events. When an error is muted: - New occurrences are still tracked and stored in the database - No telemetry events are emitted for new occurrences - You can still see the error and its occurrences in the web UI This is useful for noisy errors that you want to keep tracking but don't want to receive notifications about. """ @spec mute(Error.t()) :: {:ok, Error.t()} | {:error, Ecto.Changeset.t()} def mute(error = %Error{}) do changeset = Ecto.Changeset.change(error, muted: true) Repo.update(changeset) end @doc """ Unmutes the error so new occurrences will send telemetry events again. This reverses the effect of `mute/1`, allowing telemetry events to be emitted for new occurrences of this error again. """ @spec unmute(Error.t()) :: {:ok, Error.t()} | {:error, Ecto.Changeset.t()} def unmute(error = %Error{}) do changeset = Ecto.Changeset.change(error, muted: false) Repo.update(changeset) end @doc """ Sets the current process context. The given context will be merged into the current process context. The given context may override existing keys from the current process context. ## Context depth You can store context on more than one level of depth, but take into account that the merge operation is performed on the first level. That means that any existing data on deep levels for he current context will be replaced if the first level key is received on the new contents. ## Content serialization The content stored on the context should be serializable using the JSON library used by the application (usually `Jason`), so it is rather recommended to use primitive types (strings, numbers, booleans...). If you still need to pass more complex data types to your context, please test that they can be encoded to JSON or storing the errors will fail. In the case of `Jason` that may require defining an Encoder for that data type if not included by default. """ @spec set_context(context()) :: context() def set_context(params) when is_map(params) do current_context = Process.get(:error_tracker_context, %{}) Process.put(:error_tracker_context, Map.merge(current_context, params)) params end @doc """ Obtain the context of the current process. """ @spec get_context() :: context() def get_context do Process.get(:error_tracker_context, %{}) end @doc """ Adds a breadcrumb to the current process. The new breadcrumb will be added as the most recent entry of the breadcrumbs list. ## Breadcrumbs limit Breadcrumbs are a powerful tool that allows to add an infinite number of entries. However, it is not recommended to store errors with an excessive amount of breadcrumbs. As they are stored as an array of strings under the hood, storing many entries per error can lead to some delays and using extra disk space on the database. """ @spec add_breadcrumb(String.t()) :: list(String.t()) def add_breadcrumb(breadcrumb) when is_binary(breadcrumb) do current_breadcrumbs = Process.get(:error_tracker_breadcrumbs, []) new_breadcrumbs = current_breadcrumbs ++ [breadcrumb] Process.put(:error_tracker_breadcrumbs, new_breadcrumbs) new_breadcrumbs end @doc """ Obtain the breadcrumbs of the current process. """ @spec get_breadcrumbs() :: list(String.t()) def get_breadcrumbs do Process.get(:error_tracker_breadcrumbs, []) end defp enabled? do !!Application.get_env(:error_tracker, :enabled, true) end defp ignored?(error, context) do ignorer = Application.get_env(:error_tracker, :ignorer) ignorer && ignorer.ignore?(error, context) end defp sanitize_context(context) do filter_mod = Application.get_env(:error_tracker, :filter) if filter_mod, do: filter_mod.sanitize(context), else: context end defp normalize_exception(%struct{} = ex, _stacktrace) when is_exception(ex) do {to_string(struct), Exception.message(ex)} end defp normalize_exception({kind, ex}, stacktrace) do case Exception.normalize(kind, ex, stacktrace) do %struct{} = ex -> {to_string(struct), Exception.message(ex)} payload -> {to_string(kind), safe_to_string(payload)} end end defp safe_to_string(term) do to_string(term) rescue Protocol.UndefinedError -> inspect(term) end defp exception_breadcrumbs(exception) do case exception do {_kind, exception} -> exception_breadcrumbs(exception) %{bread_crumbs: breadcrumbs} -> breadcrumbs _other -> [] end end defp upsert_error!(error, stacktrace, context, breadcrumbs, reason) do status_and_muted_query = from e in Error, where: [fingerprint: ^error.fingerprint], select: {e.status, e.muted} {existing_status, muted} = case Repo.one(status_and_muted_query) do {existing_status, muted} -> {existing_status, muted} nil -> {nil, false} end {:ok, {error, occurrence}} = Repo.transaction(fn -> error = ErrorTracker.Repo.with_adapter(fn :mysql -> Repo.insert!(error, on_conflict: [set: [status: :unresolved, last_occurrence_at: DateTime.utc_now()]] ) _other -> Repo.insert!(error, on_conflict: [set: [status: :unresolved, last_occurrence_at: DateTime.utc_now()]], conflict_target: :fingerprint ) end) occurrence = error |> Ecto.build_assoc(:occurrences) |> Occurrence.changeset(%{ stacktrace: stacktrace, context: context, breadcrumbs: breadcrumbs, reason: reason }) |> Repo.insert!() {error, occurrence} end) %Occurrence{} = occurrence occurrence = %{occurrence | error: error} # If the error existed and was marked as resolved before this exception, # sent a Telemetry event # If it is a new error, sent a Telemetry event case existing_status do :resolved -> Telemetry.unresolved_error(error) :unresolved -> :noop nil -> Telemetry.new_error(error) end Telemetry.new_occurrence(occurrence, muted) occurrence end end