Merge branch 'main' into main

.chloggen/mx-psi_remove-NewFlags.yaml → .chloggen/automated-status-on-start.yaml

@@ -1,25 +1,25 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: featuregate
+component: statusreporting
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Remove deprecate function `featuregate.NewFlag`
+note: Automates status reporting upon the completion of component.Start().
 
 # One or more tracking issues or pull requests related to the change
-issues: [8727]
+issues: [7682]
 
 # (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: Use `featuregate.Registry`'s `RegisterFlags` method instead.
+subtext:
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'
 # 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: [api]
+change_logs: []

.chloggen/debug-exporter-default-verbosity-basic.yaml → .chloggen/codeboten_enable-otel-by-default.yaml

@@ -4,22 +4,22 @@
 change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: exporter/debug
+component: service
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Change default `verbosity` from `normal` to `basic`
+note: "add resource attributes as labels to otel metrics to ensures backwards compatibility with OpenCensus metrics."
 
 # One or more tracking issues or pull requests related to the change
-issues: [8844]
+issues: [9029]
 
 # (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 change has currently no effect, as `basic` and `normal` verbosity share the same behavior. This might change in the future though, with the `normal` verbosity being more verbose than it currently is (see https://github.com/open-telemetry/opentelemetry-collector/issues/7806). This is why we are changing the default to `basic`, which is expected to stay at the current level of verbosity (one line per batch).
+subtext:
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'
 # 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: [user]
+change_logs: []

.chloggen/codeboten_fix-missing-metrics.yaml

@@ -0,0 +1,28 @@
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: bug_fix
+
+# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
+component: exporterhelper
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: fix missed metric aggregations
+
+# One or more tracking issues or pull requests related to the change
+issues: [9048]
+
+# (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 ensures that context cancellation in the exporter doesn't interfere with metric aggregation. The OTel
+  SDK currently returns if there's an error in the context used in `Add`. This means that if there's a
+  cancelled context in an export, the metrics are now recorded.
+
+# Optional: The change log or logs in which this entry should be included.
+# e.g. '[user]' or '[user, api]'
+# 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: []

.chloggen/dmitryax_use-func-instead-of-converter-interface.yaml → .chloggen/http2ping.yaml

@@ -1,20 +1,25 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: breaking
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: exporterhelper
+component: config/confighttp
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Replace converter interface with function in the new experimental exporter helper.
+note: Exposes http/2 transport settings to enable health check and workaround golang http/2 issue https://github.com/golang/go/issues/59690
 
 # One or more tracking issues or pull requests related to the change
-issues: [8122]
+issues: [9022]
+
+# (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:
 
 # Optional: The change log or logs in which this entry should be included.
 # e.g. '[user]' or '[user, api]'
 # 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: [api]
+change_logs: []

.chloggen/codeboten_rm-generated-jsonschema-code.yaml → .chloggen/remove_noisy_log.yaml

@@ -1,16 +1,16 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: deprecation
+change_type: bug_fix
 
 # The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
-component: telemetry
+component: exporterhelper
 
 # A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: deprecate jsonschema generated types
+note: Remove noisy log
 
 # One or more tracking issues or pull requests related to the change
-issues: [15009]
+issues: [9017]
 
 # (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.
@@ -22,4 +22,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: [api]
+change_logs: []

.github/ISSUE_TEMPLATE/stabilization.md

@@ -0,0 +1,25 @@
+---
+name: Module stabilization
+about: Stabilize a module before a 1.0 release
+title: 'Stabilize module X'
+labels: 'stabilization'
+assignees: ''
+---
+
+Before stabilizing a module, an approver or maintainer must make sure that the following criteria have been met for at least two successive minor version releases:
+
+- [ ] No open issues or PRs in the module that would require breaking changes
+- [ ] No TODOs in the module code that would require breaking changes
+- [ ] No deprecated symbols in the module
+- [ ] No symbols marked as experimental in the module
+- [ ] The module follows the [Coding guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/CONTRIBUTING.md)
+
+Please also make sure to publicly announce our intent to stabilize the module on:
+
+- [ ] The #otel-collector CNCF Slack Channel
+- [ ] The #opentelemetry CNCF Slack channel
+- [ ] A Collector SIG meeting (if unable to attend, just add to the agenda)
+
+To help other people verify the above criteria, please link to the announcement and other links used to complete the above in a comment on this issue.
+
+Once all criteria are met, close this issue by moving this module to the `stable` module set.