Splunk OpenTelemetry Zero Config Auto Instrumentation for Node.js 🔗
Splunk OpenTelemetry (OTel) Zero Configuration Auto Instrumentation for Node.js automatically instruments supported Node.js libraries in running applications to capture distributed traces. The Splunk OpenTelemetry Collector receives the distributed traces and forwards them to Splunk Application Performance Monitoring (APM) in Splunk Observability Cloud.
This feature provides the following benefits:
You don’t need to configure or manually instrument your applications before deployment if your Node.js applications use any of the supported libraries.
You can start streaming traces and monitor distributed applications with Splunk APM in minutes.
Automatic instrumentation is only available for applications using supported Node.js libraries. See Ensure you have supported Node.js and library versions. If your application isn’t supported, manually instrument your service to generate trace data. See Manually instrument Node.js applications for Splunk Observability Cloud .
Your Splunk Observability Cloud realm and access token.
To get an access token, see Retrieve and manage user API access tokens using Splunk Observability Cloud.
To find your Splunk realm, see Note about realms.
Zero Config Auto Instrumentation is available on Kubernetes and Linux using Splunk OpenTelemetry Node.js. When you activate Zero Config, Splunk OpenTelemetry Node.js automatically instruments all Node.js applications running in the target environment.
On Linux, the target environment is the entire Linux host, so the Node.js agent instruments every Node.js application on the host.
On Kubernetes, the target environment is the deployment or pod where you activated instrumentation. The Node.js agent instruments every Node.js application within the pod or deployment.
In both cases you must restart the applications to start instrumentation.
Follow instructions from the following list: