Changelog
All notable changes to this project will be documented in this file. See Keep a CHANGELOG for how to update this file. This project adheres to Semantic Versioning.
[Unreleased]
[v0.10.0] - 2018-05-29
Changed
- Replace Poison with Jason for JSON encoding.
- Reduce the log level used for dev mode warning.
- Update dependenices.
Fixed
- Fix crashes caused by JSON encoding error, we now log an error when there is a JSON encoding error.
- Send notifications even when the stacktrace isn’t a list. Errors reported from the error logger can occasionally have a malformed stacktrace, which would raise another exception prevent the notification from being sent.
[v0.9.0] - 2018-03-21
Changed
- Use lazy logging within
Honeybadger.Client
, this allows compile time purging when the log level is set higher.
Fixed
- Fix a regression which was causing
Not Found (404)
errors to be reported. - Fix an issue caused by hackney because of unread response bodies.
[v0.8.0] - 2018-01-17
Added
- Include function arity in notice backtraces. For example, the reported method
would be
notify/3
instead ofnotify
. - Include function arguments in notice backtraces. This is disabled by default,
and can be enabled by setting
filter_args
tofalse
in configuration.
Changed
- Allow
handle_errors
fromHoneybadger.Plug
to be overridden.
Fixed
- Safely convert binary
:environment_name
values to an atom. If the environment was specified via{:system, "HONEYBADGER_ENV"}
and theHONEYBADGER_ENV
value didn’t already exist as an atom the app would fail to boot. - Ignore the absence of
HONEYBADGER_API_KEY
when running in an excluded env
[v0.7.0] - 2017-11-07
Added
- Increases the logging around client activity (honeybadger-io/honeybadger-elixir#20).
- Explicitly allow sending notices with strings and maps. For example, it is now
possible to send a
RuntimeError
by callingHoneybadger.notify("oops!")
. - Added Honeybadger test mix task which can be invoked using
mix honeybadger.test
Changed
- Switch from
GenEvent
to implementinggen_event
behaviour. - Remove
error_logger
backend on application stop. - Use the latest exception’s stacktrace whenever
notify
is called from atry
expression. - Namespace modules related to
Filter
andNoticeFilter
. This is largely an internal restructuring, but any custom filters that used theHoneybadger.FilterMixin
will need to specifyHoneybadger.Filter.Mixin
instead. - Drops
HTTPoison
in favor of directly usingHackney
, which gives us access to a connection pool. - Drops Meck and stubbing in favor of a local cowboy server (honeybadger-io/honeybadger-elixir#7).
- Starts a supervision tree with the client as a child.
- Report the controller and action name as component and action for phoenix apps
Fixed
- Filtering CGI data now respects the
filter_disable_url
setting. All path related fields (ORIGINAL_FULLPATH
,QUERY_STRING
,PATH_INFO
) are filtered now. - Get the environment directly from
Mix.env
and always compare the environment names as atoms (honeybadger-io/honeybadger-elixir#94). - Changes notify from a macro to a function.
- Stops spawning new tasks for every error, instead relying on async handling in the client (honeybadger-io/honeybadger-elixir#88).
[0.6.3] - 2017-05-04
Changed
- Removes metrics reporting.
Fixed
- Loosens httpoison dependency.
- Misc. bug fixes.
[0.6.2] - 2016-10-24
Added
- ability to customize error names/messages,
Fixed
- stops plug error notifications from being sent twice
- minor typo fixes
- dependency updates
[0.6.1] - 2016-08-02
Fixed
- Reformatting the plug environment data sent to Honeybadger.
[0.6.0] - 2016-07-22
Fixed
- This release removes warnings for Elixir 1.3.0 and covers v1.4.0-dev as of
2016-07-22. There was also a switch to using
:native
FromUnits
to match thePlug.Logger
usage of:erlang.convert_time_unit
. This maintains consistency betweenHoneybadger.Logger
andPlug.Logger
.
[0.5.0] - 2016-04-26
Added
- Honeybadger now collects successful response times, aggregates them and sends them to the Honeybadger API! You can see request metric data from the metrics tab on Honeybadger.io!
[0.4.0] - 2016-02-23
Changed
Due to the
Mix.env/0
function always being set toprod
for dependencies and Mix being compiled out of applications by exrm, we now require you to explicitly declare yourenvironment_name
for every environment in yourconfig.exs
files.Example:
# config/dev.exs config :honeybager, environment_name: :dev
Doing this will ensure you get accurate environment information for exceptions that happen at runtime as well as compile time. You can also set the
environment_name
setting aMIX_ENV
environment variable.Example: $ MIX_ENV=prod mix phoenix.server
Note: setting
environment_name
in your config files takes higher precedence than theMIX_ENV
environment variable.
[0.3.1] - 2016-02-04
Fixed
- Fix a bug where notifications reported by the
error_logger
were not sending the the context