vcenter receiver host perf metric datapoints from 5 to 1

Author: StefanKurek

.chloggen/vcenter-receiver_remove_extra_host_perf_metrics.yaml

@@ -0,0 +1,41 @@
+# 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: vcenterreceiver
+
+# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
+note: "Removes the ability to sent 5 historical metrics per collection for Host Resource performance metrics."
+
+# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
+issues: [34708]
+
+# (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: |
+Sending 5 historical metrics already did not match up with what was being done with the VM performance metrics.
+It could easily lead to situations where timetamps were the tail end of these 5 datapoints would end up being
+picked up by the following collection as well. This change also fixes an issue with the googlecloud exporter
+seeing these datapoints (20s apart) as duplicates. Following is the list of affected metrics which will now only
+report a single datapoint per set of unique attribute values.
+- vcenter.host.cpu.reserved
+- vcenter.host.disk.latency.avg
+- vcenter.host.disk.latency.max
+- vcenter.host.disk.throughput
+- vcenter.host.network.packet.drop.rate
+- vcenter.host.network.packet.error.rate
+- vcenter.host.network.packet.rate
+- vcenter.host.network.throughput
+- vcenter.host.network.usage
+
+# 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]