Troubleshooting¶ Info This is a non-exhaustive list of problems and troubleshooting strategies. If you need help please email us at firstname.lastname@example.org or contact us 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. DEBUG should only be used for short periods of time due to the amount of data it generates. Sqreen is not showing any protected requests but my application has traffic¶ Ensure the main module of your application starts with the following code: require('sqreen') Sqreen does not show anything under the 'DB requests' field¶ This can come from two issues: The application does not have the Sqreen module as the first module required. Ensure that require('sqreen') is the first statement executed by the application. Sqreen does not suppor the database. Please contact us to discuss this topic. Sqreen does not log in¶ Run the troubleshooting script sqreen-check-network: At the root of the project, run the following: $ node ./node_modules/.bin/sqreen-check-network Or if using a proxy: $ node ./node_modules/.bin/sqreen-check-network -p <proxy_url> The script tries to reach Sqreen server to ensure it is accessible.