Skip to content

Commit b753572

Browse files
committed
Merge branch 'main' into add-new-oracledb-metrics
2 parents 49e3d1a + 957c063 commit b753572

File tree

1,529 files changed

+42277
-31032
lines changed

Some content is hidden

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

1,529 files changed

+42277
-31032
lines changed

.chloggen/replace-pc-and-add-intial-contextinference-support.yaml renamed to .chloggen/add-global-conditions-and-group-error-mode-support.yaml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,19 @@ change_type: enhancement
77
component: processor/transformprocessor
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Replace parser collection implementations with `ottl.ParserCollection` and add initial support for expressing statement's context via path names.
10+
note: Add support for global conditions and error mode overrides.
1111

1212
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
1313
issues: [29017]
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+
Global conditions are now available for context-inferred structured configurations, allowing the use of fully
20+
qualified paths. Additionally, a new configuration key called `error_mode` has been added to the context statements group.
21+
This key determines how the processor reacts to errors that occur while processing that specific group of statements.
22+
When provided, it overrides the top-level error mode, offering more granular control over error handling.
1923
2024
# If your change doesn't affect end users or the exported elements of any package,
2125
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/codeboten_opampsupervisor-emit-otlp.yaml renamed to .chloggen/add-more-vecenter-receiver-virtual-machine-preformace-metrics.yaml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
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: opampsupervisor
7+
component: vcenterreceiver
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: report own metrics via OTLP instead of prometheus receiver
10+
note: Adds three more vCenter virtual machine performance metrics
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: [37346]
13+
issues: [37488]
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.
@@ -24,4 +24,4 @@ subtext:
2424
# Include 'user' if the change is relevant to end users.
2525
# Include 'api' if there is a change to a library API.
2626
# Default: '[user]'
27-
change_logs: []
27+
change_logs: [user]

.chloggen/add-multiple-endpoints-support-httpcheckreceiver.yaml

Lines changed: 0 additions & 13 deletions
This file was deleted.

.chloggen/receiver-otlpjson-token-attr.yaml renamed to .chloggen/bearertokenauthextension-fix-grpc-token-refresh.yaml

Lines changed: 3 additions & 3 deletions
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: otlpjsonfilereceiver
7+
component: bearertokenauthextension
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Include file attributes and append it to the log record
10+
note: Load token lazily for gRPC AUTH to fix token refresh issue
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: [36641]
13+
issues: [36749]
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.
Lines changed: 27 additions & 27 deletions
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: envoyalsreceiver
8-
9-
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Add a new receiver for the Envoy ALS (Access Log Service).
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: [36464]
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: []
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]

.chloggen/cf_feature_flag_update.yaml

Lines changed: 0 additions & 28 deletions
This file was deleted.

.chloggen/codeboten_add-support-for-headers.yaml renamed to .chloggen/codeboten_ensure-onclose-hookedup.yaml

Lines changed: 3 additions & 3 deletions
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)
77
component: opampsupervisor
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: add support for headers configuration for reporting own telemetry
10+
note: The OnConnectionClose was not correctly connected for the supervisor.
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: [37353]
13+
issues: [37761]
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.

.chloggen/datadogconnector-add-stats-obfuscation.yaml

Lines changed: 0 additions & 35 deletions
This file was deleted.

.chloggen/deprecate-created-metric-beta2stable.yaml

Lines changed: 0 additions & 27 deletions
This file was deleted.

.chloggen/elasticsearchexporter_log_body.yaml renamed to .chloggen/elasticsearchexporter-goelasticsearchv8.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,10 @@ change_type: breaking
77
component: elasticsearchexporter
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Consistently store the structured body of logs and events in `body.structured` in `otel` mode
10+
note: Use go-elasticsearch/v8, require minimum version of ES 7.17.x or 8.x
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: [37387]
13+
issues: [32454]
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.

.chloggen/elasticsearchexporter_mutates-data-false.yaml

Lines changed: 0 additions & 27 deletions
This file was deleted.

.chloggen/expo-histogram-fix-downscaling.yaml

Lines changed: 0 additions & 27 deletions
This file was deleted.

.chloggen/cumulative-to-delta-processor-metric-type-filter.yaml renamed to .chloggen/firehose-unmarshal-record.yaml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@
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: cumulativetodeltaprocessor
7+
component: awsfirehosereceiver
88

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Add metric type filter for cumulativetodelta processor
10+
note: Refactor unmarshallers to implement pdata unmarshaler interfaces
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: [33673]
13+
issues: [37361]
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.

.chloggen/gcp-gce-mig.yaml

Lines changed: 0 additions & 27 deletions
This file was deleted.

.chloggen/clickhouse_examples.yaml renamed to .chloggen/hostmetricsreceiver-feature.yaml

Lines changed: 4 additions & 4 deletions
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: breaking
55

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

99
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10-
note: Adding missing examples of DDL created by the clickhouse exporter
10+
note: "Remove receiver.hostmetrics.normalizeProcessCPUUtilization feature gate"
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: [35903]
13+
issues: [34763]
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.

0 commit comments

Comments
 (0)