Merge branch 'main' into receiver/cloudfoundryreceiver

.chloggen/telemetrygen-logs-grpc-metadata.yaml → .chloggen/add_container_parser.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: telemetrygen
+component: filelogreceiver
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add headers to gRPC metadata for logs
+note: Add container operator parser
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32668]
+issues: [31959]
 
 # (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/supervisor-persists-remote-config.yaml → .chloggen/always-add-span-name-dimension.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: cmd/opampsupervisor
+component: exceptionsconnector
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Persist collector remote config & telemetry settings
+note: Make span name a default dimension for ouput metrics and log records.
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [21078]
+issues: [32162]
 
 # (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/xrayexporter-segment-name-fix.yaml → .chloggen/awss3receiver_impl_mvp.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: bug_fix
+change_type: new_component
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: awsxrayexporter
+component: awss3receiver
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: make comma`,` as invalid char for x-ray segment name
+note: "Initial implementation of the AWS S3 receiver."
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32610]
+issues: [30750]
 
 # (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/pass_telemetry_settings_to_stanza_ops.yaml → .chloggen/chore_move-custom-messages.yaml

@@ -4,22 +4,20 @@
 change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: pkg/stanza
+component: opampextension
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Pass TelemetrySettings to the Build method of the Builder interface
+note: Move custom message interfaces to separate package
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32662, 31256]
+issues: [32950]
 
 # (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: |
- The reason for this breaking change is to pass in the component.TelemetrySettings
- so as to use them later in various ways:
- - be able to report state statistics and telemetry in general
- - be able to switch from SugaredLogger to Logger
+ Moves `CustomCapabilityRegistry`, `CustomCapabilityHandler`, and `CustomCapabilityRegisterOption` to a new module.
+ These types can now be found in the new `github.com/open-telemetry/opentelemetry-collector-contrib/extension/opampcustommessages` module.
 
 # If your change doesn't affect end users or the exported elements of any package,
 # you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/otlpencoding_alpha.yaml → .chloggen/connector-testbed.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: otlpencodingextension
+component: testbed
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Move otlpencodingextension to alpha
+note: Add the use of connectors to the testbed
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32701]
+issues: [30165]
 
 # (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: [api]

.chloggen/bugfix_missing-resource-timestamp.yaml → .chloggen/deltatocumulative-exphist.yaml

@@ -1,21 +1,23 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: "enhancement"
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: prometheusremotewrite
+component: deltatocumulativeprocessor
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Modify prometheusremotewrite.FromMetrics to only generate target_info if there are metrics, as otherwise you can't deduce the timestamp.
+note: exponential histogram accumulation
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32318]
+issues: [31340]
 
 # (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:
+ accumulates exponential histogram datapoints by adding respective bucket counts.
+ also handles downscaling, changing zero-counts, offset adaptions and optional fields
 
 # If your change doesn't affect end users or the exported elements of any package,
 # you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/fix-cwlogs-xray.yaml → .chloggen/drosiek-exporter-logs.yaml

@@ -1,21 +1,25 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: awsxrayreceiver
+component: sumologicexporter
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Retain CloudWatch Log Group when translating X-Ray segments 
+note: change logs behavior
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [31784]
+issues: [31479]
 
 # (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:
+subtext: |
+ * set OTLP as default format
+ * add support for OTLP format
+ * do not support metadata attributes
+ * do not support source headers
 
 # If your change doesn't affect end users or the exported elements of any package,
 # you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/bugfix_target-info-required-attrs.yaml → .chloggen/drosiek-exporter-metrics.yaml

@@ -1,21 +1,26 @@
 # Use this changelog template to create an entry for release notes.
 
 # One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
-change_type: bug_fix
+change_type: breaking
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
-component: prometheusremotewrite
+component: sumologicexporter
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Change prometheusremotewrite.FromMetrics so that the target_info metric is only generated if at least one identifying OTel resource attribute (service.name and/or service.instance.id) is defined.
+note: change metrics behavior
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32148]
+issues: [31479]
 
 # (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:
+subtext: |
+ * remove suppport for carbon2 and graphite
+ * add support for otlp format
+ * do not support metadata attributes
+ * do not support source headers
+ * set otlp as default metrics format
 
 # If your change doesn't affect end users or the exported elements of any package,
 # you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/drosiek-sumologicexporter-prom-formatter.yaml → .chloggen/drosiek-sumo-sticky-session.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: bug_fix
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
 component: sumologicexporter
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "do not replace `.` with `_` for prometheus format"
+note: add sticky session support
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [31479]
+issues: [32315]
 
 # (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/elasticsearchexporter_retry-on-status.yaml → .chloggen/elasticsearchexporter_go-docappender.yaml

@@ -7,18 +7,21 @@ change_type: enhancement
 component: elasticsearchexporter
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: Add retry.retry_on_status config
+note: Replace go-elasticsearch BulkIndexer with go-docappender
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32584]
+issues: [32378]
 
 # (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: |
- Previously, the status codes that trigger retries were hardcoded to be 429, 500, 502, 503, 504.
- It is now configurable using `retry.retry_on_status`, and defaults to `[429, 500, 502, 503, 504]` to avoid a breaking change.
- To avoid duplicates, it is recommended to configure `retry.retry_on_status` to `[429]`, which would be the default in a future version.
+ Replace go-elasticsearch BulkIndexer with go-docappender bulk indexer, in preparation for future reliability fixes.
+ As a result of this change, there are minor behavioral differences:
+ - flush timeout is now enforced on client side
+ - oversize payload special handling is now removed
+ - go-docappender uses bulk request filterPath which means bulk response is smaller, less JSON parsing and lower CPU usage
+ - document level retry debug logging is removed as retries are done transparently
 
 # If your change doesn't affect end users or the exported elements of any package,
 # you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

.chloggen/exporter-elasticsarch-more-ecs-mode.yaml

@@ -0,0 +1,27 @@
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: enhancement
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: elasticsearchexporter
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Converts more SemConv fields in OTel events to ECS fields in Elasticsearch documents when `mapping.mode: ecs` is specified."
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [31694]
+
+# (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:
+
+# If your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# 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]

.chloggen/fix_vcenter-datastore-attr-warning.yaml → .chloggen/feat_vcenter-performance-tweaks.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: bug_fix
+change_type: enhancement
 
 # The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
 component: vcenterreceiver
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Adds `vcenter.cluster.name` attributes warning log related to Datastore resource"
+note: "Refactors how and when client makes calls in order to provide for faster collection times."
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32674]
+issues: [31837]
 
 # (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/fix_vcenter-cluster-vm-count-metric.yaml → .chloggen/feat_vcenter-vm-add-packet-drop-metric.yaml

@@ -7,10 +7,10 @@ change_type: bug_fix
 component: vcenterreceiver
 
 # A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
-note: "Updates the `vcenter.cluster.vm.count` metric to also report suspended VM counts"
+note: "Adds inititially disabled packet drop rate metric for VMs."
 
 # Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
-issues: [32803]
+issues: [32929]
 
 # (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/fix-remotetap-limit.yaml

@@ -0,0 +1,30 @@
+# Use this changelog template to create an entry for release notes.
+
+# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
+change_type: breaking
+
+# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
+component: remotetapprocessor
+
+# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: Make the `limit` configuration work properly.
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [32385]
+
+# (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: |
+ The `limit` configuration was ignored previously, but now it works according to the configuration and documentation.
+ Nothing is required of users.
+ See the remotetapprocessor's `README.md` for details.
+
+# If your change doesn't affect end users or the exported elements of any package,
+# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.
+# 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: []