Platform Docs
Agent Docs
Support Docs
Troubleshooting
Troubleshooting
Not seeing data? Email support@scoutapm.com with:
- A link to your app within Scout (if applicable)
- Your NodeJS version
- The name of the framework and version you are trying to instrument, e.g. Express 4.17.0
- Scout debug logs
We typically respond within a couple of hours during the business day.
Core-Agent
In some cases, debug level logs from the Node agent may not be enough, and trace level core-agent logs may be needed.
Debug Logs
To set Scout’s log level to debug, set the SCOUT_LOG_LEVEL configuration to debug — nothing is logged at any level until this is set. Start here; see Logging for output format and what gets logged.
Not Connecting to the Core Agent?
Connection failures log at error (so they show at any log level) as:
[scout] failed to connect to agent at [/tmp/scout_apm_core/...]: <error message>
Common causes: coreAgentDownload/coreAgentLaunch disabled without the core agent already running, a permissions issue on the socket directory (core_agent_dir / core_agent_permissions in Configuration), or the binary failing to start for your platform — check trace level core-agent logs.
Per-integration issues (BullMQ, Sequelize, NestJS, Express, Log Management) are covered on each integration’s own docs page.