Filtering sensitive data

You have complete control over the data that Honeybadger reports when an error occurs. Before data is sent to Honeybadger, it is passed through a filter to remove sensitive fields and do other processing on the data. The default configuration is equivalent to:

config :honeybadger,
  filter: Honeybadger.Filter.Default,
  filter_keys: [:password, :credit_card]

This will remove any entries in the context, session, cgi_data and params that match one of the filter keys. The filter is case insensitive and matches atoms or strings.

If Honeybadger.Filter.Default does not suit your needs, you can implement your own filter. See the Honeybadger.Filter.Mixin module doc for details on implementing your own filter.

Filtering arguments

By default, Honeybadger includes function arguments in backtraces (for example, the arguments passed to a function that raised a FunctionClauseError). Arguments are not passed through filter_keys. To remove them from all backtraces, set filter_args to true:

config :honeybadger, filter_args: true