By default AppSignal gathers relevant data for errors and performance measurements to help you find the cause of the issue. Sometimes you need more information, app specific data or a custom request header your app uses.
You can configure AppSignal to gather more, or less, information than it does by default by tagging your transactions and configuring the request headers, parameter filtering, etc.
By default AppSignal does not gather all request headers from a request. We only include non user identifiable request headers. This is so you and AppSignal are GDPR compliant by default. If you are missing some headers you really need for your app you can customize which request headers are collected in Ruby and Elixir.
If you use any framework with automatic parameter filtering, AppSignal will use the parameter filtering of the framework to filter the parameters. This can be further customized with our parameter filtering in Ruby and Elixir.
AppSignal gathers session data for requests by default. This may help you track down errors or performance issues that were caused by some session data your app is using. However, your app's session data may contain sensitive user information which you do not want to the AppSignal servers.
Namespaces allow grouping of actions. By default AppSignal uses the "web", "background" and "frontend" namespaces to group transactions. It's possible to create a custom namespace such as "admin", "api" to group controllers in the same namespace.
The grouped actions in the namespace can be configured with their own notification defaults, allowing a critical namespace to always notify about errors, while the "web" namespace does not. It's also possible to configure the AppSignal integration to ignore a namespace to
Read more about namespaces in the namespaces section.