From adcdf52b186c2eff1c7cd8dcc0c4e8a7fe12a8b5 Mon Sep 17 00:00:00 2001 From: Carson Long Date: Tue, 7 Nov 2023 14:36:19 -0800 Subject: [PATCH] Update content/en/blog/2023/cloud-foundry.md Co-authored-by: Severin Neumann --- content/en/blog/2023/cloud-foundry.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/blog/2023/cloud-foundry.md b/content/en/blog/2023/cloud-foundry.md index 921cdaa2b405..705016b7fbf9 100644 --- a/content/en/blog/2023/cloud-foundry.md +++ b/content/en/blog/2023/cloud-foundry.md @@ -64,9 +64,9 @@ Fluent Bit early because our ability to contribute to the codebase would be minimal, which we worried would limit us in the future. We then looked more seriously at Telegraf and OpenTelemetry. Both are written in -Go, so we were good there. Telegraf has a more limited community, and does not -offer a customizable build process. We liked that OpenTelemetry allows us to -build a Collector with a curated selection of our own components and community +Go, so we were good there. Our main reason to go with OpenTelemetry, was the +availability of a customizable build process: OpenTelemetry allows us to +[build a Collector](/docs/collector/custom-collector/) with a curated selection of our own components and community components. Additionally, when looking at OpenTelemetry we found that many [tools](/ecosystem/integrations/) and [vendors](/ecosystem/vendors/)