[receiver/vcenter] Adds New Packet Dropped Rate Metric for VMs #32930

StefanKurek · 2024-05-07T20:04:32Z

Description:
Adds new default disabled (with Warning log for default enabled on next release) metric vcenter.vm.network.packet.drop.rate for Virtual Machines.

This metric makes use of the droppedRx and droppedTx Network performance metrics detailed here for Virtual machines. This would use the same metric attributes as the other VM packet metrics and closely match vcenter.vm.network.packet.rate in every other way.

Link to tracking Issue:
#32929

Testing:
Unit/integration tests updated and tested. Local environment tested.

Documentation:
New documentation generated based on the metadata.

receiver/vcenterreceiver/metadata.yaml

…telemetry#32930) **Description:** <Describe what has changed.> Adds new default disabled (with Warning log for default enabled on next release) metric `vcenter.vm.network.packet.drop.rate` for Virtual Machines. This metric makes use of the `droppedRx` and `droppedTx` Network performance metrics detailed [here](https://vdc-repo.vmware.com/vmwb-repository/dcr-public/d1902b0e-d479-46bf-8ac9-cee0e31e8ec0/07ce8dbd-db48-4261-9b8f-c6d3ad8ba472/network_counters.html) for Virtual machines. This would use the same metric attributes as the other VM packet metrics and closely match `vcenter.vm.network.packet.rate` in every other way. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#32929 **Testing:** <Describe what testing was performed and which tests were added.> Unit/integration tests updated and tested. Local environment tested. **Documentation:** <Describe the documentation added.> New documentation generated based on the metadata.

