feat(api): allow adding span links after span creation #4536@seemk
This change is non-breaking for end-users, but breaking for Trace SDK implmentations in accordance with the specification as new features need to be implemented.
Note: This package will now be versioned according to the version of semantic conventions being provided.
:rocket: (Enhancement)
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
v1.26.0
1.26.0
:rocket: (Enhancement)
feat: include instrumentation scope info in console span and log record exporters #4848@blumamir
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
:bug: (Bug Fix)
fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879@trentm
deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865@lforst
feat: include instrumentation scope info in console span and log record exporters #4848@blumamir
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
:bug: (Bug Fix)
fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879@trentm
deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865@lforst
refactor(examples): added usage of @opentelemetry/semantic-conventions and @opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764@Zen-cronic
:house: (Internal)
refactor(context-zone-peer-dep): use explicit exports #4785@pichlermarc
Note: This package will now be versioned according to the version of semantic conventions being provided.
:rocket: (Enhancement)
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
v1.26.0
1.26.0
:rocket: (Enhancement)
feat: include instrumentation scope info in console span and log record exporters #4848@blumamir
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
:bug: (Bug Fix)
fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879@trentm
deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865@lforst
feat: include instrumentation scope info in console span and log record exporters #4848@blumamir
feat(semconv): update semantic conventions to 1.27 (from 1.7.0) #4690@dyladan
Exported names have changed to ATTR_{name} for attributes (e.g. ATTR_HTTP_REQUEST_METHOD), {name}_VALUE_{value} for enumeration values (e.g. HTTP_REQUEST_METHOD_VALUE_POST), and METRIC_{name} for metrics. Exported names from previous versions are deprecated.
Import @opentelemetry/semantic-conventions for stable semantic conventions. Import @opentelemetry/semantic-conventions/incubating for all semantic conventions, stable and unstable.
Note: Semantic conventions are now versioned separately from other stable artifacts, to correspond to the version of semantic conventions they provide. Changes will be in a separate changelog.
:bug: (Bug Fix)
fix(sdk-node): avoid spurious diag errors for unknown OTEL_NODE_RESOURCE_DETECTORS values #4879@trentm
deps(opentelemetry-instrumentation): Bump shimmer types to 1.2.0 #4865@lforst
refactor(examples): added usage of @opentelemetry/semantic-conventions and @opentelemetry/resources to the examples in examples/opentelemetry-web for maintaining consistency across all examples. #4764@Zen-cronic
:house: (Internal)
refactor(context-zone-peer-dep): use explicit exports #4785@pichlermarc
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
- `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
- `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency
- `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions
Bumps the otel-dependencies group with 3 updates in the / directory: @opentelemetry/api, @opentelemetry/exporter-prometheus and @opentelemetry/sdk-trace-node.
Updates
@opentelemetry/api
from 1.8.0 to 1.9.0Release notes
Sourced from
@opentelemetry/api
's releases.Changelog
Sourced from
@opentelemetry/api
's changelog.Commits
08f597f
chore: release API 1.4.0 / SDK 1.9.0 / 0.35.0 (#3516)969bb62
fix(tracing): make spans resilient to performance clock drift (#3434)2dcc898
Document repo settings (#3519)475e401
docs(sdk-metrics): fix badge and reword introductory sentence (#3484)126ae93
fix(sdk-node): fix exporter to be read only OTEL_TRACES_EXPORTER is set to a ...c93ab9e
fix(core): fix precision loss in numberToHrtime (#3480)3fd6fb8
fix(sdk-metrics): fix duplicated registration of metrics for collectors (#3488)93222fc
fix(api): declare this parameter type in observable callbacks (#3497)eecb800
feat(sdk-node): configure no-op sdk withOTEL_SDK_DISABLED
environment vari...1c3af6c
feat(api-logs): add the SeverityNumber enumeration (#3443)Updates
@opentelemetry/exporter-prometheus
from 0.51.1 to 0.53.0Release notes
Sourced from
@opentelemetry/exporter-prometheus
's releases.... (truncated)
Commits
720bc8c
chore: prepare next release (#4960)65cedf7
chore: prepare next release (#4949)bd25230
docs: document console exporter output stability (#4956)948496d
chore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17
docs: Describe support for ESM (#4876)2ca2459
test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601
feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52
chore: prepare next release (#4939)5578a11
chore: sync package-lock.json (#4947)5c1ae0a
docs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Updates
@opentelemetry/sdk-metrics
from 1.24.1 to 1.26.0Release notes
Sourced from
@opentelemetry/sdk-metrics
's releases.... (truncated)
Changelog
Sourced from
@opentelemetry/sdk-metrics
's changelog.... (truncated)
Commits
720bc8c
chore: prepare next release (#4960)65cedf7
chore: prepare next release (#4949)bd25230
docs: document console exporter output stability (#4956)948496d
chore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17
docs: Describe support for ESM (#4876)2ca2459
test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601
feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52
chore: prepare next release (#4939)5578a11
chore: sync package-lock.json (#4947)5c1ae0a
docs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Updates
@opentelemetry/sdk-trace-node
from 1.24.1 to 1.26.0Release notes
Sourced from
@opentelemetry/sdk-trace-node
's releases.... (truncated)
Changelog
Sourced from
@opentelemetry/sdk-trace-node
's changelog.... (truncated)
Commits
720bc8c
chore: prepare next release (#4960)65cedf7
chore: prepare next release (#4949)bd25230
docs: document console exporter output stability (#4956)948496d
chore: pin unit test to node 22.6 until 22.8 is available (#4957)966ac17
docs: Describe support for ESM (#4876)2ca2459
test(exporter-logs-otlp-grpc): improve error reporting in particular test fai...c398601
feat(jaeger-remote-sampler): Implement jaeger remote sampler (#4589)3cf1c52
chore: prepare next release (#4939)5578a11
chore: sync package-lock.json (#4947)5c1ae0a
docs(sdk-metrics): Update Histogram docs to reflect upper bound inclusivity (...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show