From 211f8b0e2b92e4c6d2ba2b9bb2ef23401a820039 Mon Sep 17 00:00:00 2001 From: Joshua Timmons Date: Tue, 26 Dec 2023 22:58:07 -0500 Subject: [PATCH] Add links to README --- README.md | 2 +- testdata/test.go | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3040ef4..05db8b3 100644 --- a/README.md +++ b/README.md @@ -9,7 +9,7 @@ Checks usage of [OpenTelemetry spans](https://pkg.go.dev/go.opentelemetry.io/ote ## Problem Statement -Tracing is one of the pillars of observability. But it's easy to shoot yourself in the foot when creating and managing OTEL spans. For two reasons: +Tracing is an -- often celebrated [[1](https://andydote.co.uk/2023/09/19/tracing-is-better/), [2](https://charity.wtf/2022/08/15/live-your-best-life-with-structured-events/)] -- pillar of observability. But it's easy to shoot yourself in the foot when creating and managing OTEL spans. For two reasons: ### Forgetting to call `span.End()` diff --git a/testdata/test.go b/testdata/test.go index 0942efa..cfcbd15 100644 --- a/testdata/test.go +++ b/testdata/test.go @@ -168,3 +168,7 @@ func _() { _, span = otel.Tracer("foo").Start(context.Background(), "bar") defer span.End() } + +func _() { + // TODO: https://andydote.co.uk/2023/09/19/tracing-is-better/ +}