Skip to main content
Version: 6.1.0

Frequently Asked Questions

I am running an application with the N|Solid Runtime but the NSolid Pro UI says there are no processes connected?​

Without configuration to tell it where to send data, the N|Solid Runtime behaves no differently than the Node.js runtime. The minimum configuration required for it to activate and export data is one of the following addresses:

  • NSOLID_SAAS To connect to a N|Solid SaaS account.
  • NSOLID_COMMAND: Configures a connection to an on-premise N|Solid Console Server on your Enterprise account using the ZeroMQ protocol
  • NSOLID_GRPC: Configures a connection to an on-premise N|Solid Console Server on your Enterprise account using the gRPC protocol. Available in N|Solid 6.1.0 and later.
  • NSOLID_STATSD To send data to a StatsD endpoint.
  • NSOLID_OTLP To send OpenTelemetry traces to an OTLP endpoint.

For a step-by-step guide on setting up your environment check out our Configuration guide.

I can't find one or more features in NSolid​

NSolid supports Role Based Access Control. The role assigned to your user-profile may be configured to limit your access to a sub-set of NSolid features. Contact your organization's account administrator to see which permissions you may be missing. To learn how NodeSource's RBAC works and which permission are available, visit the RBAC section in the accounts docs.

How do I find a memory leak?​

Check out our How To guide aimed at walking through our various tools that can be used to locate and solve Memory Leaks in Node.js here.

Memory leaks can be difficult to find and address--our Services team is ready to help you today.

How do I improve performance? How do I reduce the number of processes I am running to save money?​

There are a number of types of performance issues N|Solid is primed to help with.

Event Loop pauses can cause brief spikes of latency resulting in bottlenecks or occasionally terrible response times. Read our How To guide for finding pauses in your event loop.

The V8 engine is fast, but it can only do one thing at a time--check out our How To Guide for an in-depth guide on how to find slow execution paths in your JavaScript code.

Garbage Collection due to memory leaks can be a performance killer. Check out our How To Guide for using our memory profiling tools.

And as always, if you need help--our Services team is ready to help you dive into finding and solving performance issues.

What version should I be using?​

If you have the choice, always select the most recently started Node.js LTS line. This will provide you with the longest possible support cycle before the LTS line rotates to a new version. If you are on an LTS line that is within 6 months of expiring, it is time to start the updating process now.

Let us know if you would like our team's help on moving your application to a modern version of Node.js.