Create blog post announcing opentelemetry kotlin

[fractalwrench]

• I have read and followed the Contributing docs, especially the "First-time contributing?" section.
• This PR has content that I did not fully write myself.
  • I used AI and I have read and followed the Generative AI Contribution Policy.
• I have the experience and knowledge necessary to understand, review, and validate all content in this PR.¹

---

Provides a follow up post to the call for contributors on the OpenTelemetry Kotlin SDK. The donation process has now completed so the SIG like to inform folks that a Kotlin SDK exists, with the aim of gaining users & potential contributors to the SIG.

I will request review from the other maintainers/approvers of opentelemetry-kotlin to confirm they're happy with the content.

It would be great if this could be merged as close to March 23rd as possible, as Embrace/CNCF will be doing some additional marketing around that time. I've read the publication guidelines and understand that it might not be possible to hit the exact date.

PREVIEW: https://deploy-preview-9293--opentelemetry.netlify.app/blog/2026/kotlin-multiplatform-opentelemetry/

Footnotes

1. Yes, I can answer maintainer questions about the content of this PR, without using AI. ↩

[tiffany76]

LGTM with a couple small changes!

We've slotted you in for March 23. Thanks!

[tiffany76]

/fix:format

[otelbot-docs]

✅ fix:format applied successfully in run 22577594701.

[fractalwrench]

Could somebody with the necessary permissions remove the ready-to-be-merged label? Ideally we're aiming for around March 23rd on this one. Thanks!

[vitorvasc]

Could somebody with the necessary permissions remove the ready-to-be-merged label? Ideally we're aiming for around March 23rd on this one. Thanks!

I'll create a follow-up issue so the labels workflow handles PRs containing blog posts better. In the meantime, updates and new commits on this PR might re-add the ready-to-be-merged label.

[bidetofevil]

Looks good to me. In the future, we may want to discuss the relationship of this project with opentelemetry-android and opentelemetry-swift, and if someone had a KMP app right now and want to use OTel, what the trade offs are with going with this vs using the other two separately. But the scope of that probably deserves its own post rather than adding girth to this one.