Autoinstrumentation-nodejs

An automatic instrumentation agent for Node.js applications that the OpenTelemetry Operator injects into Kubernetes workloads to add OpenTelemetry support…

  • Development
  • Infrastructure
  • Tools & Utilities
An automatic instrumentation agent for Node.js applications that the OpenTelemetry Operator injects into Kubernetes workloads to add OpenTelemetry support without manual code changes.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score

Not enough data yet for a health score. It needs at least 2 of 4 factors: maintenance, popularity, ease of install, resource needs.

No GitHub repository data collected yet.

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • OpenTelemetry Operator In Kubernetes, the OpenTelemetry Operator can inject this Node.js instrumentation automatically; use the official automatic-instrumentation docs to enable and configure it. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I enable Node.js auto-instrumentation in Kubernetes?

The OpenTelemetry Operator can inject the Node.js instrumentation automatically. Use the automatic-instrumentation docs to enable and configure the injection.

How can I limit which Node.js instrumentations are active?

Use the OTEL_NODE_ENABLED_INSTRUMENTATIONS setting to control OpenTelemetry auto-instrumentation for Node.js.

Why do some Node.js libraries not produce telemetry with auto-instrumentation?

Auto-instrumentation only works with libraries that are currently supported. Check the OpenTelemetry Registry for the supported libraries.

How do I debug Node auto-instrumentation that works locally but not after deployment?

Set OTEL_LOG_LEVEL to DEBUG to get hints about what is going on. In the reported case, incoming and outgoing HTTP metrics stopped after the application was deployed.

Answers sourced from opentelemetry.io, stackoverflow.com, stackoverflow.com, www.reddit.com

Community

Collected 48 days ago - public community threads