fix(deps): update dependency @elastic/opentelemetry-node to v1.3.0

[elastic-renovate-prod]

This PR contains the following updates:

Package	Type	Update	Change
@elastic/opentelemetry-node (source)	dependencies	minor	1.0.0 -> 1.3.0

---

Release Notes

elastic/elastic-otel-node (@​elastic/opentelemetry-node)

v1.3.0: @​elastic/opentelemetry-node 1.3.0

Compare Source

Changelog

Features and enhancements

• Added @opentelemetry/instrumentation-oracledb to the default set of instrumentations.

• New Central Configuration settings. Typically these settings are only useful
  for temporary debugging of telemetry.

  • send_traces: A boolean to disable/enable sending of trace telemetry (i.e. spans).
  • send_metrics: The same, for the metrics signal.
  • send_logs: The same, for the logs signal.

  While these are supported in EDOT Node.js, they will only be present in
  "Agent Configuration" UI of Kibana version 9.2 and later.
  #​928

• New ELASTIC_OTEL_CONTEXT_PROPAGATION_ONLY configuration environment variable.
  Set this to true to disable sending of spans, but otherwise continue to
  do context propagation. This can be useful in limited conditions to support
  propagating trace-context through a service to downstream services for
  distributed tracing, but not collect spans from the service. (Note that this
  typically results in incomplete or broken traces in Kibana trace viewer.)
  #​928

Fixes

Chores

• OTLP export requests (HTTP flavors only) will include an identifier for EDOT Node.js in the User-Agent header.
  #​982

---

README | Full Release Notes | Breaking Changes

v1.2.0: @​elastic/opentelemetry-node 1.2.0

Compare Source

Changelog

Features and enhancements

• Initial support for Central Configuration: the ability to configure some aspects of EDOT Node.js in running instrumented applications from a central Kibana. This feature is in technical preview. #​834 #​886

  This release includes support for the following settings: logging_level, deactivate_all_instrumentations, deactivate_instrumentations

Chores

• Support for instrumenting redis version 4 has moved from @opentelemetry/instrumentation-redis-4 to @opentelemetry/instrumentation-redis. If you are using the OTEL_NODE_ENABLED_INSTRUMENTATIONS or OTEL_NODE_DISABLED_INSTRUMENTATIONS environment variables to control instrumentation of redis@4 you will need to change from using "redis-4" to "redis".

---

README | Full Release Notes | Breaking Changes

v1.1.1: @​elastic/opentelemetry-node 1.1.1

Compare Source

Changelog

• Fix publishing so that the "hook.mjs" file is included.
  https://github.com/elastic/elastic-otel-node/pull/835/835)

  Without this fix, using node --import @​elastic/opentelemetry-node ... will
  crash with:

    Cannot find module '.../node_modules/@​elastic/opentelemetry-node/hook.mjs' imported from .../node_modules/@​elastic/opentelemetry-node/import.mjs
  

---

README | Full Changelog

v1.1.0: @​elastic/opentelemetry-node 1.1.0

Compare Source

Changelog

• BREAKING CHANGE: This includes an update to @opentelemetry/instrumentation-aws-sdk
  v0.54.0 which inclues the following breaking changes:

  • Instrumentation of AWS SDK v2 has been dropped. See https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-aws-sdk/CHANGELOG.md#0510-2025-04-08. (https://github.com/elastic/elastic-otel-node/pull/788)
  • The aws.region span attribute has been changed to cloud.region. See https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/plugins/node/opentelemetry-instrumentation-aws-sdk/CHANGELOG.md#0540-2025-06-02. (https://github.com/elastic/elastic-otel-node/pull/814)

• feat: Add env var ELASTIC_OTEL_HOST_METRICS_DISABLED to control whether
  EDOT Node.js will collect host metrics (process.*). This
  means users can disable host metrics without affecting metrics from instrumentationhttps://github.com/elastic/elastic-otel-node/issues/736sues/736)

• The ELASTIC_OTEL_METRICS_DISABLED environment variable is now deprecated.
  Use OTEL_METRICS_EXPORTER=none (instead of ELASTIC_OTEL_METRICS_DISABLED=true)
  to disable any metrics being exported by EDOT Node.js.

• feat: Restore the @elastic/opentelemetry-node/sdk entry-point and show how
  to use it to bootstrap the EDOT Node.js SDK in code. This means using
  node --import ./telemetry.mjs app.js, rather than the typical zero-code
  node --import @​elastic/opentelemetry-node app.js method for starting the SDK.
  https://github.com/elastic/elastic-otel-node/issues/718/718)

  The ./telemetry.mjs file uses APIs exported by @elastic/opentelemetry-node/sdk
  to configure and start the OpenTelemetry Node.js SDK. See
  examples/telemetry.mjs.

  WARNING: Bootstrapping the Node SDK in code often means using
  OpenTelemetry JS APIs that are not yet stable. These APIs may break in
  minor versions of @elastic/opentelemetry-node.

• chore: add custom GCP resource detector to avoid internal telemetry to be sent. See open-telemetry/opentelemetry-js-contrib#2320.
  https://github.com/elastic/elastic-otel-node/pull/709/709)

---

README | Full Changelog

---

Configuration

📅 Schedule: Branch creation - "after 1am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.