Seneste nyt om open source
Blog on OpenTelemetryWe are delighted to announce the results of the 2026 OpenTelemetry Governance Committee Election! The OpenTelemetry project continues to bring together an exceptionally vibrant community, who are shaping the future of observability with their contributions. This year, active contributors have shown their commitment again by participating in our election process, and they’ve done it in great numbers. 836 contributors were eligible to vote this year, and 345 of them cast their ballot. With a participation rate of 41%, it is in line with last year’s participation rate, where 273 ballots were cast with 702 eligible voters. (39%)
29 October , 2026Blog on OpenTelemetryThere are many reasons for building your own OpenTelemetry Collector distribution. The existing distributions are designed to be broadly useful, which means they include many more components than what an individual deployment uses. Building your own gives you the ability to select only the components you care about, add your own custom components, and control exactly what ends up in the binary you run in production. One of the reasons I prefer to build my own distribution is to limit the size of the binary I have to ship around and to ensure that the least amount of dependencies are included. Fewer dependencies means a smaller binary, a smaller attack surface, and fewer third-party modules to track when a vulnerability is disclosed
29 October , 2026Blog on OpenTelemetryIf you run the File Log receiver with a storage extension, the Collector writes a checkpoint every time it polls your log files. That checkpoint is how the receiver remembers where it stopped reading, so a restart does not lose or duplicate logs. For years that checkpoint format was JSON. Starting with OpenTelemetry Collector Contrib v0.164.0, checkpoints are always written as protobuf. On our benchmarks, saving a checkpoint is almost 5 times faster, loading one is more than 5 times faster, and the checkpoint itself is about 35% smaller.
28 October , 2026Zabbix BlogThe Lebanese International University (LIU) conducts applied networking research aimed at making professional-grade monitoring practices accessible in academic settings through its Department of Computer and Communication Engineering. The department recently completed a research project that explored how Zabbix could be used to monitor a fully virtualized network environment, with the goal of offering a model that any academic or training lab could adopt. The challenge Networking education broadly relies on physical lab equipment (routers, switches) that is expensive to acquire, maintain, and scale, putting realistic, hands-on monitoring practice out of reach for many programs. The research set out to test whether a simulated network environment could be monitored exactly as one would monitor production infrastructure – collecting live metrics, visualizing device health, and practicing remote management, while operating on a budget appropriate for an academic lab. The solution The team built a virtual network topology in PNETLab (routers, switches, and end devices using multi-vendor images) and connected it to a Zabbix server running on a low-cost Raspberry Pi 5
28 October , 2026Blog on OpenTelemetryThe OpenTelemetry Transformation Language (OTTL) is now v1. Starting with opentelemetry-collector-contrib v0.164.0, OTTL is stable for traces, metrics, and logs. The release of v1 means OTTL meets the Collector’s ‘stable’ stability criteria for testing, benchmarking, documentation, and telemetry. It also comes with a compatibility promise for all of 1.x. If you write OTTL statements, the syntax and the standard functions stay backward compatible
27 October , 2026Linux Foundation - BlogOver the past three decades, open source communities have absorbed one massive technological shift after another: the emergence of the web, the mobile revolution, and the rise of cloud native infrastructure. Through each transition, our ecosystem adapted, strengthened its collaborative norms, and grew more resilient. Yet generative AI introduces a fundamentally distinct dynamic, directly affecting the heart of how project communities function.
26 October , 2026Blog on OpenTelemetryI believe OpenTelemetry’s primary constraint isn’t ideas, code contributions, or adoption, but maintainers. About me I’ve been working on OpenTelemetry since early 2021. I’m a maintainer of opentelemetry-java, opentelemetry-configuration, and opentelemetry-injector, and a member of the Technical Committee. In that time I’ve worked at two observability companies, New Relic and now Grafana Labs, in roles with a charter to work on OpenTelemetry while also engaging in internal engineering efforts that depend on it. This post is my opinion, informed by involvement in a lot of different OpenTelemetry projects and by watching various contributors come and go.
26 October , 2026Blog on OpenTelemetryDo you use OpenTelemetry’s registry or ecosystem lists? Comment on the issue and tell us which pages you need and why. We are reviewing the future of these pages. Understanding how people use them will help us focus our efforts within the maintainer time available. Which pages are affected? We have frozen new entries and updates to the following lists while we consider retiring or changing them: Registry: libraries, Collector components, and other tools for using and extending OpenTelemetry. Vendors: organizations offering solutions that consume OpenTelemetry
23 October , 2026Blog on OpenTelemetryOpenTelemetry has updated its client versioning policy to make room for security fixes that need to change behavior. Stable SDKs and Contrib components, such as instrumentation libraries and exporters, can now make narrowly scoped, necessary security changes in minor or patch releases, even when those changes affect existing users. Public API compatibility remains protected. The intent is to help users receive security improvements within the major version they already use. Some upgrades may require configuration or operational changes
22 October , 2026