From 49800d1f3688533d71acbc2a012958ff0e68292e Mon Sep 17 00:00:00 2001 From: Elan Hasson <234704+ElanHasson@users.noreply.github.com> Date: Mon, 26 Aug 2024 05:24:03 -0400 Subject: [PATCH 1/3] Update README.md to fix typo (#34838) **Description:** Corrected typo. **Link to tracking Issue:** n/a **Testing:** n/a **Documentation:** Corrected a typo. --- processor/metricsgenerationprocessor/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/processor/metricsgenerationprocessor/README.md b/processor/metricsgenerationprocessor/README.md index 64e78f0d5215..3d81bcad46f7 100644 --- a/processor/metricsgenerationprocessor/README.md +++ b/processor/metricsgenerationprocessor/README.md @@ -18,7 +18,7 @@ The metrics generation processor (`experimental_metricsgenerationprocessor`) can be used to create new metrics using existing metrics following a given rule. Currently it supports following two approaches for creating a new metric. -1. It can create a new metric from two existing metrics by applying one of the folliwing arithmetic operations: add, subtract, multiply, divide and percent. One use case is to calculate the `pod.memory.utilization` metric like the following equation- +1. It can create a new metric from two existing metrics by applying one of the following arithmetic operations: add, subtract, multiply, divide and percent. One use case is to calculate the `pod.memory.utilization` metric like the following equation- `pod.memory.utilization` = (`pod.memory.usage.bytes` / `node.memory.limit`) 1. It can create a new metric by scaling the value of an existing metric with a given constant number. One use case is to convert `pod.memory.usage` metric values from Megabytes to Bytes (multiply the existing metric's value by 1,048,576) From 2d5b62d99b9940c2dde01e0c50016be46177e970 Mon Sep 17 00:00:00 2001 From: Felipe Lopes Date: Mon, 26 Aug 2024 07:13:10 -0300 Subject: [PATCH 2/3] [chore][receiver/datadog] Fix data race detected in tests (#34834) **Description:** Fixes #34823 **Link to tracking Issue:** **Testing:** **Documentation:** --- receiver/datadogreceiver/receiver_test.go | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/receiver/datadogreceiver/receiver_test.go b/receiver/datadogreceiver/receiver_test.go index 573e271ba8fa..c671abdf48ff 100644 --- a/receiver/datadogreceiver/receiver_test.go +++ b/receiver/datadogreceiver/receiver_test.go @@ -115,9 +115,6 @@ func TestDatadogServer(t *testing.T) { } func TestDatadogInfoEndpoint(t *testing.T) { - cfg := createDefaultConfig().(*Config) - cfg.Endpoint = "localhost:0" // Using a randomly assigned address - for _, tc := range []struct { name string tracesConsumer consumer.Traces @@ -214,6 +211,9 @@ func TestDatadogInfoEndpoint(t *testing.T) { t.Run(tc.name, func(t *testing.T) { t.Parallel() + cfg := createDefaultConfig().(*Config) + cfg.Endpoint = "localhost:0" // Using a randomly assigned address + dd, err := newDataDogReceiver( cfg, receivertest.NewNopSettings(), From 234eadd91ae4b83bf548972ff7237db90b1125f3 Mon Sep 17 00:00:00 2001 From: Jorge Creixell Date: Mon, 26 Aug 2024 16:58:00 +0200 Subject: [PATCH 3/3] Update README for grafanacloudconnector (#34845) **Description:** - The connector has enough contributors and no longer seeks new ones, so the metadata and README files have been updated accordingly Signed-off-by: Jorge Creixell --- connector/grafanacloudconnector/README.md | 2 +- connector/grafanacloudconnector/metadata.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/connector/grafanacloudconnector/README.md b/connector/grafanacloudconnector/README.md index 41c415c8d770..9d6d81983dfb 100644 --- a/connector/grafanacloudconnector/README.md +++ b/connector/grafanacloudconnector/README.md @@ -5,7 +5,7 @@ | ------------- |-----------| | Distributions | [contrib] | | Issues | [![Open issues](https://img.shields.io/github/issues-search/open-telemetry/opentelemetry-collector-contrib?query=is%3Aissue%20is%3Aopen%20label%3Aconnector%2Fgrafanacloud%20&label=open&color=orange&logo=opentelemetry)](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aopen+is%3Aissue+label%3Aconnector%2Fgrafanacloud) [![Closed issues](https://img.shields.io/github/issues-search/open-telemetry/opentelemetry-collector-contrib?query=is%3Aissue%20is%3Aclosed%20label%3Aconnector%2Fgrafanacloud%20&label=closed&color=blue&logo=opentelemetry)](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aclosed+is%3Aissue+label%3Aconnector%2Fgrafanacloud) | -| [Code Owners](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#becoming-a-code-owner) | [@jpkrohling](https://www.github.com/jpkrohling), [@rlankfo](https://www.github.com/rlankfo), [@jcreixell](https://www.github.com/jcreixell) \| Seeking more code owners! | +| [Code Owners](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#becoming-a-code-owner) | [@jpkrohling](https://www.github.com/jpkrohling), [@rlankfo](https://www.github.com/rlankfo), [@jcreixell](https://www.github.com/jcreixell) | [alpha]: https://github.com/open-telemetry/opentelemetry-collector#alpha [contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib diff --git a/connector/grafanacloudconnector/metadata.yaml b/connector/grafanacloudconnector/metadata.yaml index 5c16ba8f19d0..873309168138 100644 --- a/connector/grafanacloudconnector/metadata.yaml +++ b/connector/grafanacloudconnector/metadata.yaml @@ -8,7 +8,7 @@ status: codeowners: active: [jpkrohling, rlankfo, jcreixell] emeritus: [] - seeking_new: true + seeking_new: false tests: config: