[Snyk] Upgrade @opentelemetry/instrumentation from 0.45.1 to 0.51.1

[integraci-co804]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade @opentelemetry/instrumentation from 0.45.1 to 0.51.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 8 versions ahead of your current version.

• The recommended version was released on 21 days ago.

Release notes

Package name: @opentelemetry/instrumentation

• 0.51.1 - 2024-05-07
  

  0.51.1

  🐛 (Bug Fix)

  • fix(instrumentation): update import-in-the-middle to 1.7.4
• 0.51.0 - 2024-04-24
  

  0.51.0

  💥 Breaking Change

  • feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @ pichlermarc
    • NodeSDK.configureTracerProvider(), please use constructor options instead
    • NodeSDK.configureMeterProvider(), please use constructor options instead
    • NodeSDK.configureLoggerProvider(), please use constructor options instead
    • NodeSDK.addResource(), please use constructor options instead
    • NodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected on NodeSDK.start() if the constructor option autoDetectResources is unset, undefined or true.
  • feat(instrumentation): add patch and unpatch diag log messages #4641
    • Instrumentations should not log patch and unpatch messages to diag channel.
  • feat!(instrumentation): remove moduleExports generic type from instrumentation registration #4598 @ blumamir
    • breaking for instrumentation authors that depend on
      • InstrumentationBase
      • InstrumentationNodeModuleDefinition
      • InstrumentationNodeModuleFile

  🚀 (Enhancement)

  • refactor(instrumentation-grpc): move to use SEMATTRS #4633
  • feat(otlp-transformer): consolidate scope/resource creation in transformer #4600
  • feat(sdk-logs): print message when attributes are dropped due to attribute count limit #4614 @ HyunnoH
  • feat(sdk-node): add usage for the detector ServiceInstanceIdDetectorSync. #4626 @ maryliag
    • The resource detector can be added to default resource detector list by adding the value serviceinstance to the list of resource detectors on the environment variable OTEL_NODE_RESOURCE_DETECTORS, e.g OTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstance
    • The value can be overwritten by
      • merging a resource containing the service.instance.id attribute
      • using another resource detector which writes service.instance.id

  🐛 (Bug Fix)

  • fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @ pichlermarc
  • fix(instrumentation): Don't use require to load package.json files #4593 @ timfish
• 0.50.0 - 2024-04-03
  

  0.50.0

  💥 Breaking Change

  • fix(exporter-*-otlp-grpc)!: lazy load gRPC to improve compatibility with @ opentelemetry/instrumenation-grpc #4432 @ pichlermarc
    • Fixes a bug where requiring the gRPC exporter before enabling the instrumentation from @ opentelemetry/instrumentation-grpc would lead to missing telemetry
    • Breaking changes, removes several functions and properties that were used internally and were not intended for end-users
      • getServiceClientType()
        • this returned a static enum value that would denote the export type (SPAN, METRICS, LOGS)
      • getServiceProtoPath()
        • this returned a static enum value that would correspond to the gRPC service path
      • metadata
        • was used internally to access metadata, but as a side effect allowed end-users to modify metadata on runtime.
      • serviceClient
        • was used internally to keep track of the service client used by the exporter, as a side effect it allowed end-users to modify the gRPC service client that was used
      • compression
        • was used internally to keep track of the compression to use but was unintentionally exposed to the users. It allowed to read and write the value, writing, however, would have no effect.
  • feat(api-events)!: removed domain from the Events API #4569 @ martinkuba
  • fix(api-events)!: renamed EventEmitter to EventLogger in the Events API #4569 @ martinkuba
  • feat(api-logs)!: changed LogRecord body data type to AnyValue and AnyValueMap types #4575 @ martinkuba

  🚀 (Enhancement)

  • feat(instrumentation-xhr): optionally ignore network events #4571 @ MustafaHaddara
  • refactor(instrumentation-http): use exported strings for semconv #4573 @ JamieDanielson
  • perf(instrumentation-http): remove obvious temp allocations #4576 @ Samuron
  • feat(sdk-node): add HostDetector as default resource detector #4566 @ maryliag
  • feat(api-events): added data field to the Event interface #4575 @ martinkuba

  🐛 (Bug Fix)

  • fix(exporter--otlp-): use parseHeaders() to ensure header-values are not 'undefined' #4540
    • Fixes a bug where passing undefined as a header value would crash the end-user app after the export timeout elapsed.
  • fix(sdk-logs): ensure default resource attributes are used as fallbacks when a resource is passed to LoggerProvider.

  📚 (Refine Doc)

  • docs(instrumentation-http): document semantic conventions and attributes in use. #4587 @ JamieDanielson
• 0.49.1 - 2024-02-29
  

  0.49.1

  🐛 (Bug Fix)

  • fix(instrumentation): don't add @ opentelemetry/api-logs as a peerDependency #4515 @ pichlermarc
• 0.49.0 - 2024-02-29
  

  0.49.0

  💥 Breaking Change

  • fix(otlp-exporter-base)!: remove unload event from OTLPExporterBrowserBase #4438 @ eldavojohn
    • Reason: The 'unload' event prevents sites from taking advantage of Google's backward/forward cache and will be deprecated. It is now up to the consuming site to implement these shutdown events.
    • This breaking change affects users under this scenario:
      1. A user extends the exporter and overrides the shutdown function, and does something which is usually called by the unload listener
      2. We remove the unload event listener
      3. That user's overridden shutdown function no longer gets called

  🚀 (Enhancement)

  • feat(instrumentation): allow LoggerProvider to be specified in Instrumentations #4314 @ hectorhdzg
  • feat(instrumentation): add getModuleDefinitions() to InstrumentationBase #4475 @ pichlermarc
  • feat(exporter-metrics-otlp-http): add option to set the exporter aggregation preference #4409 @ AkselAllas
  • feat(node-sdk): add spanProcessors option #4454 @ naseemkullah

  🐛 (Bug Fix)

  • fix(sdk-node): allow using samplers when the exporter is defined in the environment #4394 @ JacksonWeber
  • fix(instrumentation): normalize paths for internal files in scoped packages #4467 @ pichlermarc
    • Fixes a bug where, on Windows, internal files on scoped packages would not be instrumented.
  • fix(otlp-transformer): only use BigInt inside hrTimeToNanos() #4484 @ pichlermarc
  • fix(instrumentation-fetch): do not enable in Node.js; clarify in docs this instr is for web fetch only #4498 @ trentm
• 0.48.0 - 2024-01-26
• 0.47.0 - 2024-01-15
• 0.46.0 - 2023-12-14
• 0.45.1 - 2023-11-08

from @opentelemetry/instrumentation GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs