Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
47 lines (32 sloc) 1.79 KB
title: "Parameter filtering"
In most apps, at least some of the data that is sent to the application is sensitive or personally identifiable information that should not leave the network. To prevent AppSignal from storing this data the Ruby gem should be configured to not send this data at all or filter out specific values.
We support two ways of filtering parameters from being sent to AppSignal. Either with the built-in AppSignal parameter filtering or, when using Phoenix, using the Phoenix parameter filtering.
!> **Warning**: Do not send personal data to AppSignal. If your parameters or session data contain personal data, please use filtering to avoid sending this data to AppSignal.
## Table of Contents
- [AppSignal parameter filtering](#appsignal-parameter-filtering)
- [Processor parameter filtering](#processor-parameter-filtering)
- [Phoenix's filter_parameters configuration](#phoenix-filter_parameters-configuration)
## AppSignal parameter filtering
If you're not using Phoenix, or want to filter parameters without changing the
Phoenix.Logger's configuration, you can set up filtered parameters in the
AppSignal configuration file.
# config/appsignal.exs
config :appsignal, :config,
filter_parameters: ["password", "secret"]
### Processor parameter filtering
<%= partial "shared/processor_filtering" %>
## Phoenix filter_parameters configuration
You can use Phoenix's parameter filtering, which is used to keep sensitive
information from the logs. AppSignal will also follow these filtering rules.
# config/config.exs
config :phoenix,
:filter_parameters, ["password", "secret"]
If `:filter_parameters` is not set, Phoenix will default to `["password"]`. This
means that a Phoenix app will not send any passwords to AppSignal without any