fiper
Sign in

List

FinOps

Cloud costs, financial operations and practical FinOps coverage.

77 sources

Stories from Blog on OpenTelemetry. Show all stories · All sources

Latest stories

Newest first

  • Blog on OpenTelemetry Read

    The Humans of OpenTelemetry - KubeCon Japan 2026

    We’re back with our fifth edition of Humans of OpenTelemetry, and for the first time, from Japan! At KubeCon + CloudNativeCon Japan 2026 in Yokohama, I interviewed OpenTelemetry end users and practitioners from the Japanese cloud native community, and learned how they got involved with OTel: Yuzuru Ohira (LayerX) Mikata Chikahisa (Loglass) Yoshiki Fujikane (CyberAgent) Takashi Okamoto (NTT DATA) Kohei Sugimoto (MIXI) The interviews were conducted in Japanese, and the transcript below is an English translation.

  • Blog on OpenTelemetry Read

    Versioned metrics: Shipping the first Release Candidate metrics in hostmetrics

    OpenTelemetry Collector Contrib v0.160.0 adds the ability to emit release candidate (RC) process semantic conventions metrics to the hostmetrics receiver’s process scraper, the last stage before a stable v1. The System SIG has worked on this for the better part of a year, and we think that the process metrics are in a good shape – but RC exists so the community can prove that. If you collect process metrics, we’d like you to try the new versioned output and tell us what breaks.

  • Blog on OpenTelemetry Read

    OTel-Native by Design - Building Products That Export to Any Observability Stack

    With contributions from Dan Gomez Blanco (New Relic). If you’re building self-hosted software or a SaaS product, your users will eventually ask to send logs, traces, and metrics to their own observability stack, whether to satisfy compliance, manage costs, or centralize all their observability data in one place. Locking them into your built-in dashboards or limiting exports to certain vendors creates unnecessary friction.

  • Blog on OpenTelemetry Read

    OpenTelemetry Community Awards 2026

    We are delighted to announce the 3rd annual OpenTelemetry Community Awards this year! This project and its newly minted status as a graduated CNCF project would not be possible without many, many awesome humans who contribute their time, knowledge, and skills to further develop and improve the field of observability.

  • Blog on OpenTelemetry Read

    The OpenTelemetry Java agent 3.0 is almost here — preview it today

    The 2.32.0 release of the OpenTelemetry Java agent is now out and serves as the release candidate for 3.0, which is targeted for October 2026. Some behavior may still change before 3.0, but you can preview the new behavior now, before it becomes the default. 3.0 changes telemetry, configuration, and instrumentation defaults. Database and code conventions become stable defaults, messaging adopts newer conventions that are still experimental, and some capture settings and instrumentation defaults change. What to check covers each area.

  • Blog on OpenTelemetry Read

    Zero-code trace-log correlation with OBI

    You get paged. A trace shows a request failing in one of your services, and you know the answer is in the logs — but which log lines belong to that request? If the service never adopted structured logging with trace context, the honest answer is: you grep by timestamp and hope. OpenTelemetry eBPF Instrumentation (OBI) can now add that missing trace context to the logs your services already write. Your applications don’t change: no SDK, no logging-library configuration, no application rebuild or redeploy.

You have reached the end of this list.

Showing 6 of 6 articles

Know a source we’re missing? Tell us about it