Skip to content

Commit

Permalink
add otel challenges blog post from thenewstack
Browse files Browse the repository at this point in the history
  • Loading branch information
hazelweakly committed Oct 14, 2024
1 parent 607b34a commit 6c4ea29
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions src/blog/opentelemetry-challenges-handling-long-running-spans.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
title: "OpenTelemetry Challenges: Handling Long-Running Spans"
date: 2024-10-10
---

> Long running spans are one of my biggest "we don't really actually have a good standard solution for this" issues in opentelemetry.
> They're something I've run into before, weirdly frequently, and especially so when attempting to try and instrument front-end or mobile facing systems.
>
> It turns out, though, that the issues here with long running spans are actually pretty similar to the issues with interrupted, partial, or unclosed spans.
> In fact, they're really mostly the same thing (with the added bonus that if you do tail sampling your sampling decision is going to happen before the span ends, which exacerbates the problem by turning functioning spans into partial and broken ones)
>
> Anyway, I talk about this and more in this article and even point out a really cool solution from [Embrace](https://embrace.io) that addresses this in an opentelemetry compatible way
> (hint: does the phrase "write ahead log" make you quiver with excitement? If so, you should definitely read this)
<https://thenewstack.io/opentelemetry-challenges-handling-long-running-spans/>

0 comments on commit 6c4ea29

Please sign in to comment.