Skip to content

Commit 71c125a

Browse files
Merge branch 'main' into fix-dd-memory-leak
2 parents ae6cab5 + aa00ed1 commit 71c125a

File tree

822 files changed

+24034
-24227
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

822 files changed

+24034
-24227
lines changed

.chloggen/add-compression-auto.yaml

+29
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: enhancement
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: fileconsumer
8+
9+
10+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
11+
note: Support "`compression:auto`" which automatically detects file compression type and ingests data. Currently, only gzip compressed files are auto detected. This allows for mix of compressed and uncompressed files to be ingested with the same filelogreceiver.
12+
13+
14+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
15+
issues: [37772]
16+
17+
# (Optional) One or more lines of additional information to render under the primary note.
18+
# These lines will be padded with 2 spaces and then inserted directly into the document.
19+
# Use pipe (|) for multiline entries.
20+
subtext:
21+
22+
# If your change doesn't affect end users or the exported elements of any package,
23+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
24+
# Optional: The change log or logs in which this entry should be included.
25+
# e.g. '[user]' or '[user, api]'
26+
# Include 'user' if the change is relevant to end users.
27+
# Include 'api' if there is a change to a library API.
28+
# Default: '[user]'
29+
change_logs: [user]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: enhancement
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: elasticsearchexporter
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Report Elasticsearch request success / failure via componentstatus
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [39562]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext:
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: [user]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
2+
change_type: enhancement
3+
4+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
5+
component: confmap/googlesecretmanager
6+
7+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8+
note: Mark the Google Secret Manager provider as alpha stability.
9+
10+
# One or more tracking issues related to the change
11+
issues: [39665]
12+
13+
# (Optional) One or more lines of additional information to render under the primary note.
14+
# These lines will be padded with 2 spaces and then inserted directly into the document.
15+
# Use pipe (|) for multiline entries.
16+
subtext:
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
2+
change_type: enhancement
3+
4+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
5+
component: confmap/googlesecretmanager
6+
7+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
8+
note: Update scheme to use googlesecretsmanager instead of googlesecretmanagerprovider.
9+
# One or more tracking issues related to the change
10+
issues: [39971]
11+
12+
# (Optional) One or more lines of additional information to render under the primary note.
13+
# These lines will be padded with 2 spaces and then inserted directly into the document.
14+
# Use pipe (|) for multiline entries.
15+
subtext:
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: enhancement
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: prometheusremotewriteexporter
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Add `exporter.prometheusremotewritexporter.enableSendingRW2` feature gate and configuration to the exporter to send Prometheus remote write 2.0 version.
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [33661]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext: WARNING! PRW 2.0 support for the exporter is still under development and not ready for usage.
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: [user, api]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: bug_fix
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: clickhouseexporter
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: clickhouseexporter doesn't set the database name in the dsn of the query that creates the database
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [38829]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext:
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: []
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: enhancement
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: receiver/hostmetricsreceiver
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Migrated `hostmetricsreceiver` to use `pkg/winperfcounters` when retrieving Windows performance counters.
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [38858]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext:
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: [user]

.chloggen/prom-scrape-config-ta.yaml

+27
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: bug_fix
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: prometheusreceiver
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Add 'fallback_scrape_protocol' to entries obtained through Target Allocator, unless already defined.
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [39672]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext: This applies the same configuration change that is already applied on static configuration.
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: [user]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: breaking
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: coralogixexporter
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Remove deprecated batcher config for coralogixexporter, use sending_queue::batch
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [39960]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext:
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: [user]
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Use this changelog template to create an entry for release notes.
2+
3+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4+
change_type: deprecation
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: processor/tailsampling
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: The invert decisions (InvertSampled and InvertNotSampled) have been deprecated, please make use of drop policy to explicitly not sample select traces.
11+
12+
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13+
issues: [39833]
14+
15+
# (Optional) One or more lines of additional information to render under the primary note.
16+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17+
# Use pipe (|) for multiline entries.
18+
subtext:
19+
20+
# If your change doesn't affect end users or the exported elements of any package,
21+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
22+
# Optional: The change log or logs in which this entry should be included.
23+
# e.g. '[user]' or '[user, api]'
24+
# Include 'user' if the change is relevant to end users.
25+
# Include 'api' if there is a change to a library API.
26+
# Default: '[user]'
27+
change_logs: []

cmd/golden/go.mod

