[Snyk] Upgrade @opentelemetry/instrumentation from 0.38.0 to 0.51.0 #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Snyk has created this PR to upgrade @opentelemetry/instrumentation from 0.38.0 to 0.51.0. See this package in npm: @opentelemetry/instrumentation See this project in Snyk: https://app.snyk.io/org/nicholaschoi168/project/3cd8d310-f359-441d-8f93-95be28b09235?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.38.0 to 0.51.0.
ℹ️ 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 18 versions ahead of your current version.
The recommended version was released 25 days ago, on 2024-04-24.
Release notes
Package name: @opentelemetry/instrumentation
-
0.51.0 - 2024-04-24
- feat(sdk-node)!: remove long deprecated methods in favor of constructor options #4606 @ pichlermarc
- 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
- 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
- The value can be overwritten by
- merging a resource containing the
- using another resource detector which writes
- fix(otlp-grpc-exporter-base): avoid TypeError on exporter shutdown #4612 @ pichlermarc
- fix(instrumentation): Don't use
-
0.50.0 - 2024-04-03
- fix(exporter-*-otlp-grpc)!: lazy load gRPC to improve compatibility with
- Fixes a bug where requiring the gRPC exporter before enabling the instrumentation from
- Breaking changes, removes several functions and properties that were used internally and were not intended for end-users
- this returned a static enum value that would denote the export type (
- this returned a static enum value that would correspond to the gRPC service path
- was used internally to access metadata, but as a side effect allowed end-users to modify metadata on runtime.
- 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
- 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
- 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
- feat(api-events): added data field to the Event interface #4575 @ martinkuba
- fix(exporter--otlp-): use parseHeaders() to ensure header-values are not 'undefined' #4540
- Fixes a bug where passing
- fix(sdk-logs): ensure default resource attributes are used as fallbacks when a resource is passed to LoggerProvider.
- docs(instrumentation-http): document semantic conventions and attributes in use. #4587 @ JamieDanielson
-
0.49.1 - 2024-02-29
- fix(instrumentation): don't add
-
0.49.0 - 2024-02-29
- 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:
- A user extends the exporter and overrides the shutdown function, and does something which is usually called by the unload listener
- We remove the unload event listener
- That user's overridden shutdown function no longer gets called
- 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
- 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
-
0.45.0 - 2023-11-07
-
0.44.0 - 2023-10-10
-
0.43.0 - 2023-09-12
-
0.42.0 - 2023-09-11
-
0.41.2 - 2023-08-08
-
0.41.1 - 2023-07-24
-
0.41.0 - 2023-07-06
-
0.40.0 - 2023-06-06
-
0.39.1 - 2023-05-12
-
0.39.0 - 2023-05-11
-
0.38.0 - 2023-04-13
from @opentelemetry/instrumentation GitHub release notes0.51.0
💥 Breaking Change
NodeSDK.configureTracerProvider(), please use constructor options insteadNodeSDK.configureMeterProvider(), please use constructor options insteadNodeSDK.configureLoggerProvider(), please use constructor options insteadNodeSDK.addResource(), please use constructor options insteadNodeSDK.detectResources(), this is not necessary anymore, resources are now auto-detected onNodeSDK.start()if the constructor optionautoDetectResourcesis unset,undefinedortrue.InstrumentationBaseInstrumentationNodeModuleDefinitionInstrumentationNodeModuleFile🚀 (Enhancement)
serviceinstanceto the list of resource detectors on the environment variableOTEL_NODE_RESOURCE_DETECTORS, e.gOTEL_NODE_RESOURCE_DETECTORS=env,host,os,serviceinstanceservice.instance.idattributeservice.instance.id🐛 (Bug Fix)
requireto loadpackage.jsonfiles #4593 @ timfish0.50.0
💥 Breaking Change
@ opentelemetry/instrumenation-grpc#4432 @ pichlermarc@ opentelemetry/instrumentation-grpcwould lead to missing telemetrygetServiceClientType()SPAN,METRICS,LOGS)getServiceProtoPath()metadataserviceClientcompression🚀 (Enhancement)
HostDetectoras default resource detector #4566 @ maryliag🐛 (Bug Fix)
undefinedas a header value would crash the end-user app after the export timeout elapsed.📚 (Refine Doc)
0.49.1
🐛 (Bug Fix)
@ opentelemetry/api-logsas apeerDependency#4515 @ pichlermarc0.49.0
💥 Breaking Change
🚀 (Enhancement)
🐛 (Bug Fix)
Commit messages
Package name: @opentelemetry/instrumentation
default_lang_committo front matter of all nonenpages open-telemetry/opentelemetry.io#4612)endoc links open-telemetry/opentelemetry.io#4627)Compare
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
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs
Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.