From 412f3655eebb3f2c6f4a03d7597d1edf0bd56c06 Mon Sep 17 00:00:00 2001 From: Carson Long Date: Tue, 7 Nov 2023 16:29:05 -0600 Subject: [PATCH] Update content/en/blog/2023/cloud-foundry.md Co-authored-by: Severin Neumann --- content/en/blog/2023/cloud-foundry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/2023/cloud-foundry.md b/content/en/blog/2023/cloud-foundry.md index d03585f67c67..921cdaa2b405 100644 --- a/content/en/blog/2023/cloud-foundry.md +++ b/content/en/blog/2023/cloud-foundry.md @@ -92,7 +92,7 @@ with many of those lines simply closing curly brackets. In writing this code we had to think about how to take our existing data model and translate it into the OpenTelemetry protobuf data model. We found OpenTelemetry to have considered many edge cases we had encountered in the past, and plenty we had not yet -encountered. Someday we hope to understand how to use Scopes and Resources +encountered. Someday we hope to understand how to use [Scopes](/docs/concepts/instrumentation-scope/) and [Resources](/docs/concepts/resources/) effectively. Our implementation worked well, though we found the OpenTelemetry Collector to