From 22f3b24ff00ea393733443940eb91e67c9144117 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Mon, 21 Oct 2024 18:28:18 -0400 Subject: [PATCH 01/15] Add Gateway deployment arch --- .../en/docs/collector/deployment/gateway.md | 22 +++++++++++++++++++ .../docs/collector/img/otel-gateway-arch.svg | 10 +++++++++ 2 files changed, 32 insertions(+) create mode 100644 content/en/docs/collector/img/otel-gateway-arch.svg diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway.md index 8ef00132d819..8ebd37ea4ccc 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway.md @@ -198,6 +198,28 @@ The load-balancing exporter emits metrics including that you can use for health and performance monitoring of the OTLP endpoint collector. +## Typical Gateway deployment architecture + +The following diagram shows a typical deployment architecture for a gateway +![gateway](../img/otel-gateway-arch.svg) + +There are a few limitations in running the OTel collector in gateway mode. + +- We can't use receivers that need to be unique per host instance. Using these + receivers in gateway mode will result in Duplicate data, especially if the + collector runs in multiple instances. Examples include, but are not limited + to: + + - [hostmetricsreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), + may result in dupicate host metrics. + - [filelogreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver), + may result in duplicate logs. + +- Using a `resourcedetection` processor in gateway mode is not recommended. This + processor is used to detect the resources of the host where the collector is + running. Use `resourcedetection` processor in the pipeline of Daemonset + collector deployment. + ## Tradeoffs Pros: diff --git a/content/en/docs/collector/img/otel-gateway-arch.svg b/content/en/docs/collector/img/otel-gateway-arch.svg new file mode 100644 index 000000000000..28b9ee0f9c68 --- /dev/null +++ b/content/en/docs/collector/img/otel-gateway-arch.svg @@ -0,0 +1,10 @@ + + + + + + + + LoadBalancerOTLPExporterOTLPReceiverhostmetricsreceiverhostmetricsreceiverOTLPExporterOTel Collector DaemonOTel Collector DaemonNode in Cluster BNode in Cluster BBackend AexporterOTLPReceiverOTel Collector Gateway instance 1OTLPReceiverBackend Bexporter Backend AexporterBackend Bexporter Backend ABackend BOTel Collector Gateway instance 2 \ No newline at end of file From fc6a8f1f00b0c8619b4cfa1a9415d9faa7b7749c Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Mon, 21 Oct 2024 21:08:18 -0400 Subject: [PATCH 02/15] add links --- content/en/docs/collector/deployment/gateway.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway.md index 8ebd37ea4ccc..479d8484d0c7 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway.md @@ -210,15 +210,17 @@ There are a few limitations in running the OTel collector in gateway mode. collector runs in multiple instances. Examples include, but are not limited to: - - [hostmetricsreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), - may result in dupicate host metrics. - - [filelogreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver), + - [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), + may result in duplicate host metrics. + - [`filelogreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver), may result in duplicate logs. -- Using a `resourcedetection` processor in gateway mode is not recommended. This - processor is used to detect the resources of the host where the collector is - running. Use `resourcedetection` processor in the pipeline of Daemonset - collector deployment. +- Using a + [`resourcedetection`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor) + processor in gateway mode is not recommended. This processor is used to detect + the resources of the host where the collector is running. Use + `resourcedetection` processor in the pipeline of Daemonset collector + deployment. ## Tradeoffs From 40b3820014065a26795b6c88f40669cf3dd43200 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 22 Oct 2024 13:31:18 -0400 Subject: [PATCH 03/15] Add to spell ignore --- content/en/docs/collector/deployment/gateway.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway.md index 479d8484d0c7..786cd450aa44 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway.md @@ -4,7 +4,7 @@ description: Why and how to send signals to a single OTLP end-point and from there to backends weight: 3 -cSpell:ignore: hostnames loadbalancer loadbalancing +cSpell:ignore: hostnames loadbalancer loadbalancing hostmetricsreceiver filelogreceiver resourcedetection --- The gateway collector deployment pattern consists of applications (or other From dc266da8a1deae7972d275bafa9784ef52a89f1c Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 22 Oct 2024 13:38:39 -0400 Subject: [PATCH 04/15] fix format --- content/en/docs/collector/deployment/gateway.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway.md index 786cd450aa44..695fcb529df6 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway.md @@ -4,7 +4,9 @@ description: Why and how to send signals to a single OTLP end-point and from there to backends weight: 3 -cSpell:ignore: hostnames loadbalancer loadbalancing hostmetricsreceiver filelogreceiver resourcedetection +cSpell:ignore: + hostnames loadbalancer loadbalancing hostmetricsreceiver filelogreceiver + resourcedetection --- The gateway collector deployment pattern consists of applications (or other From 858575de5f299bc7212fe19f8838f234780f7f76 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 22 Oct 2024 13:42:02 -0400 Subject: [PATCH 05/15] fix format + spell --- content/en/docs/collector/deployment/gateway.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway.md index 695fcb529df6..4ad8ff451bdf 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway.md @@ -4,9 +4,8 @@ description: Why and how to send signals to a single OTLP end-point and from there to backends weight: 3 -cSpell:ignore: - hostnames loadbalancer loadbalancing hostmetricsreceiver filelogreceiver - resourcedetection +# prettier-ignore +cSpell:ignore: filelogreceiver hostmetricsreceiver hostnames loadbalancer loadbalancing resourcedetection --- The gateway collector deployment pattern consists of applications (or other From 39a041b586121c27e344723fe2fd90aa4ca59275 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Thu, 24 Oct 2024 10:08:58 -0400 Subject: [PATCH 06/15] PR feedback - update description --- content/en/docs/collector/deployment/gateway.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway.md index 4ad8ff451bdf..59c2c9649a3d 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway.md @@ -206,10 +206,10 @@ The following diagram shows a typical deployment architecture for a gateway There are a few limitations in running the OTel collector in gateway mode. -- We can't use receivers that need to be unique per host instance. Using these - receivers in gateway mode will result in Duplicate data, especially if the - collector runs in multiple instances. Examples include, but are not limited - to: +- Few receivers need to be unique per host instance. Running multiple instances + of these receivers will result in Duplicate data. It is recommended not to use + them in the Gateway collector but only for the collector running in Daemonset + mode. Examples include, but are not limited to: - [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), may result in duplicate host metrics. From 272b013490972a938528792252e7f1d8ad13ce16 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Thu, 24 Oct 2024 12:40:20 -0400 Subject: [PATCH 07/15] PR feedback - create gateway --- .../docs/collector/deployment/{gateway.md => gateway/index.md} | 2 +- .../collector/{img => deployment/gateway}/otel-gateway-arch.svg | 0 2 files changed, 1 insertion(+), 1 deletion(-) rename content/en/docs/collector/deployment/{gateway.md => gateway/index.md} (99%) rename content/en/docs/collector/{img => deployment/gateway}/otel-gateway-arch.svg (100%) diff --git a/content/en/docs/collector/deployment/gateway.md b/content/en/docs/collector/deployment/gateway/index.md similarity index 99% rename from content/en/docs/collector/deployment/gateway.md rename to content/en/docs/collector/deployment/gateway/index.md index 59c2c9649a3d..dce2f2cc1e0d 100644 --- a/content/en/docs/collector/deployment/gateway.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -202,7 +202,7 @@ collector. ## Typical Gateway deployment architecture The following diagram shows a typical deployment architecture for a gateway -![gateway](../img/otel-gateway-arch.svg) +![gateway](otel-gateway-arch.svg) There are a few limitations in running the OTel collector in gateway mode. diff --git a/content/en/docs/collector/img/otel-gateway-arch.svg b/content/en/docs/collector/deployment/gateway/otel-gateway-arch.svg similarity index 100% rename from content/en/docs/collector/img/otel-gateway-arch.svg rename to content/en/docs/collector/deployment/gateway/otel-gateway-arch.svg From 5e7995395bffab60622659085ef363ee4f27eaae Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 29 Oct 2024 11:53:14 -0400 Subject: [PATCH 08/15] PR feedback --- .../collector/deployment/gateway/index.md | 22 ++++++++++++++----- 1 file changed, 17 insertions(+), 5 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index dce2f2cc1e0d..9ce1e356fd51 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -201,14 +201,26 @@ collector. ## Typical Gateway deployment architecture -The following diagram shows a typical deployment architecture for a gateway +A typical Gateway architecture involves running both Collector in Gateway mode +and Agent mode. + +The following diagram shows a typical deployment architecture for a gateway. +Here + +- We use Agent Collectors (running on each host, similar to kubernetes + daeomonsets) to collect telemetry from services running on the host and host + telemetry, such as host metrics and scrap logs. +- We use Gateway Collector to process OTLP data, such as filtering, sampling, + and exporting to backends etc. + ![gateway](otel-gateway-arch.svg) -There are a few limitations in running the OTel collector in gateway mode. +There are a few limitations in running the OpenTelmetry collector in gateway +mode. - Few receivers need to be unique per host instance. Running multiple instances - of these receivers will result in Duplicate data. It is recommended not to use - them in the Gateway collector but only for the collector running in Daemonset + of these receivers will result in duplicate data. It is recommended not to use + them in the Gateway Collector but only for the collector running in Daemonset mode. Examples include, but are not limited to: - [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), @@ -219,7 +231,7 @@ There are a few limitations in running the OTel collector in gateway mode. - Using a [`resourcedetection`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor) processor in gateway mode is not recommended. This processor is used to detect - the resources of the host where the collector is running. Use + the resources of the host where the Collector is running. Use `resourcedetection` processor in the pipeline of Daemonset collector deployment. From f85c48dac69af545f10d0644454396bdd40fadd6 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 29 Oct 2024 12:00:37 -0400 Subject: [PATCH 09/15] fix format + spell --- .../docs/collector/deployment/gateway/index.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index 9ce1e356fd51..2a48f32297bf 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -204,13 +204,13 @@ collector. A typical Gateway architecture involves running both Collector in Gateway mode and Agent mode. -The following diagram shows a typical deployment architecture for a gateway. -Here +The following diagram shows a typical deployment architecture for a gateway +deployment. Here -- We use Agent Collectors (running on each host, similar to kubernetes +- We use Agent Collectors (running on each host, similar to Kubernetes daeomonsets) to collect telemetry from services running on the host and host telemetry, such as host metrics and scrap logs. -- We use Gateway Collector to process OTLP data, such as filtering, sampling, +- We use Gateway Collectors to process OTLP data, such as filtering, sampling, and exporting to backends etc. ![gateway](otel-gateway-arch.svg) @@ -218,10 +218,11 @@ Here There are a few limitations in running the OpenTelmetry collector in gateway mode. -- Few receivers need to be unique per host instance. Running multiple instances - of these receivers will result in duplicate data. It is recommended not to use - them in the Gateway Collector but only for the collector running in Daemonset - mode. Examples include, but are not limited to: +- There are few receivers in OpenTelmetry Collector that need to be unique per + host instance. Running multiple instances of these receivers will result in + duplicate data. It is recommended not to use them in the Gateway Collector but + only for the collector running in Daemonset mode. Examples include, but are + not limited to: - [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), may result in duplicate host metrics. From d9ffa2b62166965ed6bc2e7b43938503f8a860b6 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 29 Oct 2024 12:02:56 -0400 Subject: [PATCH 10/15] remove daemonset --- content/en/docs/collector/deployment/gateway/index.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index 2a48f32297bf..62a5800675ee 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -221,8 +221,8 @@ mode. - There are few receivers in OpenTelmetry Collector that need to be unique per host instance. Running multiple instances of these receivers will result in duplicate data. It is recommended not to use them in the Gateway Collector but - only for the collector running in Daemonset mode. Examples include, but are - not limited to: + only for the collector running in Agent mode. Examples include, but are not + limited to: - [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), may result in duplicate host metrics. @@ -233,8 +233,7 @@ mode. [`resourcedetection`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor) processor in gateway mode is not recommended. This processor is used to detect the resources of the host where the Collector is running. Use - `resourcedetection` processor in the pipeline of Daemonset collector - deployment. + `resourcedetection` processor in the pipeline of Agent collector deployment. ## Tradeoffs From c0296a281f735f7b18a207fc9481e8e2f61bce0b Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 29 Oct 2024 12:09:03 -0400 Subject: [PATCH 11/15] fix spell --- content/en/docs/collector/deployment/gateway/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index 62a5800675ee..808db699a594 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -208,17 +208,17 @@ The following diagram shows a typical deployment architecture for a gateway deployment. Here - We use Agent Collectors (running on each host, similar to Kubernetes - daeomonsets) to collect telemetry from services running on the host and host + daemonsets) to collect telemetry from services running on the host and host telemetry, such as host metrics and scrap logs. - We use Gateway Collectors to process OTLP data, such as filtering, sampling, and exporting to backends etc. ![gateway](otel-gateway-arch.svg) -There are a few limitations in running the OpenTelmetry collector in gateway +There are a few limitations in running the OpenTelemetry collector in gateway mode. -- There are few receivers in OpenTelmetry Collector that need to be unique per +- There are few receivers in OpenTelemetry Collector that need to be unique per host instance. Running multiple instances of these receivers will result in duplicate data. It is recommended not to use them in the Gateway Collector but only for the collector running in Agent mode. Examples include, but are not From c4d8b997d537bb2017e085dc22165b3fd2a6d87a Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Tue, 29 Oct 2024 12:15:51 -0400 Subject: [PATCH 12/15] fix lint issues --- content/en/docs/collector/deployment/gateway/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index 808db699a594..9888933b6a90 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -215,7 +215,7 @@ deployment. Here ![gateway](otel-gateway-arch.svg) -There are a few limitations in running the OpenTelemetry collector in gateway +There are a few limitations in running the OpenTelemetry Collector in gateway mode. - There are few receivers in OpenTelemetry Collector that need to be unique per From 23795b2d2d8e19a0acca3a6763c4043d5f8f685b Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Mon, 4 Nov 2024 12:26:10 -0500 Subject: [PATCH 13/15] Apply suggestions from code review Co-authored-by: Severin Neumann --- .../en/docs/collector/deployment/gateway/index.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index 9888933b6a90..a2a231a0b60a 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -199,18 +199,16 @@ The load-balancing exporter emits metrics including that you can use for health and performance monitoring of the OTLP endpoint collector. -## Typical Gateway deployment architecture +## Combined deployment of Collectors as agents and gateways -A typical Gateway architecture involves running both Collector in Gateway mode -and Agent mode. +Often a deployment of multiple OpenTelemetry collectors involves running both Collector as gateways and as [agents](/docs/collector/deployment/agent/). -The following diagram shows a typical deployment architecture for a gateway -deployment. Here +The following diagram shows an architecture for such a combined deployment: -- We use Agent Collectors (running on each host, similar to Kubernetes +- We use the Collectors using the agent deployment pattern (running on each host, similar to Kubernetes daemonsets) to collect telemetry from services running on the host and host telemetry, such as host metrics and scrap logs. -- We use Gateway Collectors to process OTLP data, such as filtering, sampling, +- We use Collectors using the gateway deployment pattern to process data, such as filtering, sampling, and exporting to backends etc. ![gateway](otel-gateway-arch.svg) From 19141ff0c2d0d84638eaa0f16a232ee7410f2418 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Mon, 4 Nov 2024 12:50:26 -0500 Subject: [PATCH 14/15] PR feedback - update diagram --- .../collector/deployment/gateway/index.md | 48 +++++++++---------- .../deployment/gateway/otel-gateway-arch.svg | 4 +- 2 files changed, 25 insertions(+), 27 deletions(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index a2a231a0b60a..58aaf5f43acf 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -201,37 +201,35 @@ collector. ## Combined deployment of Collectors as agents and gateways -Often a deployment of multiple OpenTelemetry collectors involves running both Collector as gateways and as [agents](/docs/collector/deployment/agent/). +Often a deployment of multiple OpenTelemetry collectors involves running both +Collector as gateways and as [agents](/docs/collector/deployment/agent/). The following diagram shows an architecture for such a combined deployment: -- We use the Collectors using the agent deployment pattern (running on each host, similar to Kubernetes - daemonsets) to collect telemetry from services running on the host and host - telemetry, such as host metrics and scrap logs. -- We use Collectors using the gateway deployment pattern to process data, such as filtering, sampling, - and exporting to backends etc. +- We use the Collectors running in the agent deployment pattern (running on each + host, similar to Kubernetes daemonsets) to collect telemetry from services + running on the host and host telemetry, such as host metrics and scrap logs. +- We use Collectors running in the gateway deployment pattern to process data, + such as filtering, sampling, and exporting to backends etc. ![gateway](otel-gateway-arch.svg) -There are a few limitations in running the OpenTelemetry Collector in gateway -mode. - -- There are few receivers in OpenTelemetry Collector that need to be unique per - host instance. Running multiple instances of these receivers will result in - duplicate data. It is recommended not to use them in the Gateway Collector but - only for the collector running in Agent mode. Examples include, but are not - limited to: - - - [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver), - may result in duplicate host metrics. - - [`filelogreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver), - may result in duplicate logs. - -- Using a - [`resourcedetection`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor) - processor in gateway mode is not recommended. This processor is used to detect - the resources of the host where the Collector is running. Use - `resourcedetection` processor in the pipeline of Agent collector deployment. +This combined deployment pattern is necessary, when you use components in your +Collector that either need to be unique per host or that consume information +that is only available on the same host as the application is running: + +- Receivers like the + [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver) + or + [`filelogreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver) + need to be unique per host instance. Running multiple instances of these + receivers will result in duplicated data. + +- Processors like the + [`resourcedetectionprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor) + are used to add information about the host, the collector and the application + are running on. Running them within a Collector on a remote machine will + result in incorrect data. ## Tradeoffs diff --git a/content/en/docs/collector/deployment/gateway/otel-gateway-arch.svg b/content/en/docs/collector/deployment/gateway/otel-gateway-arch.svg index 28b9ee0f9c68..f2062bb879e6 100644 --- a/content/en/docs/collector/deployment/gateway/otel-gateway-arch.svg +++ b/content/en/docs/collector/deployment/gateway/otel-gateway-arch.svg @@ -3,8 +3,8 @@ - LoadBalancerOTLPExporterOTLPReceiverhostmetricsreceiverhostmetricsreceiverOTLPExporterOTel Collector DaemonOTel Collector DaemonNode in Cluster BNode in Cluster BBackend AexporterOTLPReceiverOTel Collector Gateway instance 1OTLPReceiverBackend Bexporter Backend AexporterBackend Bexporter Backend ABackend BOTel Collector Gateway instance 2 \ No newline at end of file + LoadBalancerOTLPExporterOTLPReceiverhostmetricsreceiverhostmetricsreceiverOTLPExporterOTel Collector DaemonOTel Collector DaemonGateway Node in Cluster BNode in Cluster BBackend AexporterOTLPReceiverOTel Collector Gateway instance 1OTLPReceiverBackend Bexporter Backend AexporterBackend Bexporter Backend ABackend BOTel Collector Gateway instance 2Service BService Aresourcedetectionprocessor \ No newline at end of file From 5f8f908835fa160d40c0d64e2b17873ff92d2933 Mon Sep 17 00:00:00 2001 From: Dinesh Gurumurthy Date: Mon, 4 Nov 2024 12:54:07 -0500 Subject: [PATCH 15/15] fix spell --- content/en/docs/collector/deployment/gateway/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/collector/deployment/gateway/index.md b/content/en/docs/collector/deployment/gateway/index.md index 58aaf5f43acf..6b3dae479b81 100644 --- a/content/en/docs/collector/deployment/gateway/index.md +++ b/content/en/docs/collector/deployment/gateway/index.md @@ -5,7 +5,7 @@ description: backends weight: 3 # prettier-ignore -cSpell:ignore: filelogreceiver hostmetricsreceiver hostnames loadbalancer loadbalancing resourcedetection +cSpell:ignore: filelogreceiver hostmetricsreceiver hostnames loadbalancer loadbalancing resourcedetectionprocessor --- The gateway collector deployment pattern consists of applications (or other