From 75b86eeb5a11bc2eeecbf7408848b221e0d70c0b Mon Sep 17 00:00:00 2001 From: Michal Skalski Date: Wed, 4 Dec 2024 20:06:15 +0900 Subject: [PATCH] [chore]: Mention the possibility of having multiple instances of loadbalancingexporter (#35489) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adding explicit statement about using multiple instances of `loadbalancingexporter` can help clarify deployment architecture. Reference: https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/22801 **Description:** **Link to tracking Issue:** **Testing:** **Documentation:** --------- Co-authored-by: Juraci Paixão Kröhling Co-authored-by: Juraci Paixão Kröhling --- exporter/loadbalancingexporter/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/exporter/loadbalancingexporter/README.md b/exporter/loadbalancingexporter/README.md index eecaa3e389fd..5df7812fb204 100644 --- a/exporter/loadbalancingexporter/README.md +++ b/exporter/loadbalancingexporter/README.md @@ -78,6 +78,8 @@ The `loadbalancingexporter` will, irrespective of the chosen resolver (`static`, Unfortunately, data loss is still possible if all of the exporter's targets remains unavailable once redelivery is exhausted. Due consideration needs to be given to the exporter queue and retry configuration when running in a highly elastic environment. +To avoid a single point of failure, requests can be distributed among multiple Collector instances configured with the `loadbalancingexporter`. The consistent hashing mechanism will ensure a deterministic result between instances sharing the same configuration and resolve an exact list of backend endpoints. + ## Configuration Refer to [config.yaml](./testdata/config.yaml) for detailed examples on using the exporter.