commit 41d853ddd4be38c9f65634b911b1b623e5ec8012 Author: Curtis Robert <crobert@splunk.com> Date: Mon May 13 06:30:42 2024 -0700 [chore][receiver/sqlserver] Document Windows-only metrics (#32944) **Description:** <Describe what has changed.>  The referenced metrics are being gathered from Windows perf counters, thus they're currently only available on Windows. With the introduction of direct connection and other supported OSs, I think it would be good to be clear to users about metric availability. commit 2502368da65e9eaf1d3228ec205f6ebe6c505564 Author: Curtis Robert <crobert@splunk.com> Date: Mon May 13 06:28:14 2024 -0700 [chore][exporter/rabbitmq] Add missing code owner (#32984) **Description:** <Describe what has changed.>  @atoulme [volunteered to be the sponsor](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/28891#issuecomment-1981402878) of this component, so I believe he should be listed as a code owner. From [CONTRIBUTING.md](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#adding-new-components): ``` A sponsor is an approver who will be in charge of being the official reviewer of the code and become a code owner for the component. ``` **Link to tracking Issue:** <Issue number if applicable> #28891 commit a133a8efefbe34dd45d8d4c8473ebbd75f4bdcc3 Author: Dominik Rosiek <58699848+sumo-drosiek@users.noreply.github.com> Date: Mon May 13 10:05:36 2024 +0200 [exporter/sumologic] change logs behavior (#32939) **Description:** * set OTLP as default format * add support for OTLP format * do not support metadata attributes * do not support source headers **Link to tracking Issue:** #32315 **Testing:** * unit tests **Documentation:** * inline comments * readme --------- Signed-off-by: Dominik Rosiek <drosiek@sumologic.com> commit c5485bf4ddef9c0acce85bff1fed60f669aabf6a Author: Joshua MacDonald <jmacd@users.noreply.github.com> Date: Mon May 13 00:47:46 2024 -0700 OpenTelemetry Protocol with Apache Arrow Exporter component (#31996) **Description:** This is the same code as OTel-Arrow at https://github.com/open-telemetry/otel-arrow/releases/tag/v0.23.0 (plus [backported lint and test fixes](https://github.com/open-telemetry/otel-arrow/commit/0910113d46454c80881db840e21f25485dce2499)). Only import statements change here, to match the host repository. **Link to tracking Issue:** #26491 **Testing:** Test coverage is approximately 90%. **Documentation:** I double-checked and the existing README had only a few updates needed. commit 82a828b798cd9074b9a3aec95c2115e825042799 Author: Stefan Kurek <stefan.kurek@observiq.com> Date: Fri May 10 14:30:09 2024 -0400 [chore] vcenterreceiver Adds Accidentally Removed Unit Test Configs/Results (#32987) **Description:** <Describe what has changed.> In this [PR](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32913), I accidentally removed all the enabled configs from the 2nd set of unit tests. This was incorrect as there are still 4 of them that are currently disabled by default. This is rectifying that by adding those back in. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> This change is for the unit tests only **Documentation:** <Describe the documentation added.> NA commit cf2afd0db91d01e001804efedbb789e6015a4a8b Author: Juraj Michálek <juraj.michalek132@gmail.com> Date: Fri May 10 16:46:41 2024 +0200 chore: remote write exporter retry on 429 (#31924) **Description:** <Describe what has changed.> This PR adds an option to retry the remote write requests when the receiving backend responds with 429 http status code,  **Link to tracking Issue:** #31032 **Testing:** <Describe what testing was performed and which tests were added.> Added tests covering the case. **Documentation:** <Describe the documentation added.> Not sure what's the pattern for documenting feature flags. --------- Co-authored-by: Anthony Mirabella <a9@aneurysm9.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> Co-authored-by: David Ashpole <dashpole@google.com> commit bc2ff482f0669c00a17f8ea2004d8d6d164abd8b Author: Evan Bradley <11745660+evan-bradley@users.noreply.github.com> Date: Fri May 10 09:55:02 2024 -0400 [chore] Add contrib confmap providers to otelcontribcol (#32916) **Description:** Contrib hosts two confmap providers which aren't in the local binary. We should add them so we can test them with a live system. cc @Aneurysm9 @driverpt @atoulme --------- Co-authored-by: Evan Bradley <evan-bradley@users.noreply.github.com> commit cde2b0af181cae8333f1200e8f6750bfb4af7cf2 Author: Brandon Johnson <brandon.johnson@observiq.com> Date: Fri May 10 08:45:08 2024 -0400 [opampextension]: Move custom message interface to separate module (#32951) **Description:** <Describe what has changed.> * Breaks our the custom message interface to a separate module, so other components can use the interface without needing to import the `opampextension` module in its entirety. We could temporarily alias the old methods if we'd like, but I think that the CustomMessage stuff has been so short lived that, in addition to the alpha status of the opampextension component, it feels justified to just skip the deprecation process and move it to a new module. **Link to tracking Issue:** Closes #32950 **Testing:** * Covered by existing unit tests **Documentation:** * Added more documentation on usage in the new module. * Modified opampextension docs to point to the new module. commit 0894a437bda260e5c4770914c94ab674f1172fce Author: Curtis Robert <crobert@splunk.com> Date: Fri May 10 04:39:17 2024 -0700 [chore][CONTRIBUTING.md] Update adding component directions (#32957) **Description:** <Describe what has changed.>  This is two main changes: 1. Remove `goleak` section. It's now added by default by mdatagen, there's nothing required of users here. 2. Add information and reformat the `Last steps` section of adding a new component. - Move the directions to be bullet points - Add `make generate` to make sure the component's README is updated properly - Explicitly point out that stability and distribution needs to be updated in `metadata.yaml` - Add step for adding the component to the releases repo. My understanding is that if a component is `Alpha`, it should be included in the release, so I've made that a noted part of the steps here. (Let me know if we should word this in a more "optional" way.) --------- Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> commit fba86583b486fd40f190f3c994b8d9a84c81723c Author: Huy Vo <hvoam@amazon.com> Date: Fri May 10 04:34:09 2024 -0700 Add connector usage to the testbed (#32881) **Description:** Added a new component to the testbed called DataConnectors which allows connectors to be added to the testbed config. Also, added a sample connector correctness test using the routingconnector as an example of the usage. **Link to tracking Issue:** #30165 **Testing:** Sample correctness test using routingconnector. **Documentation:** Will update the testbed README with new addition. --------- Co-authored-by: Bryan Aguilar <bryaag@amazon.com> commit 6015403943ced9d3014c2249cbb41906e9a3fb32 Author: Ankit Patel <8731662+ankitpatel96@users.noreply.github.com> Date: Fri May 10 00:57:05 2024 -0400 Instantiate ID in pkg/stanza/adapter tests (#32966) **Description:** <Describe what has changed.> In https://github.com/open-telemetry/opentelemetry-collector/pull/10069, I am making Type an interface. This means the zero value of Type will be nil - which will cause this test to fail. Initializing ID instead of relying on the zero value fixes this --------- Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> Co-authored-by: Bogdan Drutu <bogdandrutu@gmail.com> commit a4b0e5928e46c23a0ab42e2a72d468156d62051b Author: lkwronski <45148751+lkwronski@users.noreply.github.com> Date: Fri May 10 00:06:25 2024 +0200 [processor/transform] Add common where clause (#31491) **Description:** Add global conditions with where clause  **Link to tracking Issue:** Fixes #27830 **Testing:** Unit tests **Documentation:** TODO ~~The main objective is to extend the `ContextStatements` struct by adding a new `Conditions` parameter. By introducing `Conditions` to `ContextStatements`, we can now apply a global condition to all related statements in `WithStatementSequenceGlobalConditions` function.~~ Thanks in advance for your feedback! If this changes will be fine, I will add common where clause into another context `span`, `metrics`. commit c0512b91f0ad83d2e7c56c193bc8503693ea569c Author: Michal Pristas <michal.pristas@gmail.com> Date: Thu May 9 21:06:40 2024 +0200 [pkg/ottl] Added support for timezone in Time converter (#32479) **Description:** Added support for default timezone in Time converter. Timezone is optional and can be specified as so: `Time("2023-05-26 12:34:56", "%Y-%m-%d %H:%M:%S", "America/New_York")` **Link to tracking Issue:** #32140 **Testing:** Unit tests added **Documentation:** Documentation in ottl/Readme updated --------- Co-authored-by: Tyler Helmuth <12352919+TylerHelmuth@users.noreply.github.com> Co-authored-by: Evan Bradley <11745660+evan-bradley@users.noreply.github.com> commit 7fd145b5fceca5faadd35f5bcfca2d043fbd6e52 Author: shalper2 <99686388+shalper2@users.noreply.github.com> Date: Thu May 9 11:37:07 2024 -0500 [chore][receiver/splunkenterprise] Splunkent wire component (#32795) **Description:** Graduate splunkenterprise receiver component to alpha **Link to tracking Issue:** **Testing:** Performed `make otelcontribcol` and ran resulting binary with the following config: ```yaml extensions: basicauth/indexer: client_auth: username: admin password: securityFirst basicauth/cluster_master: client_auth: username: admin password: securityFirst receivers: splunkenterprise: indexer: auth: authenticator: basicauth/indexer endpoint: "https://localhost:8089/" timeout: 45s cluster_master: auth: authenticator: basicauth/cluster_master endpoint: "https://localhost:8089/" timeout: 45s exporters: otlp: endpoint: 127.0.0.1:8000 service: extensions: [basicauth/indexer, basicauth/cluster_master] pipelines: metrics: receivers: [splunkenterprise] exporters: [otlp] ``` and received the following output: ``` sh ~> ./otelcontribcol_linux_amd64 --config=file:config.yaml 2024-05-08T17:34:33.032-0500 info service@v0.100.0/service.go:102 Setting up own telemetry... 2024-05-08T17:34:33.032-0500 info service@v0.100.0/telemetry.go:103 Serving metrics {"address": ":8888", "level": "Normal"} 2024-05-08T17:34:33.032-0500 info receiver@v0.100.0/receiver.go:310 Development component. May change in the future. {"kind": "receiver", "name": "splunkenterprise", "data_type": "metrics"} 2024-05-08T17:34:33.033-0500 info service@v0.100.0/service.go:169 Starting otelcontribcol... {"Version": "0.100.0-dev", "NumCPU": 16} 2024-05-08T17:34:33.033-0500 info extensions/extensions.go:34 Starting extensions... 2024-05-08T17:34:33.033-0500 info extensions/extensions.go:37 Extension is starting... {"kind": "extension", "name": "basicauth/cluster_master"} 2024-05-08T17:34:33.033-0500 info extensions/extensions.go:52 Extension started. {"kind": "extension", "name": "basicauth/cluster_master"} 2024-05-08T17:34:33.033-0500 info extensions/extensions.go:37 Extension is starting... {"kind": "extension", "name": "basicauth/indexer"} 2024-05-08T17:34:33.033-0500 info extensions/extensions.go:52 Extension started. {"kind": "extension", "name": "basicauth/indexer"} 2024-05-08T17:34:33.033-0500 info service@v0.100.0/service.go:195 Everything is ready. Begin running and processing data. ``` indicating that the collector was able to successfully start with the component configured. **Documentation:** Documentation was updated to indicate change in status from development to alpha --------- Co-authored-by: Curtis Robert <crobert@splunk.com> commit e57185cb2c48e6e11ab8db73e63f4b36adcc2134 Author: Raj Nishtala <113392743+rnishtala-sumo@users.noreply.github.com> Date: Thu May 9 11:36:03 2024 -0400 fix(test): Skip flaky test around forcing collector re-registration until the root cause is confirmed (#32937) **Description:** Remove flaky test around forcing collector re-registration until the root cause is confirmed **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32785 **Testing:** Unit tests commit bcc9fe467b2b7937ac709fea15e3f65179aa11df Author: Carson Ip <carsonip@users.noreply.github.com> Date: Thu May 9 16:19:04 2024 +0100 [exporter/elasticsearch] Replace go-elasticsearch BulkIndexer with go-docappender (#32359) **Description:** <Describe what has changed.>  Replace go-elasticsearch BulkIndexer with go-docappender BulkIndexer for Flush function in preparation for reliability fixes. Maintain similar interface and implementation to go-elasticsearch BulkIndexer. Further changes to expose individual `docappender.BulkIndexer` instances are needed down the road but it is out of the scope of this PR. Implications of this change: - 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 ~~Blocked by #32585~~ **Link to tracking Issue:** <Issue number if applicable> Fixes #32378 **Testing:** Integration test is passing --------- Co-authored-by: Vishal Raj <vishal.raj@elastic.co> commit 17f5711fefff4e2cc26cf3e6414c676d33a0ba61 Author: Curtis Robert <crobert@splunk.com> Date: Thu May 9 08:13:31 2024 -0700 [chore][receiver/splunkenterprise] Add header to README (#32956) **Description:** <Describe what has changed.>  The readme for the Splunk Enterprise receiver does not currently have the autogenerated header. This was missing because `mdatagen` requires `` and `` to know where to insert the generated data. commit 59d08fcba1d71d92ee9abb3ede7f6c353717bb39 Author: Curtis Robert <crobert@splunk.com> Date: Thu May 9 03:26:49 2024 -0700 [chore][CI/CD][arm] Trigger arm runs on label (#32955) **Description:** <Describe what has changed.>  I found in https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32948 that the label `Run ARM` has been added, but the `build-and-test-arm / arm-unittest-matrix (pull_request) ` workflow is still skipped. This is because the `label` action does not trigger a retry. From [documentation](https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request): ``` if no activity types are specified, the workflow runs when a pull request is opened or reopened or when the head branch of the pull request is updated. ``` We need to specify that labelling issues should trigger the workflow to check to see if it needs to run again. I've copied the added section from the Windows workflow. I also added that we should only run on PRs against `main`. **Testing:** This PR shows it's working as it should now. Arm test was [originally skipped](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/9009218559/job/24753003216?pr=32955), but after adding the label, tests [have started](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/9009223570/job/24753017935?pr=32955) commit b1bbd587d4adc89f9cbc34754c4e67123d8e5283 Author: Daniel Jaglowski <jaglows3@gmail.com> Date: Wed May 8 12:38:49 2024 -0500 [chore][fileconsumer] Skip flaky TestFlushPeriodEOF on windows (#32946) See https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32715 This also adds a bit more debugging info for other tests which fail on the same expectation, since it's not very obvious what was expected vs actually found. commit fec5543b69f0266130b40b440b763f89568816fb Author: Stefan Kurek <stefan.kurek@observiq.com> Date: Wed May 8 13:38:19 2024 -0400 [receiver/vcenter] Switches Over Metadata Configs Waiting for v0.100.0 Release (#32913) **Description:** <Describe what has changed.> A number of configurations were disabled by default and had warnings that they were going to be enabled in v0.101.0 (1 metric had a warning that it was going to be removed). Now that v0.100.0 has been release, I have removed all of these warnings, and made the modifications that the warnings "warned" about. I have also updated the tests to reflect this. **Link to tracking Issue:** <Issue number if applicable> #32803 #32805 #32821 #32531 #32557 **Testing:** <Describe what testing was performed and which tests were added.> Unit/integration tests updated and tested. Local environment tested. **Documentation:** <Describe the documentation added.> New documentation generated based on the metadata. commit 497fed777540f5a627445804afacbe3b4ee33ba0 Author: lizeyuan <lzyutf8@163.com> Date: Thu May 9 01:20:05 2024 +0800 [remotetapprocessor] use 'time/rate' to limit traffic (#32481) bug: The remotetapprocessor `limit` configure doesn't work. how to fix: use `time/rate` to limit traffic. Resolves https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32385 --------- Co-authored-by: Andrzej Stencel <astencel@sumologic.com> commit f4a3147bc5006e01ea6c7b57f6980ce4864cdb79 Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Wed May 8 10:19:15 2024 -0700 fix(deps): update module github.com/open-telemetry/otel-arrow to v0.22.0 (#32105) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/otel-arrow](https://togithub.com/open-telemetry/otel-arrow) | `v0.18.0` -> `v0.22.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fopen-telemetry%2fotel-arrow/v0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fopen-telemetry%2fotel-arrow/v0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fopen-telemetry%2fotel-arrow/v0.18.0/v0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fopen-telemetry%2fotel-arrow/v0.18.0/v0.22.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>open-telemetry/otel-arrow (github.com/open-telemetry/otel-arrow)</summary> ### [`v0.22.0`](https://togithub.com/open-telemetry/otel-arrow/releases/tag/v0.22.0) [Compare Source](https://togithub.com/open-telemetry/otel-arrow/compare/v0.21.0...v0.22.0) Includes [#178](https://togithub.com/open-telemetry/otel-arrow/issues/178). [CHANGELOG](https://togithub.com/open-telemetry/otel-arrow/blob/main/CHANGELOG.md) ### [`v0.21.0`](https://togithub.com/open-telemetry/otel-arrow/releases/tag/v0.21.0) [Compare Source](https://togithub.com/open-telemetry/otel-arrow/compare/v0.20.0...v0.21.0) See the [CHANGELOG](https://togithub.com/open-telemetry/otel-arrow/blob/main/CHANGELOG.md). ### [`v0.20.0`](https://togithub.com/open-telemetry/otel-arrow/releases/tag/v0.20.0) [Compare Source](https://togithub.com/open-telemetry/otel-arrow/compare/v0.19.0...v0.20.0) ##### What's Changed - Backport lint fixes from OTel-Collector-Contrib PR 31996 by [@jmacd](https://togithub.com/jmacd) in [https://github.com/open-telemetry/otel-arrow/pull/163](https://togithub.com/open-telemetry/otel-arrow/pull/163) - Upgrade collector to v0.97.0 by [@moh-osman3](https://togithub.com/moh-osman3) in [https://github.com/open-telemetry/otel-arrow/pull/164](https://togithub.com/open-telemetry/otel-arrow/pull/164) **Full Changelog**: https://github.com/open-telemetry/otel-arrow/compare/v0.19.0...v0.20.0 ### [`v0.19.0`](https://togithub.com/open-telemetry/otel-arrow/releases/tag/v0.19.0) [Compare Source](https://togithub.com/open-telemetry/otel-arrow/compare/v0.18.0...v0.19.0) See [CHANGELOG.md](https://togithub.com/open-telemetry/otel-arrow/blob/main/CHANGELOG.md#0190---2024-03-26) for release notes. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> commit 344990300ec413e990cdf406525523130c2ece46 Author: Stefan Kurek <stefan.kurek@observiq.com> Date: Wed May 8 12:57:11 2024 -0400 [receiver/vcenter] Adds New Packet Dropped Rate Metric for VMs (#32930) **Description:** <Describe what has changed.> Adds new default disabled (with Warning log for default enabled on next release) metric `vcenter.vm.network.packet.drop.rate` for Virtual Machines. This metric makes use of the `droppedRx` and `droppedTx` Network performance metrics detailed [here](https://vdc-repo.vmware.com/vmwb-repository/dcr-public/d1902b0e-d479-46bf-8ac9-cee0e31e8ec0/07ce8dbd-db48-4261-9b8f-c6d3ad8ba472/network_counters.html) for Virtual machines. This would use the same metric attributes as the other VM packet metrics and closely match `vcenter.vm.network.packet.rate` in every other way. **Link to tracking Issue:** <Issue number if applicable> #32929 **Testing:** <Describe what testing was performed and which tests were added.> Unit/integration tests updated and tested. Local environment tested. **Documentation:** <Describe the documentation added.> New documentation generated based on the metadata. commit 89d09e0ba97df2eca607d017741113a292f916bd Author: Stefan Kurek <stefan.kurek@observiq.com> Date: Wed May 8 12:42:09 2024 -0400 [receiver/vcenter] Fixes Cluster Resource Attributes for Datastore Resource (#32687) **Description:** <Describe what has changed.> Removed the `vcenter.cluster.name` resource attribute from all Datastore resources. **Link to tracking Issue:** <Issue number if applicable> #32674 **Testing:** <Describe what testing was performed and which tests were added.> Unit/integration tests updated and tested. Local environment tested. **Documentation:** <Describe the documentation added.> New documentation generated based on the metadata. --------- Co-authored-by: Daniel Jaglowski <jaglows3@gmail.com> Co-authored-by: Curtis Robert <crobert@splunk.com> commit 3e868a41264da17cba9a7123709b90b3effe19d3 Author: James Hughes (Splunk) <jameshughes@splunk.com> Date: Wed May 8 09:35:40 2024 -0700 [chore] Add some docs to readme regarding file exporter (#32855) Admittedly I tested this via docker-compose. I can expand to having a full docker-compose file with telemetry gen if that's preferred. --------- Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com> commit 097c74557b4d1f5569397ea5204549e8953af043 Author: Curtis Robert <crobert@splunk.com> Date: Wed May 8 09:32:00 2024 -0700 [receiver/googlecloudpubsubreceiver] Fix memory leak during shutdown (#32361) **Description:** <Describe what has changed.>  This PR contains the following changes: 1. Add `Close` call to the receiver's GRPC client. Without this, goroutines were being leaked on shutdown. 2. Change `grpc.Dial` -> `grpc.NewClient`. They offer the same functionality, but `Dial` is being deprecated in favor of `NewClient`. 3. Enable `goleak` checks on this receiver to help ensure no goroutines are being leaked. 4. Change a couple `Assert.Nil` calls to `Assert.NoError`. The output of `NoError` includes the error message if hit, `Nil` simply includes the object's address, i.e. `&status.Error{s:(*status.Status)(0xc00007e158)}` **Link to tracking Issue:** <Issue number if applicable> #30438 **Testing:** <Describe what testing was performed and which tests were added.> All existing tests are passing, as well as added goleak check. commit bbcbe3cfbfee86d36b79e7c80a0f1d7e8acfbb66 Author: Anthony Mirabella <a9@aneurysm9.com> Date: Wed May 8 11:58:37 2024 -0400 Move Aneurysm9 to emeritus status (#32943) I have been unable to provide this position the bandwidth that it deserves and it is time to formalize recognition of that fact. Signed-off-by: Anthony J Mirabella <a9@aneurysm9.com> commit 0e2f434de88ca8ae1a9b1969c61ff4bfecde03b7 Author: Lauri Tirkkonen <101785056+lauri-paypay@users.noreply.github.com> Date: Wed May 8 18:13:49 2024 +0300 [exporter/loadbalancing] Improve the performance when merging traces belonging to the same backend (#32032) **Description:** no need to reimplement that in an extremely allocation-inefficient fashion. I'm actually not sure why mergeTraces() and mergeMetrics() need to exist in the first place; all the other exporters coupled with the batch processor work just fine, not sure why loadbalancing would be special. https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/30141 seems to imply they were implemented to improve performance, but I don't really understand why batch processor would not have been sufficient for that improvement originally. benchmarks before: ``` goos: darwin goarch: arm64 pkg: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter BenchmarkMergeTraces_X100-8 50214 23507 ns/op BenchmarkMergeTraces_X500-8 10000 113952 ns/op BenchmarkMergeTraces_X1000-8 5208 226062 ns/op BenchmarkMergeMetrics_X100-8 64933 18540 ns/op BenchmarkMergeMetrics_X500-8 12885 91418 ns/op BenchmarkMergeMetrics_X1000-8 6590 184584 ns/op PASS ok github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter 9.783s ``` and after: ``` goos: darwin goarch: arm64 pkg: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter BenchmarkMergeTraces_X100-8 295886529 3.836 ns/op BenchmarkMergeTraces_X500-8 309865370 3.833 ns/op BenchmarkMergeTraces_X1000-8 310739948 3.800 ns/op BenchmarkMergeMetrics_X100-8 315567813 3.841 ns/op BenchmarkMergeMetrics_X500-8 310341650 3.849 ns/op BenchmarkMergeMetrics_X1000-8 314292003 3.830 ns/op PASS ok github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter 10.733s ``` **Link to tracking Issue:** n/a **Testing:** unit tests pass & cpu time for our collectors using loadbalancingexporter (12 replicas, total of 25k-40k spans/sec) went from 800ms-1400ms/sec down to <40msec/sec. **Documentation:** none --------- Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de> commit f617c655708938b3a8f245143c8926e2acf07812 Author: Juraci Paixão Kröhling <juraci@kroehling.de> Date: Wed May 8 16:17:38 2024 +0200 [connector/servicegraph] Remove use of host.GetExporters (#32902) Fixes #31628 Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de> --------- Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de> Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com> commit ba9ef9e02a79783fbf8ad66ce292df5da5393850 Author: Juraci Paixão Kröhling <juraci@kroehling.de> Date: Wed May 8 16:05:19 2024 +0200 [receiver/haproxy] Unit test timing out (#32940) I wasn't able to reproduce the exact situation from CI, but the tests I changed weren't completing at all here. Looking closely, it looks like they never closed the stream, something the first test does. After closing it, the tests start passing locally for me. While I'm not confident this will fix the CI flaky failures, this does make the test work locally for me. Fixes #32877 Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de> Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de> Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com> commit f1f2a85bfe750c04569d11189288895957331adb Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Wed May 8 06:45:54 2024 -0700 chore(deps): update dependency go to v1.22.3 (#32621) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [go](https://go.dev/) ([source](https://togithub.com/golang/go)) | toolchain | minor | `1.21.9` -> `1.22.3` | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>golang/go (go)</summary> ### [`v1.22.3`](https://togithub.com/golang/go/compare/go1.22.2...go1.22.3) ### [`v1.22.2`](https://togithub.com/golang/go/compare/go1.22.1...go1.22.2) ### [`v1.22.1`](https://togithub.com/golang/go/compare/go1.22.0...go1.22.1) ### [`v1.22.0`](https://togithub.com/golang/go/compare/go1.21.7...go1.22rc1) ### [`v1.21.10`](https://togithub.com/golang/go/compare/go1.21.9...go1.21.10) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Signed-off-by: Juraci Paixão Kröhling <juraci@kroehling.de> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Juraci Paixão Kröhling <juraci@kroehling.de> commit 66ce83d8442a2274cd17d53704368a4a56968a60 Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Wed May 8 06:37:58 2024 -0700 Update module github.com/grafana/loki/pkg/push to v0.0.0-20240507085123-772616cd8f5c (#32897) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/grafana/loki/pkg/push](https://togithub.com/grafana/loki) | `v0.0.0-20240506154431-a772ed705c65` -> `v0.0.0-20240507085123-772616cd8f5c` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fgrafana%2floki%2fpkg%2fpush/v0.0.0-20240507085123-772616cd8f5c?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fgrafana%2floki%2fpkg%2fpush/v0.0.0-20240507085123-772616cd8f5c?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fgrafana%2floki%2fpkg%2fpush/v0.0.0-20240506154431-a772ed705c65/v0.0.0-20240507085123-772616cd8f5c?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fgrafana%2floki%2fpkg%2fpush/v0.0.0-20240506154431-a772ed705c65/v0.0.0-20240507085123-772616cd8f5c?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> commit 353c7afa65c194994dfdf0629c7e07180d7029ae Author: Curtis Robert <crobert@splunk.com> Date: Wed May 8 06:32:31 2024 -0700 [chore][receiver/sqlserver] Update documentation for darwin and linux OS (#32878) **Description:** <Describe what has changed.>  With the enhancement in https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/30297, the SQL Server receiver can now run on MacOS and Linux, since it no longer solely relies on Windows. The difference in functionality has (hopefully) been documented clearly between the different platforms, so the unsupported warning can be removed. I missed this in my previous PRs. commit 7a248f5cc8303e1854f4bbc5be3db4869edd7f7f Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Wed May 8 12:45:51 2024 +0200 Update module github.com/aws/aws-sdk-go to v1.52.4 (#32928) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/aws/aws-sdk-go](https://togithub.com/aws/aws-sdk-go) | `v1.52.3` -> `v1.52.4` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2faws%2faws-sdk-go/v1.52.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2faws%2faws-sdk-go/v1.52.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2faws%2faws-sdk-go/v1.52.3/v1.52.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2faws%2faws-sdk-go/v1.52.3/v1.52.4?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>aws/aws-sdk-go (github.com/aws/aws-sdk-go)</summary> ### [`v1.52.4`](https://togithub.com/aws/aws-sdk-go/blob/HEAD/CHANGELOG.md#Release-v1524-2024-05-07) [Compare Source](https://togithub.com/aws/aws-sdk-go/compare/v1.52.3...v1.52.4) \=== ##### Service Client Updates - `service/b2bi`: Updates service documentation - `service/budgets`: Updates service API and documentation - This release adds tag support for budgets and budget actions. - `service/resiliencehub`: Updates service API, documentation, and paginators - `service/route53profiles`: Updates service API and documentation </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> commit 061b8eab3862fae67143d4f7a58ef4c73b164345 Author: Dominik Rosiek <58699848+sumo-drosiek@users.noreply.github.com> Date: Wed May 8 11:41:28 2024 +0200 sumologicexporter!: change metrics behavior (#32737) **Description:** <Describe what has changed.>  * 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 format This PR reduces size of #32315 **Link to tracking Issue:** #31479 **Testing:** - unit tests - manual tests **Documentation:** - Readme --------- Signed-off-by: Dominik Rosiek <drosiek@sumologic.com> Co-authored-by: Adam Boguszewski <aboguszewski@sumologic.com> commit 11396751f11905fe62df105f444cef9ab531def0 Author: David Ashpole <dashpole@google.com> Date: Wed May 8 04:36:53 2024 -0400 chore: add constants for prometheus translation (#32830) **Description:** This is a cleanup to consolidate the constants used for prometheus translation in a single place. --------- Co-authored-by: Curtis Robert <crobert@splunk.com> commit 984a1855a796c694c5b5b4ab0e8059f17d91eaee Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Wed May 8 10:29:34 2024 +0200 Update module google.golang.org/api to v0.178.0 (#32927) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [google.golang.org/api](https://togithub.com/googleapis/google-api-go-client) | `v0.177.0` -> `v0.178.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/google.golang.org%2fapi/v0.178.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/google.golang.org%2fapi/v0.178.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/google.golang.org%2fapi/v0.177.0/v0.178.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/google.golang.org%2fapi/v0.177.0/v0.178.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>googleapis/google-api-go-client (google.golang.org/api)</summary> ### [`v0.178.0`](https://togithub.com/googleapis/google-api-go-client/releases/tag/v0.178.0) [Compare Source](https://togithub.com/googleapis/google-api-go-client/compare/v0.177.0...v0.178.0) ##### Features - **all:** Auto-regenerate discovery clients ([#2561](https://togithub.com/googleapis/google-api-go-client/issues/2561)) ([2d22d11](https://togithub.com/googleapis/google-api-go-client/commit/2d22d11df9643a4fad0f9e952d7a92a419370122)) - **all:** Auto-regenerate discovery clients ([#2564](https://togithub.com/googleapis/google-api-go-client/issues/2564)) ([b313e4b](https://togithub.com/googleapis/google-api-go-client/commit/b313e4bd70e601fd7a2a931f168fb1dece980e75)) - **all:** Auto-regenerate discovery clients ([#2565](https://togithub.com/googleapis/google-api-go-client/issues/2565)) ([0843d21](https://togithub.com/googleapis/google-api-go-client/commit/0843d217048b2e713c0d273b95b33afb99926a8c)) - **all:** Auto-regenerate discovery clients ([#2567](https://togithub.com/googleapis/google-api-go-client/issues/2567)) ([76b27f1](https://togithub.com/googleapis/google-api-go-client/commit/76b27f162032649ddb3cb3f06ed24c7333b3fa66)) - **all:** Auto-regenerate discovery clients ([#2568](https://togithub.com/googleapis/google-api-go-client/issues/2568)) ([d922e3b](https://togithub.com/googleapis/google-api-go-client/commit/d922e3b559ce5832941390b4f9bf91210e3f6579)) - **all:** Auto-regenerate discovery clients ([#2570](https://togithub.com/googleapis/google-api-go-client/issues/2570)) ([f2da582](https://togithub.com/googleapis/google-api-go-client/commit/f2da582c9f6aab240d44c8ebd2dcc43f5096f896)) - **all:** Auto-regenerate discovery clients ([#2571](https://togithub.com/googleapis/google-api-go-client/issues/2571)) ([0c976dc](https://togithub.com/googleapis/google-api-go-client/commit/0c976dcc8d1d653f2284ce273493e6714a6d4b2a)) - **gen:** Add internaloption.EnableNewAuthLibrary ([#2519](https://togithub.com/googleapis/google-api-go-client/issues/2519)) ([8c74bb8](https://togithub.com/googleapis/google-api-go-client/commit/8c74bb83e2bc27188154c506e63a3e0f3a042f55)) - **google-api-go-client:** Add x-goog-api-version header ([#2563](https://togithub.com/googleapis/google-api-go-client/issues/2563)) ([fe54ffd](https://togithub.com/googleapis/google-api-go-client/commit/fe54ffd92359506fca1ffd70dc647db0ab9a903c)) ##### Documentation - Update commit style in CONTRIBUTING ([#2566](https://togithub.com/googleapis/google-api-go-client/issues/2566)) ([5e44215](https://togithub.com/googleapis/google-api-go-client/commit/5e44215df618fcafd5f6c1bbe259062cddd32f1a)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> commit 03ebf971a8d0cd88a47e82c1093ee488d477df1f Author: acha1os <dimi.theod@hotmail.com> Date: Wed May 8 10:54:01 2024 +0300 [exporter/syslogexporter] use errors.Join instead of go.uber.org/multierr (#32925) **Description:** syslogexporter: use errors.Join instead of go.uber.org/multierr **Link to tracking Issue:** [#25121](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/25121) **Testing:** **Documentation:** commit 8c6760fe60c0054ec6e87f1b784be518dcdf7ebb Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Tue May 7 12:04:23 2024 -0700 Update module github.com/jaegertracing/jaeger to v1.57.0 (#32908) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/jaegertracing/jaeger](https://togithub.com/jaegertracing/jaeger) | `v1.56.0` -> `v1.57.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fjaegertracing%2fjaeger/v1.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fjaegertracing%2fjaeger/v1.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fjaegertracing%2fjaeger/v1.56.0/v1.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fjaegertracing%2fjaeger/v1.56.0/v1.57.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>jaegertracing/jaeger (github.com/jaegertracing/jaeger)</summary> ### [`v1.57.0`](https://togithub.com/jaegertracing/jaeger/releases/tag/v1.57.0) [Compare Source](https://togithub.com/jaegertracing/jaeger/compare/v1.56.0...v1.57.0) ##### Backend Changes ##### 🐞 Bug fixes, Minor Improvements - \[jaeger-v2] define an internal interface of storage v2 spanstore ([@james-ryans](https://togithub.com/james-ryans) in [#5399](https://togithub.com/jaegertracing/jaeger/pull/5399)) - Combine jaeger ui release notes with jaeger backend ([@albertteoh](https://togithub.com/albertteoh) in [#5405](https://togithub.com/jaegertracing/jaeger/pull/5405)) - \[agent] use grpc.newclient ([@yurishkuro](https://togithub.com/yurishkuro) in [#5392](https://togithub.com/jaegertracing/jaeger/pull/5392)) - \[sampling] fix merging of per-operation strategies into service strategies without them ([@kuujis](https://togithub.com/kuujis) in [#5277](https://togithub.com/jaegertracing/jaeger/pull/5277)) - Create sampling templates when creating sampling store ([@JaeguKim](https://togithub.com/JaeguKim) in [#5349](https://togithub.com/jaegertracing/jaeger/pull/5349)) - \[kafka-consumer] set the rackid in consumer config ([@sappusaketh](https://togithub.com/sappusaketh) in [#5374](https://togithub.com/jaegertracing/jaeger/pull/5374)) - Adding best practices badge to readme.md ([@jkowall](https://togithub.com/jkowall) in [#5369](https://togithub.com/jaegertracing/jaeger/pull/5369)) ##### 👷 CI Improvements - Moving global write permissions down into the ci jobs ([@jkowall](https://togithub.com/jkowall) in [#5370](https://togithub.com/jaegertracing/jaeger/pull/5370)) ##### 📊 UI Changes ##### 🐞 Bug fixes, Minor Improvements - Improve trace page title with data and unique emoji (fixes [#2256](https://togithub.com/jaegertracing/jaeger/issues/2256)) ([@nox](https://togithub.com/nox) in [#2275](https://togithub.com/jaegertracing/jaeger-ui/pull/2275)) - Require node version 20+ ([@Baalekshan](https://togithub.com/Baalekshan) in [#2274](https://togithub.com/jaegertracing/jaeger-ui/pull/2274)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <107717825+opentelemetrybot@users.noreply.github.com> Co-authored-by: Pablo Baeyens <pbaeyens31+github@gmail.com> commit 34cd3f8b0dece8fe6f50e21a7eedbc0be79f2d71 Author: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Date: Tue May 7 12:03:59 2024 -0700 Update module github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen to v0.100.0 (#32912) [![Mend Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen](https://togithub.com/open-telemetry/opentelemetry-collector-contrib) | `v0.99.0` -> `v0.100.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.100.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.100.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.99.0/v0.100.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.99.0/v0.100.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector-contrib (github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen)</summary> ### [`v0.100.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01000) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.99.0...v0.100.0) ##### 🛑 Breaking changes 🛑 - `receiver/hostmetrics`: enable feature gate `receiver.hostmetrics.normalizeProcessCPUUtilization` ([#31368](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31368)) This changes the value of the metric `process.cpu.utilization` by dividing it by the number of CPU cores. For example, if a process is using 2 CPU cores on a 16-core machine, the value of this metric was previously `2`, but now it will be `0.125`. - `testbed`: Remove deprecated `GetAvailablePort` function ([#32800](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32800)) ##### 🚀 New components 🚀 - `healthcheckv2extension`: Introduce the skeleton for the temporary healthcheckv2 extension. ([#26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661)) - `intervalprocessor`: Implements the new interval processor. See the README for more info about how to use it ([#29461](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29461)) - `OpenTelemetry Protocol with Apache Arrow Receiver`: Implementation copied from opentelemetry/otel-arrow repository [@v0](https://togithub.com/v0).20.0. ([#26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491)) - `roundrobinconnector`: Add a roundrobin connector, that can help single thread components to scale ([#32853](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32853)) ##### 💡 Enhancements 💡 - `telemetrygen`: Add support to set metric name ([#32840](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32840)) - `exporter/kafkaexporter`: Enable setting message topics using resource attributes. ([#31178](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31178)) - `exporter/datadog`: Introduces the Datadog Agent logs pipeline for exporting logs to Datadog under the "exporter.datadogexporter.UseLogsAgentExporter" feature gate. ([#32327](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32327)) - `elasticsearchexporter`: Add retry.retry_on_status config ([#32584](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32584)) 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. - `exporter/splunkhec`: add experimental exporter batcher config ([#32545](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32545)) - `windowsperfcountersreceiver`: Returns partial errors for failures during scraping to prevent throwing out all successfully retrieved metrics ([#16712](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/16712)) - `jaegerencodingextension`: Promote jaegerencodingextension to alpha ([#32699](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32699)) - `kafkaexporter`: add an ability to publish kafka messages with message key based on metric resource attributes - it will allow partitioning metrics in Kafka. ([#29433](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29433), [#30666](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30666), [#31675](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31675)) - `cmd/opampsupervisor`: Switch the OpAMP Supervisor's bootstrap config to use the nopreceiver and nopexporter ([#32455](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32455)) - `otlpencodingextension`: Move otlpencodingextension to alpha ([#32701](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32701)) - `prometheusreceiver`: Prometheus receivers and exporters now preserve 'unknown', 'info', and 'stateset' types. ([#16768](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/16768)) It uses the metric.metadata field with the 'prometheus.type' key to store the original type. - `ptracetest`: Add support for ignore scope span instrumentation scope information ([#32852](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32852)) - `sqlserverreceiver`: Enable direct connection to SQL Server ([#30297](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30297)) Directly connecting to SQL Server will enable the receiver to gather more metrics for observing the SQL Server instance. The first metric added with this update is `sqlserver.database.io.read_latency`. - `connector/datadog`: The Datadog connector now has a config option to identify top-level spans by span kind. This new logic can be enabled by setting `traces::compute_top_level_by_span_kind` to true in the Datadog connector config. Default is false. ([#32005](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32005)) `traces::compute_top_level_by_span_kind` needs to be enabled in both the Datadog connector and Datadog exporter configs if both components are being used. With this new logic, root spans and spans with a server or consumer `span.kind` will be marked as top-level. Additionally, spans with a client or producer `span.kind` will have stats computed. Enabling this config option may increase the number of spans that generate trace metrics, and may change which spans appear as top-level in Datadog. - `exporter/datadog`: The Datadog exporter now has a config option to identify top-level spans by span kind. This new logic can be enabled by setting `traces::compute_top_level_by_span_kind` to true in the Datadog exporter config. Default is false. ([#32005](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32005)) `traces::compute_top_level_by_span_kind` needs to be enabled in both the Datadog connector and Datadog exporter configs if both components are being used. With this new logic, root spans and spans with a server or consumer `span.kind` will be marked as top-level. Additionally, spans with a client or producer `span.kind` will have stats computed. Enabling this config option may increase the number of spans that generate trace metrics, and may change which spans appear as top-level in Datadog. - `exporter/datadog`: Support stable semantic conventions for HTTP spans ([#32823](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32823)) - `cmd/opampsupervisor`: Persist collector remote config & telemetry settings ([#21078](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/21078)) - `cmd/opampsupervisor`: Support AcceptsRestartCommand Capability. ([#21077](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/21077)) - `telemetrygen`: Add headers to gRPC metadata for logs ([#32668](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32668)) - `sshcheckreceiver`: Add support for running this receiver on Windows ([#30650](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30650)) - `zipkinencodingextension`: Move zipkinencodingextension to alpha ([#32702](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32702)) ##### 🧰 Bug fixes 🧰 - `prometheusremotewrite`: Modify prometheusremotewrite.FromMetrics to only generate target_info if there are metrics, as otherwise you can't deduce the timestamp. ([#32318](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32318)) - `prometheusremotewrite`: 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. ([#32148](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32148)) - `k8sclusterreceiver`: Fix container state metadata ([#32676](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32676)) - `sumologicexporter`: do not replace `.` with `_` for prometheus format ([#31479](https://togithub.com/open-telemetry/opentelemetry-collector-con…

vcenterreceiver adds VM packets drop rate metric

0debbc6

StefanKurek requested review from djaglowski and a team as code owners May 7, 2024 20:04

github-actions bot assigned evan-bradley May 7, 2024

github-actions bot added the receiver/vcenter label May 7, 2024

github-actions bot requested a review from schmikei May 7, 2024 20:06

djaglowski reviewed May 8, 2024

View reviewed changes

receiver/vcenterreceiver/metadata.yaml Show resolved Hide resolved

djaglowski approved these changes May 8, 2024

View reviewed changes

djaglowski merged commit 3449903 into open-telemetry:main May 8, 2024
163 checks passed

github-actions bot added this to the next release milestone May 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[receiver/vcenter] Adds New Packet Dropped Rate Metric for VMs #32930

[receiver/vcenter] Adds New Packet Dropped Rate Metric for VMs #32930

StefanKurek commented May 7, 2024

[receiver/vcenter] Adds New Packet Dropped Rate Metric for VMs #32930

[receiver/vcenter] Adds New Packet Dropped Rate Metric for VMs #32930

Conversation

StefanKurek commented May 7, 2024