+29-29
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ require (
66
github.com/open-telemetry/opentelemetry-collector-contrib/pkg/golden v0.125.0
77
github.com/open-telemetry/opentelemetry-collector-contrib/pkg/pdatatest v0.125.0
88
github.com/stretchr/testify v1.10.0
9-
go.opentelemetry.io/collector/component v1.31.1-0.20250508034258-ac520a5c14cc
10-
go.opentelemetry.io/collector/component/componenttest v0.125.1-0.20250508034258-ac520a5c14cc
11-
go.opentelemetry.io/collector/consumer v1.31.1-0.20250508034258-ac520a5c14cc
12-
go.opentelemetry.io/collector/pdata v1.31.1-0.20250508034258-ac520a5c14cc
13-
go.opentelemetry.io/collector/receiver v1.31.1-0.20250508034258-ac520a5c14cc
14-
go.opentelemetry.io/collector/receiver/otlpreceiver v0.125.1-0.20250508034258-ac520a5c14cc
9+
go.opentelemetry.io/collector/component v1.31.1-0.20250509035855-4d929a9d6a7e
10+
go.opentelemetry.io/collector/component/componenttest v0.125.1-0.20250509035855-4d929a9d6a7e
11+
go.opentelemetry.io/collector/consumer v1.31.1-0.20250509035855-4d929a9d6a7e
12+
go.opentelemetry.io/collector/pdata v1.31.1-0.20250509035855-4d929a9d6a7e
13+
go.opentelemetry.io/collector/receiver v1.31.1-0.20250509035855-4d929a9d6a7e
14+
go.opentelemetry.io/collector/receiver/otlpreceiver v0.125.1-0.20250509035855-4d929a9d6a7e
1515
go.opentelemetry.io/otel/metric v1.35.0
1616
go.opentelemetry.io/otel/trace v1.35.0
1717
go.uber.org/goleak v1.3.0
@@ -48,29 +48,29 @@ require (
4848
github.com/pmezard/go-difflib v1.0.0 // indirect
4949
github.com/rs/cors v1.11.1 // indirect
5050
go.opentelemetry.io/auto/sdk v1.1.0 // indirect
51-
go.opentelemetry.io/collector v0.125.1-0.20250508034258-ac520a5c14cc // indirect
52-
go.opentelemetry.io/collector/client v1.31.1-0.20250508034258-ac520a5c14cc // indirect
53-
go.opentelemetry.io/collector/component/componentstatus v0.125.1-0.20250508034258-ac520a5c14cc // indirect
54-
go.opentelemetry.io/collector/config/configauth v0.125.1-0.20250508034258-ac520a5c14cc // indirect
55-
go.opentelemetry.io/collector/config/configcompression v1.31.1-0.20250508034258-ac520a5c14cc // indirect
56-
go.opentelemetry.io/collector/config/configgrpc v0.125.1-0.20250508034258-ac520a5c14cc // indirect
57-
go.opentelemetry.io/collector/config/confighttp v0.125.1-0.20250508034258-ac520a5c14cc // indirect
58-
go.opentelemetry.io/collector/config/configmiddleware v0.125.1-0.20250508034258-ac520a5c14cc // indirect
59-
go.opentelemetry.io/collector/config/confignet v1.31.1-0.20250508034258-ac520a5c14cc // indirect
60-
go.opentelemetry.io/collector/config/configopaque v1.31.1-0.20250508034258-ac520a5c14cc // indirect
61-
go.opentelemetry.io/collector/config/configtls v1.31.1-0.20250508034258-ac520a5c14cc // indirect
62-
go.opentelemetry.io/collector/confmap v1.31.1-0.20250508034258-ac520a5c14cc // indirect
63-
go.opentelemetry.io/collector/consumer/consumererror v0.125.1-0.20250508034258-ac520a5c14cc // indirect
64-
go.opentelemetry.io/collector/consumer/xconsumer v0.125.1-0.20250508034258-ac520a5c14cc // indirect
65-
go.opentelemetry.io/collector/extension/extensionauth v1.31.1-0.20250508034258-ac520a5c14cc // indirect
66-
go.opentelemetry.io/collector/extension/extensionmiddleware v0.125.1-0.20250508034258-ac520a5c14cc // indirect
67-
go.opentelemetry.io/collector/featuregate v1.31.1-0.20250508034258-ac520a5c14cc // indirect
68-
go.opentelemetry.io/collector/internal/sharedcomponent v0.125.1-0.20250508034258-ac520a5c14cc // indirect
69-
go.opentelemetry.io/collector/internal/telemetry v0.125.1-0.20250508034258-ac520a5c14cc // indirect
70-
go.opentelemetry.io/collector/pdata/pprofile v0.125.1-0.20250508034258-ac520a5c14cc // indirect
71-
go.opentelemetry.io/collector/pipeline v0.125.1-0.20250508034258-ac520a5c14cc // indirect
72-
go.opentelemetry.io/collector/receiver/receiverhelper v0.125.1-0.20250508034258-ac520a5c14cc // indirect
73-
go.opentelemetry.io/collector/receiver/xreceiver v0.125.1-0.20250508034258-ac520a5c14cc // indirect
51+
go.opentelemetry.io/collector v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
52+
go.opentelemetry.io/collector/client v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
53+
go.opentelemetry.io/collector/component/componentstatus v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
54+
go.opentelemetry.io/collector/config/configauth v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
55+
go.opentelemetry.io/collector/config/configcompression v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
56+
go.opentelemetry.io/collector/config/configgrpc v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
57+
go.opentelemetry.io/collector/config/confighttp v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
58+
go.opentelemetry.io/collector/config/configmiddleware v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
59+
go.opentelemetry.io/collector/config/confignet v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
60+
go.opentelemetry.io/collector/config/configopaque v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
61+
go.opentelemetry.io/collector/config/configtls v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
62+
go.opentelemetry.io/collector/confmap v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
63+
go.opentelemetry.io/collector/consumer/consumererror v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
64+
go.opentelemetry.io/collector/consumer/xconsumer v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
65+
go.opentelemetry.io/collector/extension/extensionauth v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
66+
go.opentelemetry.io/collector/extension/extensionmiddleware v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
67+
go.opentelemetry.io/collector/featuregate v1.31.1-0.20250509035855-4d929a9d6a7e // indirect
68+
go.opentelemetry.io/collector/internal/sharedcomponent v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
69+
go.opentelemetry.io/collector/internal/telemetry v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
70+
go.opentelemetry.io/collector/pdata/pprofile v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
71+
go.opentelemetry.io/collector/pipeline v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
72+
go.opentelemetry.io/collector/receiver/receiverhelper v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
73+
go.opentelemetry.io/collector/receiver/xreceiver v0.125.1-0.20250509035855-4d929a9d6a7e // indirect
7474
go.opentelemetry.io/contrib/bridges/otelzap v0.10.0 // indirect
7575
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.60.0 // indirect
7676
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.60.0 // indirect

0 commit comments

Comments
 (0)