Skip to main content
Version: 6.x (latest)

Frequently asked questions

Answers to common questions about connecting the N|Solid Runtime, finding features, fixing performance problems, and choosing a Node.js version.

My application runs with the N|Solid Runtime, but the N|Solid Console shows no connected processes. Why?​

Until you tell it where to send data, the N|Solid Runtime behaves the same as Node.js. To activate it and export data, set at least one of these:

  • NSOLID_SAAS: connects to your N|Solid SaaS account.
  • NSOLID_COMMAND: connects to a self-hosted N|Solid Console over ZeroMQ.
  • NSOLID_GRPC: connects to a self-hosted N|Solid Console over gRPC. If the Console doesn't use TLS, also set NSOLID_GRPC_INSECURE=1.
  • NSOLID_STATSD: sends metrics to a StatsD endpoint.
  • NSOLID_OTLP: exports metrics and traces to an OpenTelemetry (OTLP) endpoint, or to Datadog, Dynatrace, or New Relic (these three also need NSOLID_OTLP_CONFIG). Traces also require NSOLID_TRACING_ENABLED=1.
note

If you set both NSOLID_SAAS and NSOLID_COMMAND, NSOLID_COMMAND takes precedence and the SaaS token is ignored. This is a common reason processes don't appear in N|Solid SaaS.

For step-by-step setup, see Runtime configuration.

I can't find one or more features in N|Solid. Why?​

N|Solid supports role-based access control (RBAC). Your role may limit your access to some N|Solid features. Contact your organization's account administrator to find out which permissions you're missing. To learn how RBAC works and which permissions are available, see RBAC.

How do I find a memory leak?​

See Find a memory leak, which walks through the N|Solid tools for locating and fixing memory leaks in Node.js.

Memory leaks can be hard to find and fix. The NodeSource Services team can help.

How do I improve performance, or run fewer processes to save money?​

N|Solid can help with several kinds of performance problems:

  • Event loop pauses can cause latency spikes, bottlenecks, and occasionally very slow responses. See Find event loop pauses.
  • Slow JavaScript: V8 is fast, but it runs one thing at a time on each thread. See Optimize performance with CPU profiles to find slow execution paths in your code.
  • Garbage collection caused by memory leaks can seriously hurt performance. See Find a memory leak to use the N|Solid memory profiling tools.

If you need help finding and fixing performance issues, the NodeSource Services team can help.

Which version should I use?​

N|Solid currently supports these Node.js LTS lines:

  • Node.js 24 (Krypton): Active LTS. Use it for new projects.
  • Node.js 22 (Jod): Maintenance LTS, with end of life on April 30, 2027.

Node.js 20 (Iron) reached end of life on April 30, 2026, and no longer receives N|Solid releases.

If you have the choice, use the most recent Node.js LTS line. It gives you the longest support period before the line reaches end of life. If your LTS line is within six months of its end of life, start upgrading now.

The NodeSource Services team can help you move your application to a current version of Node.js.

NodeSource Support