Skip to content

Commit 1d9a5fd

Browse files
Merge branch 'main' into build-number-fix
2 parents 8bd9362 + 099af17 commit 1d9a5fd

File tree

2,385 files changed

+52805
-35720
lines changed

Some content is hidden

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

2,385 files changed

+52805
-35720
lines changed
Original file line numberDiff line numberDiff line change
@@ -1,27 +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: new_component
5-
6-
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7-
component: bmchelixexporter
8-
9-
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: metrics implementation
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: [36773]
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]
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: new_component
5+
6+
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7+
component: azureblobexporter
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Add new exporter for sending telemetry to Azure Storage Blob
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: [35717]
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/hostmetricsreceiver-feature.yaml renamed to .chloggen/codeboten_update-semconv.yaml

+3-3
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
change_type: breaking
55

66
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7-
component: receiver/hostmetrics
7+
component: telemetrygen
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: "Remove receiver.hostmetrics.normalizeProcessCPUUtilization feature gate"
10+
note: Update attribute of generated traces from `net.peer.ip` to `net.sock.peer.addr` to bring it in line with new semconv.
1111

1212
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13-
issues: [34763]
13+
issues: [38043]
1414

1515
# (Optional) One or more lines of additional information to render under the primary note.
1616
# These lines will be padded with 2 spaces and then inserted directly into the document.
+5-4
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
11
# Use this changelog template to create an entry for release notes.
22

33
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4-
change_type: enhancement
4+
change_type: bug_fix
55

66
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7-
component: vcenterreceiver
7+
component: azuremonitorreceiver
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Adds three more vCenter virtual machine performance metrics
10+
note: "Fix bug where the time grain wasn't honored"
1111

1212
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13-
issues: [37488]
13+
issues: [37337]
1414

1515
# (Optional) One or more lines of additional information to render under the primary note.
1616
# These lines will be padded with 2 spaces and then inserted directly into the document.
@@ -25,3 +25,4 @@ subtext:
2525
# Include 'api' if there is a change to a library API.
2626
# Default: '[user]'
2727
change_logs: [user]
28+

.chloggen/telemetrygen-public-api.yaml renamed to .chloggen/kafka_metrics_receiver-add-refresh_frequency.yaml

+7-5
Original file line numberDiff line numberDiff line change
@@ -4,18 +4,20 @@
44
change_type: enhancement
55

66
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7-
component: telemetrygen
7+
component: receiver/kafkametricsreceiver
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Exported the API for telemetrygen for test uses. Additionally added new E2E tests and fixed race condition
10+
note: Add `refresh_frequency` config to `kafkametricsreceiver`, to configure custom duration for cluster metadata refresh
1111

1212
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13-
issues: [36984]
13+
issues: [37896]
1414

1515
# (Optional) One or more lines of additional information to render under the primary note.
1616
# These lines will be padded with 2 spaces and then inserted directly into the document.
1717
# Use pipe (|) for multiline entries.
18-
subtext:
18+
subtext: |
19+
- Helps fine tuning the refresh_frequency, and enables custom cluster metadata refresh intervals
20+
- Default refresh_frequency is set 10 minutes from Sarama library defaults
1921
2022
# If your change doesn't affect end users or the exported elements of any package,
2123
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
@@ -24,4 +26,4 @@ subtext:
2426
# Include 'user' if the change is relevant to end users.
2527
# Include 'api' if there is a change to a library API.
2628
# Default: '[user]'
27-
change_logs: [api]
29+
change_logs: [user]

.chloggen/bearertokenauthextension-fix-grpc-token-refresh.yaml renamed to .chloggen/kafkametricsreceiver-cluster-admin-init.yaml

+3-3
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
change_type: bug_fix
55

66
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7-
component: bearertokenauthextension
7+
component: kafkametricsreceiver
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Load token lazily for gRPC AUTH to fix token refresh issue
10+
note: Fix incorrect cluster admin initialization in consumer scraper
1111

1212
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13-
issues: [36749]
13+
issues: [36818]
1414

1515
# (Optional) One or more lines of additional information to render under the primary note.
1616
# These lines will be padded with 2 spaces and then inserted directly into the document.
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
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: prometheusreceiver
8+
9+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10+
note: Deprecate metric start time adjustment in the prometheus receiver. It is being replaced by the metricstarttime processor.
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: [37186]
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: Start time adjustment is still enabled by default. To disable it, enable the |
19+
receiver.prometheusreceiver.RemoveStartTimeAdjustment feature gate.
20+
21+
# If your change doesn't affect end users or the exported elements of any package,
22+
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
23+
# Optional: The change log or logs in which this entry should be included.
24+
# e.g. '[user]' or '[user, api]'
25+
# Include 'user' if the change is relevant to end users.
26+
# Include 'api' if there is a change to a library API.
27+
# Default: '[user]'
28+
change_logs: []

.chloggen/prw-WAL-deadlock.yaml

-19
This file was deleted.

.chloggen/pubsubreceiver-turn-warn-into-reset-metric.yaml

-17
This file was deleted.

.chloggen/routing-deprecations-v120.yaml renamed to .chloggen/regex-deprecation.yaml

+3-3
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
44
change_type: breaking
55

66
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
7-
component: routingconnector
7+
component: processor/k8sattributes
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Remove `match_once` configuration parameter.
10+
note: "Move k8sattr.fieldExtractConfigRegex.disallow feature gate to stable"
1111

1212
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
13-
issues: [36824]
13+
issues: [25128]
1414

1515
# (Optional) One or more lines of additional information to render under the primary note.
1616
# These lines will be padded with 2 spaces and then inserted directly into the document.

.github/ALLOWLIST

+23-5
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,27 @@ internal/common
1919

2020
## DEPRECATED components
2121

22+
# Start deprecated components list
23+
24+
25+
26+
# End deprecated components list
27+
2228
## UNMAINTAINED components
23-
exporter/kineticaexporter/
24-
exporter/opensearchexporter/
25-
extension/observer/ecstaskobserver/
26-
receiver/awscloudwatchmetricsreceiver/
27-
receiver/rabbitmqreceiver/
29+
30+
# Start unmaintained components list
31+
32+
exporter/kineticaexporter
33+
exporter/opensearchexporter
34+
extension/observer/ecstaskobserver
35+
receiver/awscloudwatchmetricsreceiver
36+
receiver/couchdbreceiver
37+
receiver/elasticsearchreceiver
38+
receiver/memcachedreceiver
39+
receiver/mysqlreceiver
40+
receiver/postgresqlreceiver
41+
receiver/rabbitmqreceiver
42+
receiver/zookeeperreceiver
43+
scraper/zookeeperscraper
44+
45+
# End unmaintained components list

0 commit comments

Comments
 (0)