Merge branch 'main' into goleak_signalfxexp

.chloggen/ottl_grok.yaml → .chloggen/add-large-file-tests.yaml

@@ -4,13 +4,13 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: pkg/ottl
+component: testbed
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Introduce ExtractGrokPatterns converter
+note: Add test case scenarios to handle large files to existing testbed.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32593]
+issues: [34288]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.

.chloggen/mo-silent_fix-34315.yaml → .chloggen/apachereceiver_fix_panic_on_invalid_endpoint.yaml

@@ -4,13 +4,13 @@
 change_type: 'bug_fix'
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: azuremonitorreceiver
+component: apachereceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add Azure China as a `cloud` option.
+note: Fix panic on invalid endpoint configuration
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [34315]
+issues: [34992]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.

.chloggen/ottl_sha512_converter.yaml → .chloggen/avoid_rendering_whole_event_to_obtain_provider_name_windowseventlogreceiver.yaml

@@ -4,13 +4,13 @@
 change_type: 'enhancement'
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: pkg/ottl
+component: windowseventlogreceiver
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Introduce `sha512` converter to generate SHA-512 hash/digest from given payload.
+note: Avoid rendering the whole event to obtain the provider name
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [34007]
+issues: [34755]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
@@ -24,4 +24,4 @@ subtext:
 # Include 'user' if the change is relevant to end users.
 # Include 'api' if there is a change to a library API.
 # Default: '[user]'
-change_logs: []
+change_logs: [user]

.chloggen/es_add_default_metrics.yaml → .chloggen/clickhouse-upgrade-statuscode-kind.yaml

@@ -4,23 +4,24 @@
 change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: elasticsearchreceiver
+component: clickhouseexporter
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Enable more index metrics by default
+note: Upgrade trace SpanKind and StatusCode string values
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [34396]
+issues: [34799]
 
 # (Optional) One or more lines of additional information to render under the primary note.
 # These lines will be padded with 2 spaces and then inserted directly into the document.
 # Use pipe (|) for multiline entries.
 subtext: |
-  This enables the following metrics by default: 
-  `elasticsearch.index.documents`
-  `elasticsearch.index.operations.merge.current`
-  `elasticsearch.index.segments.count`
-  To preserve previous behavior, update your Elasticsearch receiver configuration to disable these metrics.
+  This change updates the output of the trace SpanKind and StatusCode fields to be consistent
+  with the specification's enum values. While this change will not break any deployments, it may affect
+  queries dependent on the old enum names.
+  
+  For more details on old->new values, see this related PR:
+  https://github.com/open-telemetry/opentelemetry-collector/pull/6250
 
 
 # If your change doesn't affect end users or the exported elements of any package,