Troubleshooting¶ Info This is a non-exhaustive list of problems or troubleshooting strategies. If you need help please email us at firstname.lastname@example.org or through our web chat. Please don't hesitate, we're here to help! Increase log verbosity¶ The Sqreen agent can log messages to a text file. These messages contain warnings about possible abnormal behavior and describe some actions the agent is executing. Two values in Sqreen configuration control the logging: Env variable name Role Default value Options SQREEN_LOG_LOCATION Specify a custom file to write Sqreen logs The terminal Custom filepath SQREEN_LOG_LEVEL Sqreen logging level WARN INFO, DEBUG The INFO level is verbose but still suitable for production environments. Only use DEBUG for short periods of time due to the amount of data it generates. Avoid Sqreen exceptions on New Relic dashboard¶ By default Sqreen prevents his own exceptions from being displayed on New Relic dashboard. However, if you enable your own server side configuration for filtering issues, it will disable this default behavior. To filter Sqreen exceptions from New Relics: Follow the tutorial of New Relic explaining how to ignore errors using server-side configuration in the UI. Add Sqreen exceptions used to block a request sqreen.exceptions:RequestBlocked sqreen.exceptions:AttackBlocked sqreen.exceptions:ActionBlock sqreen.exceptions:ActionRedirect User identifications are not reported with Django¶ Sqreen automatically reports user authentications when your application uses Django standard authentication mechanism. However, if you chose to start Sqreen from code rather than from the CLI, this feature may not work. If you experience such issue, it is recommended to start sqreen from the CLI. If the issue still persists, please don't hesitate to contact us.