Blog post: OTel Sucks (But Also Rocks!) #6589
Conversation
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
|
|
||
| In preparation for the KubeCon talk "[OTel Sucks (But Also Rocks!)](https://sched.co/1txHm)", Juraci spoke with community members and gathered a wealth of valuable insights. Due to time constraints, not all the material could be included in the presentation, so this is an attempt to do justice to the community's contributions. | ||
|
|
||
| ## Where OTel Falls Short |
There was a problem hiding this comment.
I know the post covers a talk, but I'd like to know what we're doing, as a project, to address the pains. All complex projects have great and less great parts, so that's hardly surprising. Can we enrich what came out of the talk with our own stance as a project?
There was a problem hiding this comment.
The talk didn't happen yet, so nothing came out of it yet :-) What I can say right now is that the points mentioned are known to us all and we addressed them (semconv stability) or are addressing them (other semconv stability, collector stablity).
There was a problem hiding this comment.
Do you think it'd be valuable to add a note on this somewhere? That we're on it?
There was a problem hiding this comment.
Not sure: I think I prefer a honest "we are listening" tone. There are times where we just need to listen, and I think this is one of them. Perhaps we could have a "OTel Rocks" next year, showing how we progressed on the topics brought this year?
There was a problem hiding this comment.
Not sure: I think I prefer a honest "we are listening" tone. There are times where we just need to listen, and I think this is one of them. Perhaps we could have a "OTel Rocks" next year, showing how we progressed on the topics brought this year?
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
jpkrohling
force-pushed
the
jpkrohling/blog-post-otel-rocks
branch
from
34fc8e2 to
02f2fde
Compare
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
There was a problem hiding this comment.
Minor copyedits suggested inline.
Would there be a way to structure the two main sections so that we could see, at a glance, what the main points are? Consider breaking them prose into subsection, or even just using some bold text on key terms, or using a bulleted list.
Here's an AI summary, maybe it can give you ideas on how to highlight the main points (I'm not saying to copy this summary):
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
|
I could add that summary, but I feel like we the whole blog post is already a relatively short summary. For comparison, here's the content that would be summarized:
Wouldn't that shorter summary make the whole blog post repetitive? |
Agreed, it would. I wasn't suggesting adding a summary, but restructuring or adding phrases in bold to the content that is already there so that, at a glace, a reader can get the main ideas being put forth. How does that sound? |
This blog post accompanies the KubeCon talk "OTel Sucks (But Also Rocks!)".
Signed-off-by: Juraci Paixão Kröhling [email protected]
Preview: https://deploy-preview-6589--opentelemetry.netlify.app/blog/2025/otel-rocks/