The Node.js data collector can provide you with visibility and control of your Node.js applications, and help you ensure optimal performance and efficient use of resources. You can reduce and prevent application crashes and slowdowns around the clock, as the data collector assists you in detecting, diagnosing and isolating performance issues.
The Node.js data collector helps you to manage the performance and availability of the following:
This data collector can be configured to connect to the Cloud App Management server, or the IBM Cloud Application Performance Management (Cloud APM v8) server.
The Node.js data collector is published to npm already. You can find it in ibmapm.
When the data collector is configured to connect to the Cloud App Management server, you can use it to monitor both the Node.js applications in IBM Cloud Private and on-premises Node.js applications.
To monitor a Node.js applications running as a container in IBM Cloud Private, follow the instructions as documented in Configuring the data collector for applications in IBM Cloud Private
To monitor a Node.js applications which created by Microclimate running as a container in IBM Cloud Private, follow the instructions as documented in Configuring the data collector for Microclimate based applications in IBM Cloud Private
To monitor on-premises Node.js applications, follow the instructions as documented in Configuring on-premises Node.js applications monitoring using the Cloud App Management server.
You can also use the supported variables to change the default behavior of data collection. For more information, see Advanced configuration.
To disable the Node.js data collector, roll back the changes that you have made to your application and then update the application deployment. For more information, see Disabling the Node.js data collector.
You can configure the Node.js data collector using the Cloud APM v8 server to monitor your Node.js applications running locally or in IBM Cloud Private.
Before configure the Node.js DC to connect to the Cloud APM v8 server, you need to get the configuration information from APM server first, see Get the APM configuration information.
You can also use the supported variables to change the default behavior of data collection. For more information, see Advanced configuration.
Find below some possible problem scenarios and corresponding diagnostic steps.
AssertionError [ERR_ASSERTION]: Multiple versions of Node Application Metrics are being initialized.
This version 3.1.3 is incompatible with already initialized
version 4.0.0.
This error indicates there are multiple versions of Node Application Metrics are being installed in your application. The appmetrics version 4.0.0 or later is required for Node.js data collector. If your application requires the module such as: appmetrics-dash, appmetrics-prometheus or appmetrics-zipkin which require the appmetrics, please make sure these modules has right version which requiring the appmetrics 4.0.0 or later.
"appmetrics-dash": "^4.0.0",
"appmetrics-prometheus": "^2.0.0",
"appmetrics-zipkin": "^1.0.4",
AssertionError [ERR_ASSERTION]: New version of Node Application Metrics are using by application.
This version 4.*.* is incompatible with already initialized
version 4.0.1.
If you are using greenfield ibmapm in your application, and your application is using a higher version of appmetrics, you will find this error.
you need to delete the appmetrics folder in ./ibmapm/node_modules (it is v4.0.1), so that the latest version in your application could be used.
rm -rf ./ibmapm/node_modules/appmetrics
FAQs
Node.js data collector for IBM BAM
We found that ibmapm demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
require(esm) backported to Node.js 20, easing the transition to ESM-only packages and reducing complexity for developers as Node 18 nears end-of-life.
Security News
PyPI now supports iOS and Android wheels, making it easier for Python developers to distribute mobile packages.
Security News
Create React App is officially deprecated due to React 19 issues and lack of maintenance—developers should switch to Vite or other modern alternatives.