A backend API can appear healthy while users still experience slow responses. If a Node.js service sits between the browser and that API, engineers also need to see what happened in the Node.js application.
JENNIFER’s Node.js agent brings that tier into its transaction-focused APM workflow. Customers increasingly use Node.js and Next.js in backend-for-frontend architectures. Monitoring this tier gives teams another place to examine a request that the backend metrics alone cannot explain.
Examine the request inside the application
Node.js handles many clients with a small number of threads. JavaScript callbacks run on the event loop, while a worker pool handles certain expensive operations. A long-running callback can delay other clients, so efficient concurrency depends in part on keeping that work short.
A slow request may involve application work, a wait for a dependency or contention affecting other requests. Establish which requests slowed down and whether the pattern was isolated or widespread before choosing what to inspect.
JENNIFER’s X-View plots completed transactions by response time. Select an affected request from that distribution and use transaction profiling to examine its execution information.
For a backend-for-frontend service, begin with a familiar endpoint under representative traffic. Compare a normal request with a slow one, then record the differences supported by the transaction data. The application and operations teams can use that comparison to discuss what needs further investigation.
Confirm compatibility
The Node.js agent supports Linux x64 and ARM64 for GNU environments with GLIBC 2.15 or later, and for musl environments. JENNIFER Server 5.6.5.7 or later is required.
The documented runtime minimum is Node.js 18.0 for CommonJS. ESM requirements are listed as 18.19 or later, or 20.6 or later. These are compatibility thresholds, not a recommendation to deploy an older runtime. The Node.js project recommends Active LTS or Maintenance LTS releases for production; check the lifecycle when selecting a version.
ARM64 support arrived in Node.js agent 5.6.5.6 on August 19, 2026. If you use ARM-based infrastructure, check that the installed agent version supports the deployment architecture.
Load the agent before application modules
Installation uses the @jennifersoft/jennifer5-instrumentation package. Connection and logging settings can be supplied through jennifer.toml and supported environment variables.
The agent must load before the modules it instruments. For ESM applications, preload the agent through command-line options or NODE_OPTIONS. Importing the agent from the entry file can happen too late for modules that have already loaded. Choose the startup method that matches your deployment.
Test a representative service in a test environment before expanding the rollout. Exercise normal requests, deliberate errors and a controlled slow path, and check the evidence each produces. Keep those cases for later runtime, framework or packaging changes. These cases give the team a repeatable way to check whether the expected transaction data is being collected.