🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 197 (from laksa144)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa197.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/\')), getAhrefsUnparsedNoserviceFromURL(\'https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/thenewstack.io\/how-to-make-opentelemetry-better-in-the-browser\/","crawl_time":1775640527,"first_indexed_time":1756987444,"http_code":200,"src_unparsed":"io,thenewstack!\/how-to-make-opentelemetry-better-in-the-browser\/ s443","src_root_hash":"5306194916123425997","history_drop_reason":null,"meta_title":"How to Make OpenTelemetry Better in the Browser - The New Stack","meta_descriptions":["Addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, but just improving isn't enough."],"attrs_boilerpipe_text":"This is the second of two parts. Read Part 1:\nWhy OpenTelemetry Is So Clunky for the Frontend\nIn Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with\nOpenTelemetry’s model of spans and traces\n. I’ll pick up where I left off by sharing another approach to make\nOpenTelemetry\nmore ergonomic for\nJavaScript\n. I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today.\nNow, as a reminder of where we left off last time, remember that traces, spans, span events and logs are all built on top of the same underlying primitive. That is, they’re all basically just events.\nDon’t Make Me Think\nIf we accept that OpenTelemetry is just events all the way down, then in theory, all you really have to do is write something like\ntrace.info()\nand pass in an object. That’s it. You can have\ntrace.info\n,\ntrace.error\n,\ntrace.warn\nand so on. Given the ubiquity of logging information, it shouldn’t be terribly surprising that most logging-like APIs are a quite natural interface for instrumentation. It\nworks perfectly for JavaScript and many other languages\n, including those that don’t have the ability to provide metaprogramming-style abstractions, thread-local state or other facilities that make OpenTelemetry’s API more ergonomic.\nWhile addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics.\nWhile addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. It’s a huge improvement! But certain additional functions would be really helpful. It’s still challenging to design telemetry and propagate it in a way that’s maximally useful.\nTaking inspiration from other types of instrumentation can give us some ideas of what might be useful here: What if there were a function to add metadata to the root span, regardless of where it is? Implementing this function would be tricky because span immutability is deeply central to the OpenTelemetry API, and violating that would break other things.\nHowever, another way to approach that would be durable reference values to sets of attributes, which could then be mutable. That would also potentially massively cut down on network bandwidth.\nTRENDING STORIES\nGoing further into the inspiration and ideas: What if there was a function to add a new span, but only if a parent span didn’t already exist, or otherwise attach things to the existing span? What if there were a function to take data and add it to every child span, maybe even recursively? What if there were a way to write instrumentation for a single function, but have that instrumentation remain useful when that function is called in a loop? And how could you write all of this without having to create custom processors or custom code to glue everything together in a way that makes sense for your use case?\nImagining the Future\nThis brings up a fascinating design space for me: If I were to look far into the future and imagine what telemetry could look like, what might be possible?\nLet’s take a step into this hypothetical future and imagine: What if the instrumentation library didn’t really exist in the traditional sense, and the code you were writing was actually going to be generated on the fly and rewritten by the compiler? You could use this to make instrumentation code very lightweight and minimal, essentially being custom-built for your application at compile time. You could use the compiler’s information to insert code structure automatically, add lifetime annotations, control flow information, call stack data and maybe even rewrite the telemetry to make more sense for your application’s needs.\nThis could facilitate very advanced instrumentation rewriting, minimization and compression as well; imagine a source map-style construct where you send binary pointers to certain common sets of data. You could even imagine normalizing or denormalizing telemetry automatically. Or enabling code to be written for both streaming and batch use cases without code changes. Collectors could roll and unroll telemetry for you, collapse certain pieces of data or even completely rewrite the telemetry tree as needed.\nBrowsers and language runtimes could also improve existing limitations by ensuring proper thread-local storage support, context propagation and support for context propagation inside async-like scopes.\nI’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment.\nThe ability to propagate information in a “magical” metadata object could also be a huge facilitator for building these types of structures, which could be thought of as similar to the reference of metadata idea I brought up earlier. If the language runtimes included explicit instrumentation support as well, then that instrumentation could be written in a heavily optimized manner, which would enable garbage-collected languages to benefit from low-to-zero overhead instrumentation. I find this exciting because it is an actual goal of the OpenTelemetry project, so the potential isn’t out of reach, but it’ll take a lot of coordination.\nIn addition, I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. Then you wouldn’t blow up everything with verbose debugging data when deploying to remote servers, but when debugging something locally, you could easily go all the way down to the system call level or even inspect the hardware to get extremely granular views of every interface, no matter how highly abstracted.\nJust because a language is high-level doesn’t mean you shouldn’t be able to examine the details when you need or want to. I think we could build languages in the future that allow this ergonomically, letting you instrument code for production while getting rich instrumentation for development, without having to instrument the system twice. Luckily, much of what is described here is an explicit outcome of the upcoming\nOpenTelemetry Profiling signal\n, so I hope to see a lot of progress in the next few years.\nLet’s step back and return to reality. The future is fun to think about, but what can we start with today?\nIf instrumentation were more tightly embedded into languages, then one could also imagine the uniform integration of other metadata, such as: debugging information, performance profiling, feature flags, marketing data, security events and experimentation data. Instead of each platform building its own SDKs and needing their own implementations, they could use instrumentation features built deeper into the language runtime itself. You could instrument once and feed that data into various platforms — from\nobservability and monitoring\nto security and experimentation — all using the same code.\nI like to imagine that future as being one where cross-functional collaboration is more accessible and where understanding the complex system being built becomes a truly company-wide endeavor. I’d love to see that happen.\nGetting to Better\nAll of that starry-eyed and sparkly future musing is great, but we might not realistically see those types of changes for years or even decades. It’d also require a lot of coordination, and it’s not clear whether the communities involved even want this to happen. So let’s step back and return to reality. The future is fun to think about, but what can we start with today?\nHere’s my thinking: Since events already exist in OpenTelemetry, and since almost everything is events under the hood, we could build support for “just sending events” as an OpenTelemetry specification — think of it as an alternative representation of spans, traces, logs and span events. This would give us a ton of freedom to write whatever library SDKs are needed for a language while retaining full compatibility with vendors. We’re pretty close to being able to do this today, as all it would require would be a modified SDK implementation and a modified stateful OTel Collector. If those two things happened, vendor compatibility would stay the same, and we’d get to experiment with what an event-based representation could look like.\nSome observability vendors are already adopting this telemetry flexibility mindset in their products, particularly those involved in the mobile space. One great example of that is\nEmbrace’s User Journeys\nfunctionality, where you can create custom user flows from existing telemetry you’re already collecting without having to restructure your code. If you’re interested in learning more, you can check out their\nupcoming live webinar\non Sept. 16 at 10 a.m. PT\/1 p.m. ET.\nAn event-based representation of telemetry data would also facilitate interoperating between traces, spans, logs and span events. It would also allow us to more easily migrate from logs to traces using the same code. This doesn’t mean that I think we’re going to get rid of the current SDK, however. It’s very useful for the backend and also represents a well-done “pay now” API where the client does some more work to handle the stateful nature of telemetry and, in exchange, the collector can be stateless. That means it’s very easy for vendors to be OpenTelemetry-compatible.\nI can easily see a future in which people choose between the “pay now” model, where state complexity lives on the client, versus a “pay later” model, where state complexity is in the collector, depending on what makes sense for their environment. High-volume microservices likely benefit from a “pay now” model, and the frontend works best with a “pay later” model.\nPutting the two together and being able to tie it all into a coherent context would unlock the next generation of understanding our systems. I can already see bits of this starting to happen, and it makes me really excited for the future of OpenTelemetry in the browser.\nI’ve mentioned in other blog posts that the\nCloud Native Computing Foundation (CNCF)\nhas a new dedicated Browser Special Interest Group (SIG) for it, which is actively working on improving browser support. I think that is going to create fascinating developments, and I truly look forward to seeing what it becomes one day. If you’d like to learn more about what the Browser SIG is working on, check out this\non-demand webinar\n.\nGroup\nCreated with Sketch.","attrs_markdown":"TNS\n\nOK\n\nSUBSCRIBE\n\nJoin our community of software engineering leaders and aspirational developers. Always stay in-the-know by getting the most important news and exclusive content delivered fresh to your inbox to learn more about at-scale software development.\n\nEMAIL ADDRESS\n\nREQUIRED\n\nSUBSCRIBE\n\nRESUBSCRIPTION REQUIRED\n\nIt seems that you've previously unsubscribed from our newsletter in the past. Click the button below to open the re-subscribe form in a new tab. When you're done, simply close that tab and continue with this form to complete your subscription.\n\nRE-SUBSCRIBE\n\nThe New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our [Terms of Use](https:\/\/thenewstack.io\/terms-of-use\/) and [Privacy Policy](https:\/\/thenewstack.io\/privacy-policy\/).\n\nWelcome and thank you for joining The New Stack community\\!\n\nPlease answer a few simple questions to help us deliver the news and resources you are interested in.\n\nFIRST NAME\n\nREQUIRED\n\nLAST NAME\n\nREQUIRED\n\nCOMPANY NAME\n\nREQUIRED\n\nCOUNTRY\n\nREQUIRED\n\nZIPCODE\n\nREQUIRED\n\nGreat to meet you\\!\n\nTell us a bit about your job so we can cover the topics you find most relevant.\n\nWhat is your job level?\n\nREQUIRED\n\nWhich of these most closely describes your job role?\n\nREQUIRED\n\nHow many employees are in the organization you work with?\n\nREQUIRED\n\nWhat option best describes the type of organization you work for?\n\nREQUIRED\n\nWhich of the following best describes your organization's primary industry?\n\nREQUIRED\n\nLINKEDIN PROFILE URL\n\nWelcome\\!\n\nWe’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game.\n\nWhat’s next?\n\nCheck your inbox for a confirmation email where you can adjust your preferences and even join additional groups.\n\nFollow TNS on your favorite social media networks.\n\nBecome a [TNS follower on LinkedIn](https:\/\/www.linkedin.com\/company\/the-new-stack).\n\nCheck out [the latest featured and trending stories](https:\/\/thenewstack.io\/) while you wait for your first TNS newsletter.\n\nPREV\n\n1 of 2\n\nNEXT\n\nVOXPOP\n\nAs a JavaScript developer, what non-React tools do you use most often?\n\n✓\n\nAngular\n\n0%\n\n✓\n\nAstro\n\n0%\n\n✓\n\nSvelte\n\n0%\n\n✓\n\nVue.js\n\n0%\n\n✓\n\nOther\n\n0%\n\n✓\n\nI only use React\n\n0%\n\n✓\n\nI don't use JavaScript\n\n0%\n\nThanks for your opinion! Subscribe below to get the final results, published exclusively in our TNS Update newsletter:\n\nSUBMIT\n\nNEW! Try Stackie AI\n\nLOGIN\n\nARCHITECTURE\n\n[Cloud Native Ecosystem](https:\/\/thenewstack.io\/cloud-native\/)   [Containers](https:\/\/thenewstack.io\/containers\/)   [Databases](https:\/\/thenewstack.io\/databases\/)   [Edge Computing](https:\/\/thenewstack.io\/edge-computing\/)   [Infrastructure as Code](https:\/\/thenewstack.io\/infrastructure-as-code\/)   [Linux](https:\/\/thenewstack.io\/linux\/)   [Microservices](https:\/\/thenewstack.io\/microservices\/)   [Open Source](https:\/\/thenewstack.io\/open-source\/)   [Networking](https:\/\/thenewstack.io\/networking\/)   [Storage](https:\/\/thenewstack.io\/storage\/)\n\nENGINEERING\n\n[AI](https:\/\/thenewstack.io\/ai\/)   [AI Engineering](https:\/\/thenewstack.io\/ai-engineering\/)   [API Management](https:\/\/thenewstack.io\/api-management\/)   [Backend development](https:\/\/thenewstack.io\/backend-development\/)   [Data](https:\/\/thenewstack.io\/data\/)   [Frontend Development](https:\/\/thenewstack.io\/frontend-development\/)   [Large Language Models](https:\/\/thenewstack.io\/llm\/)   [Security](https:\/\/thenewstack.io\/security\/)   [Software Development](https:\/\/thenewstack.io\/software-development\/)   [WebAssembly](https:\/\/thenewstack.io\/webassembly\/)\n\nOPERATIONS\n\n[AI Operations](https:\/\/thenewstack.io\/ai-operations\/)   [CI\/CD](https:\/\/thenewstack.io\/ci-cd\/)   [Cloud Services](https:\/\/thenewstack.io\/cloud-services\/)   [DevOps](https:\/\/thenewstack.io\/devops\/)   [Kubernetes](https:\/\/thenewstack.io\/kubernetes\/)   [Observability](https:\/\/thenewstack.io\/observability\/)   [Operations](https:\/\/thenewstack.io\/operations\/)   [Platform Engineering](https:\/\/thenewstack.io\/platform-engineering\/)\n\nPROGRAMMING\n\n[C++](https:\/\/thenewstack.io\/c\/)   [Developer tools](https:\/\/thenewstack.io\/developer-tools\/)   [Go](https:\/\/thenewstack.io\/go\/)   [Java](https:\/\/thenewstack.io\/java\/)   [JavaScript](https:\/\/thenewstack.io\/javascript\/)   [Programming Languages](https:\/\/thenewstack.io\/programming-languages\/)   [Python](https:\/\/thenewstack.io\/python\/)   [Rust](https:\/\/thenewstack.io\/rust\/)   [TypeScript](https:\/\/thenewstack.io\/typescript\/)\n\nCHANNELS\n\n[Podcasts](https:\/\/thenewstack.io\/podcasts\/)   [Ebooks](https:\/\/thenewstack.io\/ebooks\/)   [Events](https:\/\/thenewstack.io\/events\/)   [Webinars](https:\/\/thenewstack.io\/webinars\/)   [Newsletter](https:\/\/thenewstack.io\/newsletter\/)   [TNS RSS Feeds](https:\/\/thenewstack.io\/rss-feeds\/)\n\nTHE NEW STACK\n\n[About \/ Contact](https:\/\/thenewstack.io\/about-and-contact-info\/)   [Sponsors](https:\/\/thenewstack.io\/sponsors\/)   [Advertise With Us](https:\/\/thenewstack.io\/sponsorship\/)   [Contributions](https:\/\/thenewstack.io\/contributions\/)\n\n[PODCASTS](https:\/\/thenewstack.io\/podcasts\/) [EBOOKS](https:\/\/thenewstack.io\/ebooks\/) [EVENTS](https:\/\/thenewstack.io\/events\/) [WEBINARS](https:\/\/thenewstack.io\/webinars\/) [NEWSLETTER](https:\/\/thenewstack.io\/newsletter\/) [CONTRIBUTE](https:\/\/thenewstack.io\/contributions\/)\n\n[ARCHITECTURE](https:\/\/thenewstack.io\/how-to-make-opentelemetry-better-in-the-browser\/)   [ENGINEERING](https:\/\/thenewstack.io\/how-to-make-opentelemetry-better-in-the-browser\/)   [OPERATIONS](https:\/\/thenewstack.io\/how-to-make-opentelemetry-better-in-the-browser\/)   [PROGRAMMING](https:\/\/thenewstack.io\/how-to-make-opentelemetry-better-in-the-browser\/)\n\n[Cloud Native Ecosystem](https:\/\/thenewstack.io\/cloud-native\/)   [Containers](https:\/\/thenewstack.io\/containers\/)   [Databases](https:\/\/thenewstack.io\/databases\/)   [Edge Computing](https:\/\/thenewstack.io\/edge-computing\/)   [Infrastructure as Code](https:\/\/thenewstack.io\/infrastructure-as-code\/)   [Linux](https:\/\/thenewstack.io\/linux\/)   [Microservices](https:\/\/thenewstack.io\/microservices\/)   [Open Source](https:\/\/thenewstack.io\/open-source\/)   [Networking](https:\/\/thenewstack.io\/networking\/)   [Storage](https:\/\/thenewstack.io\/storage\/)\n\n[WebAssembly is now outperforming containers at the edge Mar 29th 2026 9:00am, by B. Cameron Gain](https:\/\/thenewstack.io\/webassembly-component-model-future\/)\n\n[How platform teams are eliminating a \\$43,800 \"hidden tax\" on Kubernetes infrastructure Mar 28th 2026 4:09pm, by Janakiram MSV](https:\/\/thenewstack.io\/virtual-clusters-kubernetes-cost-isolation\/)\n\n[Solo.io launches agentevals to solve agentic AI's \"biggest unsolved problem\" Mar 28th 2026 6:00am, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/soloio-agentevals-evaluates-ai-agents\/)\n\n[Why WebAssembly won't replace Kubernetes but makes Helm more secure Mar 21st 2026 8:45am, by B. Cameron Gain](https:\/\/thenewstack.io\/helm-webassembly-kubernetes-security\/)\n\n[Why the ‘glorified host’ for AI is exactly the Kubernetes we need Mar 20th 2026 9:00am, by Danielle Cook](https:\/\/thenewstack.io\/kubernetes-glorified-ai-host\/)\n\n[Edera spent years calling KVM less secure. Here's why it changed its mind. Mar 25th 2026 2:22pm, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/edera-adds-kvm-support\/)\n\n[Minimus aims to solve one of open-source's long-festering problems Mar 24th 2026 3:00am, by Adrian Bridgwater](https:\/\/thenewstack.io\/minimus-open-source-container-security\/)\n\n[How to deploy Pi-Hole with Docker and stop ads on every device on your LAN Mar 23rd 2026 7:44am, by Jack Wallen](https:\/\/thenewstack.io\/pihole-docker-network-adblocking\/)\n\n[Chainguard has a fix for the open source packages your AI agents keep grabbing Mar 18th 2026 9:24am, by Darryl K. Taft](https:\/\/thenewstack.io\/chainguard-repository-ai-agents\/)\n\n[Chainguard thinks most DevOps teams are solving container security the hard way Mar 17th 2026 1:04pm, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/chainguard-os-packages-containers\/)\n\n[The reason your pgvector benchmark is lying to you Mar 27th 2026 5:00am, by Naina Ananthaswamy](https:\/\/thenewstack.io\/why-pgvector-benchmarks-lie\/)\n\n[Scaling Btrfs to petabytes in production: a 74% cost reduction story Mar 18th 2026 5:00am, by Motiejus Jakštys](https:\/\/thenewstack.io\/btrfs-petabyte-cost-reduction\/)\n\n[The “files are all you need” debate misses what's actually happening in agent memory architecture Mar 13th 2026 5:00am, by Mikiko Bazeley](https:\/\/thenewstack.io\/ai-agent-memory-architecture\/)\n\n[With GridGain acquisition, MariaDB bets on in-memory computing and Apache Ignite Mar 10th 2026 6:47am, by Paul Sawers](https:\/\/thenewstack.io\/with-gridgain-acquisition-mariadb-bets-on-in-memory-computing-and-apache-ignite\/)\n\n[Moving AI apps from prototype to production requires enterprise-grade postgres infrastructure Mar 9th 2026 7:00am, by Meredith Shubel](https:\/\/thenewstack.io\/ai-prototype-to-production-postgres\/)\n\n[Edge-forward: Akamai eyes sweet spot between centralized & decentralized AI inference Apr 1st 2026 7:00am, by Adrian Bridgwater](https:\/\/thenewstack.io\/akamai-edge-ai-inference\/)\n\n[Developers are coding to a moving target, and nobody knows where AI lands next Mar 3rd 2026 7:33am, by Adrian Bridgwater](https:\/\/thenewstack.io\/developers-coding-moving-target-ai\/)\n\n[Cloudflare’s new Markdown support shows how the web is evolving for AI agents Mar 2nd 2026 4:30am, by David Eastman](https:\/\/thenewstack.io\/intent-engineering-ai-agents\/)\n\n[React Server Components Vulnerability Found Dec 6th 2025 7:00am, by Loraine Lawson](https:\/\/thenewstack.io\/react-server-components-vulnerability-found\/)\n\n[Kubernetes at the Edge: Lessons From GE HealthCare’s Edge Strategy Nov 24th 2025 10:00am, by Vicki Walker](https:\/\/thenewstack.io\/kubernetes-at-the-edge-lessons-from-ge-healthcares-edge-strategy\/)\n\n[The operational gap is real, and it's getting wider Mar 26th 2026 8:00am, by Yevgeny Pats](https:\/\/thenewstack.io\/closing-cloud-operational-gap\/)\n\n[Why \"automated\" infrastructure might cost more than you think Feb 24th 2026 4:00am, by Justyn Roberts](https:\/\/thenewstack.io\/automated-infrastructure-hidden-costs\/)\n\n[Why 40% of AI projects will be canceled by 2027 (and how to stay in the other 60%) Feb 13th 2026 6:00am, by Alex Drag](https:\/\/thenewstack.io\/agentic-ai-connectivity-platform\/)\n\n[Durable Execution: Build reliable software in an unreliable world Feb 2nd 2026 3:23pm, by Charles Humble](https:\/\/thenewstack.io\/temporal-durable-execution-platform\/)\n\n[Terraform challenger Formae expands to more clouds Jan 28th 2026 6:00am, by Joab Jackson](https:\/\/thenewstack.io\/terraform-competitor-formae-expands-to-more-clouds\/)\n\n[Sparky Linux 9 brings a rolling release to Debian Mar 30th 2026 8:00am, by Jack Wallen](https:\/\/thenewstack.io\/sparky-linux-9-brings-a-rolling-release-to-debian\/)\n\n[Edera spent years calling KVM less secure. Here's why it changed its mind. Mar 25th 2026 2:22pm, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/edera-adds-kvm-support\/)\n\n[Linux kernel scale is swamping an already-flawed CVE system Mar 20th 2026 4:30am, by Jed Salazar](https:\/\/thenewstack.io\/linux-kernel-cve-system\/)\n\n[Scaling Btrfs to petabytes in production: a 74% cost reduction story Mar 18th 2026 5:00am, by Motiejus Jakštys](https:\/\/thenewstack.io\/btrfs-petabyte-cost-reduction\/)\n\n[Chainguard thinks most DevOps teams are solving container security the hard way Mar 17th 2026 1:04pm, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/chainguard-os-packages-containers\/)\n\n[Tetrate launches open source marketplace to simplify Envoy adoption Mar 11th 2026 10:52am, by Adrian Bridgwater](https:\/\/thenewstack.io\/tetrate-built-on-envoy\/)\n\n[OpenTelemetry roadmap: Sampling rates and collector improvements ahead Feb 24th 2026 11:00am, by B. Cameron Gain](https:\/\/thenewstack.io\/opentelemetry-roadmap-sampling-rates-and-collector-improvements-ahead\/)\n\n[Merging To Test Is Killing Your Microservices Velocity Dec 16th 2025 7:00am, by Arjun Iyer](https:\/\/thenewstack.io\/merging-to-test-is-killing-your-microservices-velocity\/)\n\n[IBM’s Confluent Acquisition Is About Event-Driven AI Dec 11th 2025 6:00am, by Joab Jackson](https:\/\/thenewstack.io\/ibms-confluent-acquisition-is-about-event-driven-ai\/)\n\n[Deploy Agentic AI Workflows With Kubernetes and Terraform Nov 26th 2025 9:00am, by Oladimeji Sowole](https:\/\/thenewstack.io\/deploy-agentic-ai-workflows-with-kubernetes-and-terraform\/)\n\n[Portkey open-sources its AI gateway after processing 2 trillion tokens a day Mar 31st 2026 3:53pm, by Adrian Bridgwater](https:\/\/thenewstack.io\/portkey-gateway-open-source\/)\n\n[Ollama taps Apple’s MLX framework to make local AI models faster on Macs Mar 31st 2026 8:00am, by Paul Sawers](https:\/\/thenewstack.io\/ollama-taps-apples-mlx\/)\n\n[96% of codebases rely on open source, and AI slop is putting them at risk Mar 29th 2026 6:00am, by Bill Doerrfeld](https:\/\/thenewstack.io\/ai-slop-open-source\/)\n\n[Gitleaks creator returns with Betterleaks, an open source secrets scanner for the agentic era Mar 27th 2026 11:00am, by Paul Sawers](https:\/\/thenewstack.io\/betterleaks-open-source-secret-scanner\/)\n\n[How TeamPCP turned Aqua Security's own Trivy scanner into a weapon against millions of developers Mar 27th 2026 10:00am, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/teampcp-trivy-supply-chain-attack\/)\n\n[How to deploy Pi-Hole with Docker and stop ads on every device on your LAN Mar 23rd 2026 7:44am, by Jack Wallen](https:\/\/thenewstack.io\/pihole-docker-network-adblocking\/)\n\n[Why flat Kubernetes networks fail at scale Mar 20th 2026 7:00am, by Reza Ramezanpour](https:\/\/thenewstack.io\/kubernetes-network-security-hierarchies\/)\n\n[GSMA Open Gateway offers developers one API for 300+ mobile networks Mar 4th 2026 10:26am, by Adrian Bridgwater](https:\/\/thenewstack.io\/gsma-open-gateway-developers\/)\n\n[How Homepage simplifies monitoring your self-hosted services Feb 6th 2026 8:00am, by Jack Wallen](https:\/\/thenewstack.io\/how-homepage-simplifies-monitoring-your-self-hosted-services\/)\n\n[S3 is the new network: Rethinking data architecture for the cloud era Feb 2nd 2026 4:00am, by Max Liu](https:\/\/thenewstack.io\/tidb-x-open-source-database\/)\n\n[Scaling Btrfs to petabytes in production: a 74% cost reduction story Mar 18th 2026 5:00am, by Motiejus Jakštys](https:\/\/thenewstack.io\/btrfs-petabyte-cost-reduction\/)\n\n[What is KubeVirt and why it’s growing Mar 17th 2026 9:00am, by Tiago Castro](https:\/\/thenewstack.io\/kubevirt-live-migration-mayastor\/)\n\n[S3 is the new network: Rethinking data architecture for the cloud era Feb 2nd 2026 4:00am, by Max Liu](https:\/\/thenewstack.io\/tidb-x-open-source-database\/)\n\n[Agoda’s secret to 50x scale: Getting the database basics right Jan 28th 2026 7:00am, by Cynthia Dunlop](https:\/\/thenewstack.io\/agodas-secret-to-50x-scale-getting-the-database-basics-right\/)\n\n[Chainguard EmeritOSS backs MinIO, other orphaned projects Jan 27th 2026 6:15am, by Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/chainguard-emeritoss-backs-minio-other-orphaned-projects\/)\n\n[AI](https:\/\/thenewstack.io\/ai\/)   [AI Engineering](https:\/\/thenewstack.io\/ai-engineering\/)   [API Management](https:\/\/thenewstack.io\/api-management\/)   [Backend development](https:\/\/thenewstack.io\/backend-development\/)   [Data](https:\/\/thenewstack.io\/data\/)   [Frontend Development](https:\/\/thenewstack.io\/frontend-development\/)   [Large Language Models](https:\/\/thenewstack.io\/llm\/)   [Security](https:\/\/thenewstack.io\/security\/)   [Software Development](https:\/\/thenewstack.io\/software-development\/)   [WebAssembly](https:\/\/thenewstack.io\/webassembly\/)\n\n[How to integrate VS Code with Ollama for local AI assistance](https:\/\/thenewstack.io\/how-to-integrate-vs-code-with-ollama-for-local-ai-assistance\/)\n\nApr 1st 2026 8:00am, by   [Jack Wallen](https:\/\/thenewstack.io\/author\/jack-wallen\/ \"Posts by Jack Wallen\")\n\n[Claude Code users say they’re hitting usage limits faster than normal](https:\/\/thenewstack.io\/claude-code-usage-limits\/)\n\nMar 31st 2026 2:30pm, by   [Meredith Shubel](https:\/\/thenewstack.io\/author\/mshubel\/ \"Posts by Meredith Shubel\")\n\n[Ollama taps Apple’s MLX framework to make local AI models faster on Macs](https:\/\/thenewstack.io\/ollama-taps-apples-mlx\/)\n\nMar 31st 2026 8:00am, by   [Paul Sawers](https:\/\/thenewstack.io\/author\/paul-sawers\/ \"Posts by Paul Sawers\")\n\n[Kelsey Hightower at KubeCon 2026: \"Everyone is a junior engineer when it comes to AI\"](https:\/\/thenewstack.io\/hightower-ai-open-source-kubecon\/)\n\nMar 30th 2026 2:45pm, by   [Jennifer Riggins](https:\/\/thenewstack.io\/author\/jennifer-riggins\/ \"Posts by Jennifer Riggins\")\n\n[Microsoft's Copilot makes Anthropic's Claude and OpenAI's GPT team up](https:\/\/thenewstack.io\/microsofts-copilot-llm-team\/)\n\nMar 30th 2026 9:00am, by   [Frederic Lardinois](https:\/\/thenewstack.io\/author\/frederic-lardinois\/ \"Posts by Frederic Lardinois\")\n\n[AI accelerates modernization, but don’t leave human devs behind](https:\/\/thenewstack.io\/ai-modernization-human-developers\/)\n\nMar 31st 2026 12:00pm, by   [Matthew Weier O’Phinney](https:\/\/thenewstack.io\/author\/matthew-weier-ophinney\/ \"Posts by Matthew Weier O’Phinney\")\n\n[Build it yourself: A data pipeline that trains a real model](https:\/\/thenewstack.io\/data-pipelines-serve-ai\/)\n\nMar 28th 2026 9:00am, by   [Jessica Wachtel](https:\/\/thenewstack.io\/author\/jessica-wachtel\/ \"Posts by Jessica Wachtel\")\n\n[Why online stores keep showing the wrong products — and why tensors fix it](https:\/\/thenewstack.io\/tensor-ranking-product-discovery\/)\n\nMar 25th 2026 6:00am, by   [Tim Young](https:\/\/thenewstack.io\/author\/tim-young\/ \"Posts by Tim Young\")\n\n[OpenClaw's biggest security flaw is why Jentic Mini exists](https:\/\/thenewstack.io\/openclaw-is-a-security-mess-jentic-wants-to-fix-it\/)\n\nMar 25th 2026 5:00am, by   [Darryl K. Taft](https:\/\/thenewstack.io\/author\/darryl-taft\/ \"Posts by Darryl K. Taft\")\n\n[Why most AI projects fail after the demo actually works](https:\/\/thenewstack.io\/ai-demo-to-production\/)\n\nMar 25th 2026 4:00am, by   [Oladimeji Sowole](https:\/\/thenewstack.io\/author\/oladimeji-sowole\/ \"Posts by Oladimeji Sowole\")\n\n[MCP is everywhere, but don't panic. Here's why your existing APIs still matter.](https:\/\/thenewstack.io\/api-mcp-agent-integration\/)\n\nMar 23rd 2026 5:00am, by   [Camille Crowell-Lee](https:\/\/thenewstack.io\/author\/camille-crowell-lee\/ \"Posts by Camille Crowell-Lee\") and [Morgan Fine](https:\/\/thenewstack.io\/author\/morgan-fine\/ \"Posts by Morgan Fine\")\n\n[Before you let AI agents loose, you’d better know what they’re capable of](https:\/\/thenewstack.io\/risk-mitigation-agentic-ai\/)\n\nMar 12th 2026 1:22pm, by   [Charles Humble](https:\/\/thenewstack.io\/author\/charles-humble\/ \"Posts by Charles Humble\")\n\n[GSMA Open Gateway offers developers one API for 300+ mobile networks](https:\/\/thenewstack.io\/gsma-open-gateway-developers\/)\n\nMar 4th 2026 10:26am, by   [Adrian Bridgwater](https:\/\/thenewstack.io\/author\/adrian-bridgwater\/ \"Posts by Adrian Bridgwater\")\n\n[Your AI strategy is built on layers of API sediment](https:\/\/thenewstack.io\/ai-strategy-api-sediment\/)\n\nFeb 17th 2026 9:37am, by   [Charles Humble](https:\/\/thenewstack.io\/author\/charles-humble\/ \"Posts by Charles Humble\")\n\n[Solving the Problems That Accompany API Sprawl With AI](https:\/\/thenewstack.io\/solving-the-problems-that-accompany-api-sprawl-with-ai\/)\n\nJan 15th 2026 1:00pm, by   [Heather Joslyn](https:\/\/thenewstack.io\/author\/hjoslyn\/ \"Posts by Heather Joslyn\")\n\n[Backend Development in 2026: What's Changed, What Matters, and What to Learn Next](https:\/\/thenewstack.io\/introduction-to-backend-development\/)\n\nMar 19th 2026 11:37am, by   [TNS Staff](https:\/\/thenewstack.io\/author\/tns-staff\/ \"Posts by TNS Staff\")\n\n[How To Get DNS Right: A Guide to Common Failure Modes](https:\/\/thenewstack.io\/how-to-get-dns-right-a-guide-to-common-failure-modes\/)\n\nDec 24th 2025 8:00am, by   [Sheldon Pereira](https:\/\/thenewstack.io\/author\/sheldon-pereira\/ \"Posts by Sheldon Pereira\") and [Denton Chikura](https:\/\/thenewstack.io\/author\/denton-chikura\/ \"Posts by Denton Chikura\")\n\n[Combining Rust and Python for High-Performance AI Systems](https:\/\/thenewstack.io\/combining-rust-and-python-for-high-performance-ai-systems\/)\n\nDec 3rd 2025 1:00pm, by   [Zziwa Raymond Ian](https:\/\/thenewstack.io\/author\/zziwa-raymond\/ \"Posts by Zziwa Raymond Ian\")\n\n[How MCP Uses Streamable HTTP for Real-Time AI Tool Interaction](https:\/\/thenewstack.io\/how-mcp-uses-streamable-http-for-real-time-ai-tool-interaction\/)\n\nAug 18th 2025 10:34am, by   [Janakiram MSV](https:\/\/thenewstack.io\/author\/janakiram\/ \"Posts by Janakiram MSV\")\n\n[A Backend for Frontend: Watt for Node.js Simplifies Operations](https:\/\/thenewstack.io\/a-backend-for-frontend-watt-for-node-js-simplifies-operations\/)\n\nAug 14th 2025 6:00am, by   [Loraine Lawson](https:\/\/thenewstack.io\/author\/loraine-lawson\/ \"Posts by Loraine Lawson\")\n\n[Build it yourself: A data pipeline that trains a real model](https:\/\/thenewstack.io\/data-pipelines-serve-ai\/)\n\nMar 28th 2026 9:00am, by   [Jessica Wachtel](https:\/\/thenewstack.io\/author\/jessica-wachtel\/ \"Posts by Jessica Wachtel\")\n\n[Fivetran donates its SQLMesh data transformation framework to the Linux Foundation](https:\/\/thenewstack.io\/fivetran-donates-sqlmesh-lf\/)\n\nMar 25th 2026 7:39am, by   [Frederic Lardinois](https:\/\/thenewstack.io\/author\/frederic-lardinois\/ \"Posts by Frederic Lardinois\")\n\n[Ex-Snowflake engineers say there's a blind spot in data engineering — so they built Tower to fix it](https:\/\/thenewstack.io\/tower-python-data-pipelines\/)\n\nMar 15th 2026 7:00am, by   [Paul Sawers](https:\/\/thenewstack.io\/author\/paul-sawers\/ \"Posts by Paul Sawers\")\n\n[Why the \"bible\" of data systems is getting a massive rewrite for 2026](https:\/\/thenewstack.io\/data-intensive-applications-rewrite-2026\/)\n\nMar 4th 2026 5:00am, by   [Cynthia Dunlop](https:\/\/thenewstack.io\/author\/cynthiadunlop\/ \"Posts by Cynthia Dunlop\")\n\n[How to clone a drive to an image with Clonezilla](https:\/\/thenewstack.io\/how-to-clone-a-drive-to-an-image-with-clonezilla\/)\n\nMar 3rd 2026 1:00pm, by   [Jack Wallen](https:\/\/thenewstack.io\/author\/jack-wallen\/ \"Posts by Jack Wallen\")\n\n[WebMCP turns any Chrome web page into an MCP server for AI agents](https:\/\/thenewstack.io\/webmcp-chrome-ai-agents\/)\n\nMar 17th 2026 11:50am, by   [David Eastman](https:\/\/thenewstack.io\/author\/david-eastman\/ \"Posts by David Eastman\")\n\n[Confluent adds A2A support, anomaly detection, and Queues for Kafka in major platform update](https:\/\/thenewstack.io\/confluent-kafka-a2a-agents\/)\n\nMar 3rd 2026 10:21am, by   [Jelani Harper](https:\/\/thenewstack.io\/author\/jelani-harper\/ \"Posts by Jelani Harper\")\n\n[Google's Chrome browser moves to a two-week release cycle](https:\/\/thenewstack.io\/chrome-two-week-releases\/)\n\nMar 3rd 2026 9:00am, by   [Frederic Lardinois](https:\/\/thenewstack.io\/author\/frederic-lardinois\/ \"Posts by Frederic Lardinois\")\n\n[Meta gave React its own foundation. But it's not letting go just yet.](https:\/\/thenewstack.io\/react-foundation-open-source-governance\/)\n\nMar 3rd 2026 4:00am, by   [Paul Sawers](https:\/\/thenewstack.io\/author\/paul-sawers\/ \"Posts by Paul Sawers\")\n\n[The shift left hangover: Why modern platforms are shifting down to cure developer fatigue](https:\/\/thenewstack.io\/shift-left-hangover-steve-corndell\/)\n\nJan 30th 2026 6:22pm, by   [Steve Corndell](https:\/\/thenewstack.io\/author\/steve-corndell\/ \"Posts by Steve Corndell\")\n\n[Why most AI projects fail after the demo actually works](https:\/\/thenewstack.io\/ai-demo-to-production\/)\n\nMar 25th 2026 4:00am, by   [Oladimeji Sowole](https:\/\/thenewstack.io\/author\/oladimeji-sowole\/ \"Posts by Oladimeji Sowole\")\n\n[IBM, Red Hat, and Google just donated a Kubernetes blueprint for LLM inference to the CNCF](https:\/\/thenewstack.io\/llm-d-cncf-kubernetes-inference\/)\n\nMar 24th 2026 8:20am, by   [Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/author\/sjvn\/ \"Posts by Steven J. Vaughan-Nichols\")\n\n[Andrej Karpathy's 630-line Python script ran 50 experiments overnight without any human input](https:\/\/thenewstack.io\/karpathy-autonomous-experiment-loop\/)\n\nMar 14th 2026 5:00am, by   [Janakiram MSV](https:\/\/thenewstack.io\/author\/janakiram\/ \"Posts by Janakiram MSV\")\n\n[\"Self-healing\" IT? HPE research explores how AI-trained models can catch silent infrastructure failures](https:\/\/thenewstack.io\/hpe-self-healing-ai-infrastructure\/)\n\nMar 11th 2026 9:37am, by   [Jennifer Riggins](https:\/\/thenewstack.io\/author\/jennifer-riggins\/ \"Posts by Jennifer Riggins\")\n\n[How context rot drags down AI and LLM results for enterprises, and how to fix it](https:\/\/thenewstack.io\/context-rot-enterprise-ai-llms\/)\n\nMar 9th 2026 9:00am, by   [Todd R. Weiss](https:\/\/thenewstack.io\/author\/todd-r-weiss\/ \"Posts by Todd R. Weiss\")\n\n[Inside Claude Code's leaked source: swarms, daemons, and 44 features Anthropic kept behind flags](https:\/\/thenewstack.io\/claude-code-source-leak\/)\n\nApr 1st 2026 7:23am, by   [Janakiram MSV](https:\/\/thenewstack.io\/author\/janakiram\/ \"Posts by Janakiram MSV\")\n\n[Nvidia's NemoClaw has three layers of agent security. None of them solve the real problem.](https:\/\/thenewstack.io\/nvidia-nemoclaw-openclaw-security\/)\n\nMar 28th 2026 9:30am, by   [David Eastman](https:\/\/thenewstack.io\/author\/david-eastman\/ \"Posts by David Eastman\")\n\n[Gitleaks creator returns with Betterleaks, an open source secrets scanner for the agentic era](https:\/\/thenewstack.io\/betterleaks-open-source-secret-scanner\/)\n\nMar 27th 2026 11:00am, by   [Paul Sawers](https:\/\/thenewstack.io\/author\/paul-sawers\/ \"Posts by Paul Sawers\")\n\n[How TeamPCP turned Aqua Security's own Trivy scanner into a weapon against millions of developers](https:\/\/thenewstack.io\/teampcp-trivy-supply-chain-attack\/)\n\nMar 27th 2026 10:00am, by   [Steven J. Vaughan-Nichols](https:\/\/thenewstack.io\/author\/sjvn\/ \"Posts by Steven J. Vaughan-Nichols\")\n\n[OpenClaw's biggest security flaw is why Jentic Mini exists](https:\/\/thenewstack.io\/openclaw-is-a-security-mess-jentic-wants-to-fix-it\/)\n\nMar 25th 2026 5:00am, by   [Darryl K. Taft](https:\/\/thenewstack.io\/author\/darryl-taft\/ \"Posts by Darryl K. Taft\")\n\n[How to solve the AI paradox in software development with intelligent orchestration](https:\/\/thenewstack.io\/solve-ai-paradox-orchestration\/)\n\nMar 31st 2026 12:14pm, by   [Manav Khurana](https:\/\/thenewstack.io\/author\/manav-khurana\/ \"Posts by Manav Khurana\")\n\n[AI accelerates modernization, but don’t leave human devs behind](https:\/\/thenewstack.io\/ai-modernization-human-developers\/)\n\nMar 31st 2026 12:00pm, by   [Matthew Weier O’Phinney](https:\/\/thenewstack.io\/author\/matthew-weier-ophinney\/ \"Posts by Matthew Weier O’Phinney\")\n\n[Kelsey Hightower at KubeCon 2026: \"Everyone is a junior engineer when it comes to AI\"](https:\/\/thenewstack.io\/hightower-ai-open-source-kubecon\/)\n\nMar 30th 2026 2:45pm, by   [Jennifer Riggins](https:\/\/thenewstack.io\/author\/jennifer-riggins\/ \"Posts by Jennifer Riggins\")\n\n[WebAssembly is now outperforming containers at the edge](https:\/\/thenewstack.io\/webassembly-component-model-future\/)\n\nMar 29th 2026 9:00am, by   [B. Cameron Gain](https:\/\/thenewstack.io\/author\/bruce-gain\/ \"Posts by B. Cameron Gain\")\n\n[96% of codebases rely on open source, and AI slop is putting them at risk](https:\/\/thenewstack.io\/ai-slop-open-source\/)\n\nMar 29th 2026 6:00am, by   [Bill Doerrfeld](https:\/\/thenewstack.io\/author\/bill-doerrfeld\/ \"Posts by Bill Doerrfeld\")\n\n[Edge-forward: Akamai eyes sweet spot between centralized & decentralized AI inference](https:\/\/thenewstack.io\/akamai-edge-ai-inference\/)\n\nApr 1st 2026 7:00am, by   [Adrian Bridgwater](https:\/\/thenewstack.io\/author\/adrian-bridgwater\/ \"Posts by Adrian Bridgwater\")\n\n[WebAssembly is now outperforming containers at the edge](https:\/\/thenewstack.io\/webassembly-component-model-future\/)\n\nMar 29th 2026 9:00am, by   [B. Cameron Gain](https:\/\/thenewstack.io\/author\/bruce-gain\/ \"Posts by B. Cameron Gain\")\n\n[WebAssembly could solve AI agents' most dangerous security gap](https:\/\/thenewstack.io\/webassembly-sandboxing-ai-agents\/)\n\nMar 24th 2026 9:01am, by   [B. Cameron Gain](https:\/\/thenewstack.io\/author\/bruce-gain\/ \"Posts by B. Cameron Gain\")\n\n[How WebAssembly plugins simplify Kubernetes extensibility](https:\/\/thenewstack.io\/how-webassembly-plugins-simplify-kubernetes-extensibility\/)\n\nMar 3rd 2026 2:00pm, by   [B. Cameron Gain](https:\/\/thenewstack.io\/author\/bruce-gain\/ \"Posts by B. Cameron Gain\")\n\n[WebAssembly is everywhere. Here's how it works](https:\/\/thenewstack.io\/webassembly-is-everywhere-heres-how-it-works\/)\n\nFeb 25th 2026 11:00am, by   [Jessica Wachtel](https:\/\/thenewstack.io\/author\/jessica-wachtel\/ \"Posts by Jessica Wachtel\")\n\n[AI Operations](https:\/\/thenewstack.io\/ai-operations\/)   [CI\/CD](https:\/\/thenewstack.io\/ci-cd\/)   [Cloud Services](https:\/\/thenewstack.io\/cloud-services\/)   [DevOps](https:\/\/thenewstack.io\/devops\/)   [Kubernetes](https:\/\/thenewstack.io\/kubernetes\/)   [Observability](https:\/\/thenewstack.io\/observability\/)   [Operations](https:\/\/thenewstack.io\/operations\/)   [Platform Engineering](https:\/\/thenewstack.io\/platform-engineering\/)\n\n[JetBrains: AI agents are about to repeat the cloud ROI crisis](https:\/\/thenewstack.io\/jetbrains-central-ai-agents\/)\n\nMar 31st 2026 4:02pm, by   Darryl K. Taft\n\n[HPE's AI agents cut root cause analysis time in half](https:\/\/thenewstack.io\/hpes-ai-agents-cut-root-cause-analysis-time-in-half\/)\n\nMar 25th 2026 7:14am, by   Jennifer Riggins\n\n[Why most AI projects fail after the demo actually works](https:\/\/thenewstack.io\/ai-demo-to-production\/)\n\nMar 25th 2026 4:00am, by   Oladimeji Sowole\n\n[From pillars to platform: How open observability data is changing the industry](https:\/\/thenewstack.io\/open-observability-ai-platforms\/)\n\nMar 20th 2026 6:00am, by   Ted Young\n\n[Building a Kubernetes-native pattern for AI infrastructure at scale](https:\/\/thenewstack.io\/kubernetes-native-ai-infrastructure\/)\n\nMar 19th 2026 5:00am, by   Sachi Desai\n\n[How TeamPCP turned Aqua Security's own Trivy scanner into a weapon against millions of developers](https:\/\/thenewstack.io\/teampcp-trivy-supply-chain-attack\/)\n\nMar 27th 2026 10:00am, by   Steven J. Vaughan-Nichols\n\n[Enterprise dev teams are about to hit a wall. And CI pipelines can't save them.](https:\/\/thenewstack.io\/ai-agent-validation-bottleneck\/)\n\nMar 26th 2026 7:00am, by   Anirudh Ramanathan\n\n[This simple infrastructure gap is holding back AI productivity](https:\/\/thenewstack.io\/this-simple-infrastructure-gap-is-holding-back-ai-productivity\/)\n\nFeb 22nd 2026 8:00am, by   Charlotte Fleming\n\n[Ramp’s Inspect shows closed-loop AI agents are software’s future](https:\/\/thenewstack.io\/ramps-inspect-shows-closed-loop-ai-agents-are-softwares-future\/)\n\nJan 29th 2026 11:00am, by   Arjun Iyer\n\n[QCon chat: Is agentic AI killing continuous integration?](https:\/\/thenewstack.io\/qcon-chat-is-agentic-ai-killing-continuous-integration\/)\n\nJan 27th 2026 6:00am, by   Joab Jackson\n\n[A practical guide to the 6 categories of AI cloud infrastructure in 2026](https:\/\/thenewstack.io\/ai-cloud-taxonomy-2026\/)\n\nMar 15th 2026 5:00am, by   Janakiram MSV\n\n[Runpod report: Qwen has overtaken Meta's Llama as the most-deployed self-hosted LLM](https:\/\/thenewstack.io\/runpod-ai-infrastructure-reality\/)\n\nMar 12th 2026 6:00am, by   Adrian Bridgwater\n\n[Snowflake Cortex Code CLI adds dbt and Apache Airflow support for AI-powered data pipelines](https:\/\/thenewstack.io\/snowflake-cortex-code-dbt-airflow\/)\n\nMar 8th 2026 6:00am, by   Jelani Harper\n\n[Databases weren’t built for agent sprawl – SurrealDB wants to fix it](https:\/\/thenewstack.io\/surrealdb-3-ai-agents\/)\n\nFeb 24th 2026 2:07pm, by   Paul Sawers\n\n[Rising identity complexity: How CISOs can prevent it from becoming an attacker’s roadmap](https:\/\/thenewstack.io\/ciso-identity-complexity-strategy\/)\n\nFeb 19th 2026 12:47pm, by   Jay Reddy\n\n[One developer, team power: The future of AI-driven DevSecOps](https:\/\/thenewstack.io\/future-ai-driven-devsecops\/)\n\nMar 5th 2026 2:29pm, by   Bryan Ross\n\n[Observability platform migration guide: Prometheus, OpenTelemetry, and Fluent Bit](https:\/\/thenewstack.io\/observability-platform-migration-guide\/)\n\nFeb 26th 2026 7:28am, by   Katie Greenley\n\n[Most platform teams build products, but they don’t know it](https:\/\/thenewstack.io\/internal-platforms-are-products\/)\n\nFeb 24th 2026 9:00am, by   Oleg Danilyuk\n\n[Why \"automated\" infrastructure might cost more than you think](https:\/\/thenewstack.io\/automated-infrastructure-hidden-costs\/)\n\nFeb 24th 2026 4:00am, by   Justyn Roberts\n\n[The essential shift every ITOps leader must make to survive an unrelenting stream of incidents](https:\/\/thenewstack.io\/modernizing-itops-incident-management\/)\n\nFeb 19th 2026 1:46pm, by   Ariel Russo\n\n[How platform teams are eliminating a \\$43,800 \"hidden tax\" on Kubernetes infrastructure](https:\/\/thenewstack.io\/virtual-clusters-kubernetes-cost-isolation\/)\n\nMar 28th 2026 4:09pm, by   Janakiram MSV\n\n[Your Kubernetes isn't ready for AI workloads, and drift is the reason](https:\/\/thenewstack.io\/ai-workloads-kubernetes-infrastructure-drift\/)\n\nMar 25th 2026 8:43am, by   TNS Staff\n\n[Broadcom donates Velero to CNCF — and it could reshape how Kubernetes users handle backup and disaster recovery](https:\/\/thenewstack.io\/broadcom-velero-cncf-kubernetes\/)\n\nMar 24th 2026 8:38am, by   B. Cameron Gain\n\n[IBM, Red Hat, and Google just donated a Kubernetes blueprint for LLM inference to the CNCF](https:\/\/thenewstack.io\/llm-d-cncf-kubernetes-inference\/)\n\nMar 24th 2026 8:20am, by   Steven J. Vaughan-Nichols\n\n[Why WebAssembly won't replace Kubernetes but makes Helm more secure](https:\/\/thenewstack.io\/helm-webassembly-kubernetes-security\/)\n\nMar 21st 2026 8:45am, by   B. Cameron Gain\n\n[Solo.io launches agentevals to solve agentic AI's \"biggest unsolved problem\"](https:\/\/thenewstack.io\/soloio-agentevals-evaluates-ai-agents\/)\n\nMar 28th 2026 6:00am, by   Steven J. Vaughan-Nichols\n\n[From pillars to platform: How open observability data is changing the industry](https:\/\/thenewstack.io\/open-observability-ai-platforms\/)\n\nMar 20th 2026 6:00am, by   Ted Young\n\n[Sampling: the philosopher's stone of distributed tracing](https:\/\/thenewstack.io\/distributed-tracing-sampling-opentelemetry\/)\n\nMar 19th 2026 8:00am, by   Michele Mancioppi\n\n[Why your observability bill keeps growing (and it's not your vendor's fault)](https:\/\/thenewstack.io\/why-observability-bills-grow\/)\n\nMar 18th 2026 4:00am, by   Juraci Paixão Kröhling\n\n[Why agentic AI stalls in production — and how a control plane fixes it](https:\/\/thenewstack.io\/agentic-ai-control-plane-production\/)\n\nMar 17th 2026 6:00am, by   TNS Staff\n\n[Edge-forward: Akamai eyes sweet spot between centralized & decentralized AI inference](https:\/\/thenewstack.io\/akamai-edge-ai-inference\/)\n\nApr 1st 2026 7:00am, by   Adrian Bridgwater\n\n[The operational gap is real, and it's getting wider](https:\/\/thenewstack.io\/closing-cloud-operational-gap\/)\n\nMar 26th 2026 8:00am, by   Yevgeny Pats\n\n[HPE's AI agents cut root cause analysis time in half](https:\/\/thenewstack.io\/hpes-ai-agents-cut-root-cause-analysis-time-in-half\/)\n\nMar 25th 2026 7:14am, by   Jennifer Riggins\n\n[WebAssembly could solve AI agents' most dangerous security gap](https:\/\/thenewstack.io\/webassembly-sandboxing-ai-agents\/)\n\nMar 24th 2026 9:01am, by   B. Cameron Gain\n\n[Kubernetes co-founder Brendan Burns: AI-generated code will become as invisible as assembly](https:\/\/thenewstack.io\/ai-generated-code-invisible\/)\n\nMar 24th 2026 7:20am, by   Frederic Lardinois\n\n[How to solve the AI paradox in software development with intelligent orchestration](https:\/\/thenewstack.io\/solve-ai-paradox-orchestration\/)\n\nMar 31st 2026 12:14pm, by   Manav Khurana\n\n[How platform teams are eliminating a \\$43,800 \"hidden tax\" on Kubernetes infrastructure](https:\/\/thenewstack.io\/virtual-clusters-kubernetes-cost-isolation\/)\n\nMar 28th 2026 4:09pm, by   Janakiram MSV\n\n[The operational gap is real, and it's getting wider](https:\/\/thenewstack.io\/closing-cloud-operational-gap\/)\n\nMar 26th 2026 8:00am, by   Yevgeny Pats\n\n[Enterprise dev teams are about to hit a wall. And CI pipelines can't save them.](https:\/\/thenewstack.io\/ai-agent-validation-bottleneck\/)\n\nMar 26th 2026 7:00am, by   Anirudh Ramanathan\n\n[Your Kubernetes isn't ready for AI workloads, and drift is the reason](https:\/\/thenewstack.io\/ai-workloads-kubernetes-infrastructure-drift\/)\n\nMar 25th 2026 8:43am, by   TNS Staff\n\n[C++](https:\/\/thenewstack.io\/c\/)   [Developer tools](https:\/\/thenewstack.io\/developer-tools\/)   [Go](https:\/\/thenewstack.io\/go\/)   [Java](https:\/\/thenewstack.io\/java\/)   [JavaScript](https:\/\/thenewstack.io\/javascript\/)   [Programming Languages](https:\/\/thenewstack.io\/programming-languages\/)   [Python](https:\/\/thenewstack.io\/python\/)   [Rust](https:\/\/thenewstack.io\/rust\/)   [TypeScript](https:\/\/thenewstack.io\/typescript\/)\n\n[Open source USearch library jumpstarts ScyllaDB vector search](https:\/\/thenewstack.io\/open-source-usearch-library-jumpstarts-scylladb-vector-search\/)\n\nFeb 5th 2026 12:00pm, by   Jelani Harper\n\n[AWS WAF vs. Google Cloud Armor: A Multicloud Security Showdown](https:\/\/thenewstack.io\/aws-waf-vs-google-cloud-armor-a-multicloud-security-showdown\/)\n\nNov 25th 2025 10:00am, by   Advait Patel\n\n[Goodbye Dashboards: Agents Deliver Answers, Not Just Reports](https:\/\/thenewstack.io\/goodbye-dashboards-agents-deliver-answers-not-just-reports\/)\n\nNov 23rd 2025 9:00am, by   Ketan Karkhanis\n\n[Rust vs. C++: a Modern Take on Performance and Safety](https:\/\/thenewstack.io\/rust-vs-c-a-modern-take-on-performance-and-safety\/)\n\nOct 22nd 2025 2:00pm, by   Zziwa Raymond Ian\n\n[Building a Real-Time System Monitor in Rust Terminal](https:\/\/thenewstack.io\/building-a-real-time-system-monitor-in-rust-terminal\/)\n\nOct 15th 2025 7:05am, by   Tinega Onchari\n\n[How to integrate VS Code with Ollama for local AI assistance](https:\/\/thenewstack.io\/how-to-integrate-vs-code-with-ollama-for-local-ai-assistance\/)\n\nApr 1st 2026 8:00am, by   Jack Wallen\n\n[JetBrains: AI agents are about to repeat the cloud ROI crisis](https:\/\/thenewstack.io\/jetbrains-central-ai-agents\/)\n\nMar 31st 2026 4:02pm, by   Darryl K. Taft\n\n[Claude Code users say they’re hitting usage limits faster than normal](https:\/\/thenewstack.io\/claude-code-usage-limits\/)\n\nMar 31st 2026 2:30pm, by   Meredith Shubel\n\n[OpenAI's Codex gets plugins](https:\/\/thenewstack.io\/openais-codex-gets-plugins\/)\n\nMar 27th 2026 8:20am, by   Frederic Lardinois\n\n[GitHub will train AI models on your Copilot data — and share it with Microsoft](https:\/\/thenewstack.io\/github-copilot-interaction-data\/)\n\nMar 27th 2026 6:37am, by   Meredith Shubel\n\n[Go Experts: 'I Don't Want to Maintain AI-Generated Code'](https:\/\/thenewstack.io\/go-experts-i-dont-want-to-maintain-ai-generated-code\/)\n\nSep 28th 2025 6:00am, by   David Cassel\n\n[How To Run Kubernetes Commands in Go: Steps and Best Practices](https:\/\/thenewstack.io\/how-to-run-kubernetes-commands-in-go-steps-and-best-practices\/)\n\nJun 27th 2025 8:00am, by   Sunny Yadav\n\n[Prepare Your Mac for Go Development](https:\/\/thenewstack.io\/prepare-your-mac-for-go-development\/)\n\nApr 12th 2025 7:00am, by   Damon M. Garn\n\n[Pagoda: A Web Development Starter Kit for Go Programmers](https:\/\/thenewstack.io\/pagoda-a-web-development-starter-kit-for-go-programmers\/)\n\nMar 19th 2025 6:10am, by   Loraine Lawson\n\n[Microsoft TypeScript Devs Explain Why They Chose Go Over Rust, C\\#](https:\/\/thenewstack.io\/microsoft-typescript-devs-explain-why-they-chose-go-over-rust-c\/)\n\nMar 18th 2025 7:00am, by   David Cassel\n\n[Java 26 lands without an LTS badge. Here's why developers should care anyway.](https:\/\/thenewstack.io\/java-26-performance-ai\/)\n\nMar 18th 2026 9:35am, by   Darryl K. Taft\n\n[62% of enterprises now use Java to power AI apps](https:\/\/thenewstack.io\/2026-java-ai-apps\/)\n\nFeb 10th 2026 12:58pm, by   Darryl K. Taft\n\n[BellSoft bets Java expertise can beat hardened container wave](https:\/\/thenewstack.io\/bellsoft-bets-java-expertise-can-beat-hardened-container-wave\/)\n\nJan 26th 2026 3:00pm, by   Darryl K. Taft\n\n[Java Developers Get Multiple Paths To Building AI Agents](https:\/\/thenewstack.io\/java-developers-get-multiple-paths-to-building-ai-agents\/)\n\nDec 26th 2025 7:02am, by   Darryl K. Taft\n\n[Your Enterprise AI Strategy Must Start With Java, Not Python](https:\/\/thenewstack.io\/your-enterprise-ai-strategy-must-start-with-java-not-python\/)\n\nDec 22nd 2025 1:00pm, by   Michael Coté\n\n[TypeScript 6.0 RC arrives as a bridge to a faster future](https:\/\/thenewstack.io\/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future\/)\n\nMar 14th 2026 9:00am, by   Darryl K. Taft\n\n[WebAssembly is everywhere. Here's how it works](https:\/\/thenewstack.io\/webassembly-is-everywhere-heres-how-it-works\/)\n\nFeb 25th 2026 11:00am, by   Jessica Wachtel\n\n[Wasm vs. JavaScript: Who wins at a million rows?](https:\/\/thenewstack.io\/wasm-vs-javascript-who-wins-at-a-million-rows\/)\n\nFeb 22nd 2026 6:00am, by   Jessica Wachtel\n\n[Arcjet reaches v1.0, promises stable security for JavaScript apps](https:\/\/thenewstack.io\/arcjet-reaches-v1-0-promises-stable-security-for-javascript-apps\/)\n\nFeb 14th 2026 7:00am, by   Darryl K. Taft\n\n[How WebAssembly and Web Workers prevent UI freezes](https:\/\/thenewstack.io\/how-webassembly-and-web-workers-prevent-ui-freezes\/)\n\nFeb 7th 2026 9:00am, by   Jessica Wachtel\n\n[Will AI force code to evolve or make it extinct?](https:\/\/thenewstack.io\/ai-programming-languages-future\/)\n\nMar 22nd 2026 6:00am, by   David Cassel\n\n[Java 26 lands without an LTS badge. Here's why developers should care anyway.](https:\/\/thenewstack.io\/java-26-performance-ai\/)\n\nMar 18th 2026 9:35am, by   Darryl K. Taft\n\n[TypeScript 6.0 RC arrives as a bridge to a faster future](https:\/\/thenewstack.io\/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future\/)\n\nMar 14th 2026 9:00am, by   Darryl K. Taft\n\n[Nearly half of all companies now use Rust in production, survey finds](https:\/\/thenewstack.io\/rust-enterprise-developers\/)\n\nMar 6th 2026 10:45am, by   Darryl K. Taft\n\n[Statistical language R is making a comeback against Python](https:\/\/thenewstack.io\/statistical-language-r-is-making-a-comeback-against-python\/)\n\nFeb 12th 2026 2:57pm, by   Darryl K. Taft\n\n[OpenAI acquires Astral to bring open source Python developer tools to Codex — but details are still fuzzy](https:\/\/thenewstack.io\/openai-astral-acquisition\/)\n\nMar 20th 2026 7:33am, by   Meredith Shubel\n\n[Python virtual environments: isolation without the chaos](https:\/\/thenewstack.io\/python-virtual-environments-isolation-without-the-chaos\/)\n\nFeb 16th 2026 7:00am, by   Jessica Wachtel\n\n[Statistical language R is making a comeback against Python](https:\/\/thenewstack.io\/statistical-language-r-is-making-a-comeback-against-python\/)\n\nFeb 12th 2026 2:57pm, by   Darryl K. Taft\n\n[Arcjet's Python SDK Embeds Security in Code](https:\/\/thenewstack.io\/arcjets-python-sdk-embeds-security-in-code\/)\n\nJan 16th 2026 2:00pm, by   Darryl K. Taft\n\n[2025: The Year of the Return of the Ada Programming Language?](https:\/\/thenewstack.io\/2025-the-year-of-the-return-of-the-ada-programming-language\/)\n\nJan 14th 2026 4:00pm, by   Darryl K. Taft\n\n[Nearly half of all companies now use Rust in production, survey finds](https:\/\/thenewstack.io\/rust-enterprise-developers\/)\n\nMar 6th 2026 10:45am, by   Darryl K. Taft\n\n[Wasm vs. JavaScript: Who wins at a million rows?](https:\/\/thenewstack.io\/wasm-vs-javascript-who-wins-at-a-million-rows\/)\n\nFeb 22nd 2026 6:00am, by   Jessica Wachtel\n\n[Open source USearch library jumpstarts ScyllaDB vector search](https:\/\/thenewstack.io\/open-source-usearch-library-jumpstarts-scylladb-vector-search\/)\n\nFeb 5th 2026 12:00pm, by   Jelani Harper\n\n[The 'weird' things that happened when Clickhouse replaced C++ with Rust](https:\/\/thenewstack.io\/the-weird-things-that-happened-when-clickhouse-replaced-c-with-rust\/)\n\nFeb 4th 2026 7:26am, by   B. Cameron Gain\n\n[Async Rust: Pinning demystified](https:\/\/thenewstack.io\/async-rust-pinning-demystified\/)\n\nJan 26th 2026 11:00am, by   Anshul Gupta\n\n[TypeScript 6.0 RC arrives as a bridge to a faster future](https:\/\/thenewstack.io\/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future\/)\n\nMar 14th 2026 9:00am, by   Darryl K. Taft\n\n[Mastra empowers web devs to build AI agents in TypeScript](https:\/\/thenewstack.io\/mastra-empowers-web-devs-to-build-ai-agents-in-typescript\/)\n\nJan 28th 2026 11:00am, by   Loraine Lawson\n\n[Inferno Vet Creates Frontend Framework Built With AI in Mind](https:\/\/thenewstack.io\/inferno-vet-creates-frontend-framework-built-with-ai-in-mind\/)\n\nDec 10th 2025 11:00am, by   Loraine Lawson\n\n[JavaScript Utility Library Lodash Changing Governance Model](https:\/\/thenewstack.io\/javascript-utility-library-lodash-changing-governance-model\/)\n\nNov 1st 2025 7:00am, by   Loraine Lawson\n\n[Microsoft TypeScript Devs Explain Why They Chose Go Over Rust, C\\#](https:\/\/thenewstack.io\/microsoft-typescript-devs-explain-why-they-chose-go-over-rust-c\/)\n\nMar 18th 2025 7:00am, by   David Cassel\n\n2025-09-03 10:00:46\n\nHow to Make OpenTelemetry Better in the Browser\n\nsponsor-embrace,sponsored-post-contributed,\n\n[Frontend Development](https:\/\/thenewstack.io\/category\/frontend-development\/)   \/   [JavaScript](https:\/\/thenewstack.io\/category\/javascript\/)   \/   [Observability](https:\/\/thenewstack.io\/category\/observability\/)\n\n# How to Make OpenTelemetry Better in the Browser\nAddressing the OpenTelemetry API’s design might make instrumentation more ergonomic, but just improving isn't enough.\n\nSep 3rd, 2025 10:00am by   [Hazel Weakly](https:\/\/thenewstack.io\/author\/hazel-weakly\/ \"Posts by Hazel Weakly\")\n\n![Featued image for: How to Make OpenTelemetry Better in the Browser](https:\/\/cdn.thenewstack.io\/media\/2025\/09\/e4b442ee-otel-1024x576.jpg)\n\nImage from Zakharchuk on Shutterstock.\n\n[Embrace](https:\/\/embrace.io\/?utm_content=sponsor+disclosure) sponsored this post.\n\n*This is the second of two parts. Read Part 1:*\n\n- *[Why OpenTelemetry Is So Clunky for the Frontend](https:\/\/thenewstack.io\/building-an-ergonomic-opentelemetry-for-javascript\/)*\n\nIn Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with [OpenTelemetry’s model of spans and traces](https:\/\/thenewstack.io\/opentelemetry-challenges-handling-long-running-spans\/). I’ll pick up where I left off by sharing another approach to make [OpenTelemetry](https:\/\/thenewstack.io\/what-is-opentelemetry-the-ultimate-guide\/) more ergonomic for [JavaScript](https:\/\/thenewstack.io\/30-years-of-javascript-10-milestones-that-changed-the-web\/). I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today.\n\nNow, as a reminder of where we left off last time, remember that traces, spans, span events and logs are all built on top of the same underlying primitive. That is, they’re all basically just events.\n\n## Don’t Make Me Think\nIf we accept that OpenTelemetry is just events all the way down, then in theory, all you really have to do is write something like `trace.info()` and pass in an object. That’s it. You can have `trace.info`, `trace.error`, `trace.warn` and so on. Given the ubiquity of logging information, it shouldn’t be terribly surprising that most logging-like APIs are a quite natural interface for instrumentation. It [works perfectly for JavaScript and many other languages](https:\/\/thenewstack.io\/javascript-framework-reality-check-whats-actually-working\/), including those that don’t have the ability to provide metaprogramming-style abstractions, thread-local state or other facilities that make OpenTelemetry’s API more ergonomic.\n\n> While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics.\n\nWhile addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. It’s a huge improvement! But certain additional functions would be really helpful. It’s still challenging to design telemetry and propagate it in a way that’s maximally useful.\n\n[![](https:\/\/cdn.thenewstack.io\/media\/2024\/06\/db93b5b0-embrace_logo.svg)](https:\/\/embrace.io\/?utm_content=sponsor+module)\n\nEmbrace is the user-focused observability platform that ties technical performance to end-user impact. Powered by OpenTelemetry, Embrace provides real user monitoring for mobile and web, so engineering teams can resolve issues faster, improve performance, and deliver exceptional digital experiences.\n\nLearn More\n\nThe latest from Embrace\n\nTaking inspiration from other types of instrumentation can give us some ideas of what might be useful here: What if there were a function to add metadata to the root span, regardless of where it is? Implementing this function would be tricky because span immutability is deeply central to the OpenTelemetry API, and violating that would break other things.\n\nHowever, another way to approach that would be durable reference values to sets of attributes, which could then be mutable. That would also potentially massively cut down on network bandwidth.\n\nTRENDING STORIES\n\nGoing further into the inspiration and ideas: What if there was a function to add a new span, but only if a parent span didn’t already exist, or otherwise attach things to the existing span? What if there were a function to take data and add it to every child span, maybe even recursively? What if there were a way to write instrumentation for a single function, but have that instrumentation remain useful when that function is called in a loop? And how could you write all of this without having to create custom processors or custom code to glue everything together in a way that makes sense for your use case?\n\n## Imagining the Future\nThis brings up a fascinating design space for me: If I were to look far into the future and imagine what telemetry could look like, what might be possible?\n\nLet’s take a step into this hypothetical future and imagine: What if the instrumentation library didn’t really exist in the traditional sense, and the code you were writing was actually going to be generated on the fly and rewritten by the compiler? You could use this to make instrumentation code very lightweight and minimal, essentially being custom-built for your application at compile time. You could use the compiler’s information to insert code structure automatically, add lifetime annotations, control flow information, call stack data and maybe even rewrite the telemetry to make more sense for your application’s needs.\n\nThis could facilitate very advanced instrumentation rewriting, minimization and compression as well; imagine a source map-style construct where you send binary pointers to certain common sets of data. You could even imagine normalizing or denormalizing telemetry automatically. Or enabling code to be written for both streaming and batch use cases without code changes. Collectors could roll and unroll telemetry for you, collapse certain pieces of data or even completely rewrite the telemetry tree as needed.\n\nBrowsers and language runtimes could also improve existing limitations by ensuring proper thread-local storage support, context propagation and support for context propagation inside async-like scopes.\n\n> I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment.\n\nThe ability to propagate information in a “magical” metadata object could also be a huge facilitator for building these types of structures, which could be thought of as similar to the reference of metadata idea I brought up earlier. If the language runtimes included explicit instrumentation support as well, then that instrumentation could be written in a heavily optimized manner, which would enable garbage-collected languages to benefit from low-to-zero overhead instrumentation. I find this exciting because it is an actual goal of the OpenTelemetry project, so the potential isn’t out of reach, but it’ll take a lot of coordination.\n\nIn addition, I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. Then you wouldn’t blow up everything with verbose debugging data when deploying to remote servers, but when debugging something locally, you could easily go all the way down to the system call level or even inspect the hardware to get extremely granular views of every interface, no matter how highly abstracted.\n\nJust because a language is high-level doesn’t mean you shouldn’t be able to examine the details when you need or want to. I think we could build languages in the future that allow this ergonomically, letting you instrument code for production while getting rich instrumentation for development, without having to instrument the system twice. Luckily, much of what is described here is an explicit outcome of the upcoming [OpenTelemetry Profiling signal](https:\/\/github.com\/open-telemetry\/opentelemetry-specification\/blob\/main\/oteps\/profiles\/0212-profiling-vision.md), so I hope to see a lot of progress in the next few years.\n\n> Let’s step back and return to reality. The future is fun to think about, but what can we start with today?\n\nIf instrumentation were more tightly embedded into languages, then one could also imagine the uniform integration of other metadata, such as: debugging information, performance profiling, feature flags, marketing data, security events and experimentation data. Instead of each platform building its own SDKs and needing their own implementations, they could use instrumentation features built deeper into the language runtime itself. You could instrument once and feed that data into various platforms — from [observability and monitoring](https:\/\/thenewstack.io\/monitoring-vs-observability-whats-the-difference\/ \"observability and monitoring\") to security and experimentation — all using the same code.\n\nI like to imagine that future as being one where cross-functional collaboration is more accessible and where understanding the complex system being built becomes a truly company-wide endeavor. I’d love to see that happen.\n\n## Getting to Better\nAll of that starry-eyed and sparkly future musing is great, but we might not realistically see those types of changes for years or even decades. It’d also require a lot of coordination, and it’s not clear whether the communities involved even want this to happen. So let’s step back and return to reality. The future is fun to think about, but what can we start with today?\n\nHere’s my thinking: Since events already exist in OpenTelemetry, and since almost everything is events under the hood, we could build support for “just sending events” as an OpenTelemetry specification — think of it as an alternative representation of spans, traces, logs and span events. This would give us a ton of freedom to write whatever library SDKs are needed for a language while retaining full compatibility with vendors. We’re pretty close to being able to do this today, as all it would require would be a modified SDK implementation and a modified stateful OTel Collector. If those two things happened, vendor compatibility would stay the same, and we’d get to experiment with what an event-based representation could look like.\n\nSome observability vendors are already adopting this telemetry flexibility mindset in their products, particularly those involved in the mobile space. One great example of that is [Embrace’s User Journeys](https:\/\/embrace.io\/blog\/user-journeys-walkthrough\/?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) functionality, where you can create custom user flows from existing telemetry you’re already collecting without having to restructure your code. If you’re interested in learning more, you can check out their [upcoming live webinar](https:\/\/get.embrace.io\/user-journeys-webinar?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) on Sept. 16 at 10 a.m. PT\/1 p.m. ET.\n\nAn event-based representation of telemetry data would also facilitate interoperating between traces, spans, logs and span events. It would also allow us to more easily migrate from logs to traces using the same code. This doesn’t mean that I think we’re going to get rid of the current SDK, however. It’s very useful for the backend and also represents a well-done “pay now” API where the client does some more work to handle the stateful nature of telemetry and, in exchange, the collector can be stateless. That means it’s very easy for vendors to be OpenTelemetry-compatible.\n\nI can easily see a future in which people choose between the “pay now” model, where state complexity lives on the client, versus a “pay later” model, where state complexity is in the collector, depending on what makes sense for their environment. High-volume microservices likely benefit from a “pay now” model, and the frontend works best with a “pay later” model.\n\nPutting the two together and being able to tie it all into a coherent context would unlock the next generation of understanding our systems. I can already see bits of this starting to happen, and it makes me really excited for the future of OpenTelemetry in the browser.\n\nI’ve mentioned in other blog posts that the [Cloud Native Computing Foundation (CNCF)](https:\/\/cncf.io\/?utm_content=inline+mention) has a new dedicated Browser Special Interest Group (SIG) for it, which is actively working on improving browser support. I think that is going to create fascinating developments, and I truly look forward to seeing what it becomes one day. If you’d like to learn more about what the Browser SIG is working on, check out this [on-demand webinar](https:\/\/get.embrace.io\/web-otel-panel-typ?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js).\n\nCreated with Sketch.\n\n[![](https:\/\/cdn.thenewstack.io\/media\/2024\/10\/58af1826-cropped-06daf154-screenshot-2024-10-02-at-10.13.52%E2%80%AFam.png) Hazel Weakly spends her days building out teams of humans as well as the infrastructure, systems, automation and tooling to make life better for others. She’s worked at a variety of companies, across a wide range of tech and knows... Read more from Hazel Weakly](https:\/\/thenewstack.io\/author\/hazel-weakly\/)\n\n[Embrace](https:\/\/embrace.io\/?utm_content=sponsor+disclosure) sponsored this post.\n\nSHARE THIS STORY\n\nTRENDING STORIES\n\nSHARE THIS STORY\n\nTRENDING STORIES\n\nTNS DAILY NEWSLETTER Receive a free roundup of the most recent TNS articles in your inbox each day.\n\nSUBSCRIBE\n\nThe New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our [Terms of Use](https:\/\/thenewstack.io\/terms-of-use\/) and [Privacy Policy](https:\/\/thenewstack.io\/privacy-policy\/).\n\nARCHITECTURE\n\n[Cloud Native Ecosystem](https:\/\/thenewstack.io\/cloud-native\/)   [Containers](https:\/\/thenewstack.io\/containers\/)   [Databases](https:\/\/thenewstack.io\/databases\/)   [Edge Computing](https:\/\/thenewstack.io\/edge-computing\/)   [Infrastructure as Code](https:\/\/thenewstack.io\/infrastructure-as-code\/)   [Linux](https:\/\/thenewstack.io\/linux\/)   [Microservices](https:\/\/thenewstack.io\/microservices\/)   [Open Source](https:\/\/thenewstack.io\/open-source\/)   [Networking](https:\/\/thenewstack.io\/networking\/)   [Storage](https:\/\/thenewstack.io\/storage\/)\n\nENGINEERING\n\n[AI](https:\/\/thenewstack.io\/ai\/)   [AI Engineering](https:\/\/thenewstack.io\/ai-engineering\/)   [API Management](https:\/\/thenewstack.io\/api-management\/)   [Backend development](https:\/\/thenewstack.io\/backend-development\/)   [Data](https:\/\/thenewstack.io\/data\/)   [Frontend Development](https:\/\/thenewstack.io\/frontend-development\/)   [Large Language Models](https:\/\/thenewstack.io\/llm\/)   [Security](https:\/\/thenewstack.io\/security\/)   [Software Development](https:\/\/thenewstack.io\/software-development\/)   [WebAssembly](https:\/\/thenewstack.io\/webassembly\/)\n\nOPERATIONS\n\n[AI Operations](https:\/\/thenewstack.io\/ai-operations\/)   [CI\/CD](https:\/\/thenewstack.io\/ci-cd\/)   [Cloud Services](https:\/\/thenewstack.io\/cloud-services\/)   [DevOps](https:\/\/thenewstack.io\/devops\/)   [Kubernetes](https:\/\/thenewstack.io\/kubernetes\/)   [Observability](https:\/\/thenewstack.io\/observability\/)   [Operations](https:\/\/thenewstack.io\/operations\/)   [Platform Engineering](https:\/\/thenewstack.io\/platform-engineering\/)\n\nCHANNELS\n\n[Podcasts](https:\/\/thenewstack.io\/podcasts\/)   [Ebooks](https:\/\/thenewstack.io\/ebooks\/)   [Events](https:\/\/thenewstack.io\/events\/)   [Webinars](https:\/\/thenewstack.io\/webinars\/)   [Newsletter](https:\/\/thenewstack.io\/newsletter\/)   [TNS RSS Feeds](https:\/\/thenewstack.io\/rss-feeds\/)\n\nTHE NEW STACK\n\n[About \/ Contact](https:\/\/thenewstack.io\/about-and-contact-info\/)   [Sponsors](https:\/\/thenewstack.io\/sponsors\/)   [Advertise With Us](https:\/\/thenewstack.io\/sponsorship\/)   [Contributions](https:\/\/thenewstack.io\/contributions\/)\n\n[roadmap.sh Community created roadmaps, articles, resources and journeys for developers to help you choose your path and grow in your career.](https:\/\/roadmap.sh\/?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer)\n\n[Frontend Developer Roadmap](https:\/\/roadmap.sh\/frontend?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer)\n\n[Backend Developer Roadmap](https:\/\/roadmap.sh\/backend?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer)\n\n[Devops Roadmap](https:\/\/roadmap.sh\/devops?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer)\n\n© The New Stack 2026\n\n[Disclosures](https:\/\/thenewstack.io\/disclosure-guidelines\/) [Terms of Use](https:\/\/thenewstack.io\/terms-of-use\/) [Advertising Terms & Conditions](https:\/\/thenewstack.io\/advertising-terms-conditions\/) [Privacy Policy](https:\/\/thenewstack.io\/privacy-policy\/) [Cookie Policy](https:\/\/thenewstack.io\/cookie-policy\/)\n\nFOLLOW TNS\n\n![](https:\/\/www.facebook.com\/tr?id=1244424359562950&ev=PageView&noscript=1)\n\n![](https:\/\/px.ads.linkedin.com\/collect\/?pid=4664394&fmt=gif)","attrs_readable_markdown":"*This is the second of two parts. Read Part 1:*\n\n- *[Why OpenTelemetry Is So Clunky for the Frontend](https:\/\/thenewstack.io\/building-an-ergonomic-opentelemetry-for-javascript\/)*\n\nIn Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with [OpenTelemetry’s model of spans and traces](https:\/\/thenewstack.io\/opentelemetry-challenges-handling-long-running-spans\/). I’ll pick up where I left off by sharing another approach to make [OpenTelemetry](https:\/\/thenewstack.io\/what-is-opentelemetry-the-ultimate-guide\/) more ergonomic for [JavaScript](https:\/\/thenewstack.io\/30-years-of-javascript-10-milestones-that-changed-the-web\/). I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today.\n\nNow, as a reminder of where we left off last time, remember that traces, spans, span events and logs are all built on top of the same underlying primitive. That is, they’re all basically just events.\n\n## Don’t Make Me Think\nIf we accept that OpenTelemetry is just events all the way down, then in theory, all you really have to do is write something like `trace.info()` and pass in an object. That’s it. You can have `trace.info`, `trace.error`, `trace.warn` and so on. Given the ubiquity of logging information, it shouldn’t be terribly surprising that most logging-like APIs are a quite natural interface for instrumentation. It [works perfectly for JavaScript and many other languages](https:\/\/thenewstack.io\/javascript-framework-reality-check-whats-actually-working\/), including those that don’t have the ability to provide metaprogramming-style abstractions, thread-local state or other facilities that make OpenTelemetry’s API more ergonomic.\n\n> While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics.\n\nWhile addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. It’s a huge improvement! But certain additional functions would be really helpful. It’s still challenging to design telemetry and propagate it in a way that’s maximally useful.\n\nTaking inspiration from other types of instrumentation can give us some ideas of what might be useful here: What if there were a function to add metadata to the root span, regardless of where it is? Implementing this function would be tricky because span immutability is deeply central to the OpenTelemetry API, and violating that would break other things.\n\nHowever, another way to approach that would be durable reference values to sets of attributes, which could then be mutable. That would also potentially massively cut down on network bandwidth.\n\nTRENDING STORIES\n\nGoing further into the inspiration and ideas: What if there was a function to add a new span, but only if a parent span didn’t already exist, or otherwise attach things to the existing span? What if there were a function to take data and add it to every child span, maybe even recursively? What if there were a way to write instrumentation for a single function, but have that instrumentation remain useful when that function is called in a loop? And how could you write all of this without having to create custom processors or custom code to glue everything together in a way that makes sense for your use case?\n\n## Imagining the Future\nThis brings up a fascinating design space for me: If I were to look far into the future and imagine what telemetry could look like, what might be possible?\n\nLet’s take a step into this hypothetical future and imagine: What if the instrumentation library didn’t really exist in the traditional sense, and the code you were writing was actually going to be generated on the fly and rewritten by the compiler? You could use this to make instrumentation code very lightweight and minimal, essentially being custom-built for your application at compile time. You could use the compiler’s information to insert code structure automatically, add lifetime annotations, control flow information, call stack data and maybe even rewrite the telemetry to make more sense for your application’s needs.\n\nThis could facilitate very advanced instrumentation rewriting, minimization and compression as well; imagine a source map-style construct where you send binary pointers to certain common sets of data. You could even imagine normalizing or denormalizing telemetry automatically. Or enabling code to be written for both streaming and batch use cases without code changes. Collectors could roll and unroll telemetry for you, collapse certain pieces of data or even completely rewrite the telemetry tree as needed.\n\nBrowsers and language runtimes could also improve existing limitations by ensuring proper thread-local storage support, context propagation and support for context propagation inside async-like scopes.\n\n> I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment.\n\nThe ability to propagate information in a “magical” metadata object could also be a huge facilitator for building these types of structures, which could be thought of as similar to the reference of metadata idea I brought up earlier. If the language runtimes included explicit instrumentation support as well, then that instrumentation could be written in a heavily optimized manner, which would enable garbage-collected languages to benefit from low-to-zero overhead instrumentation. I find this exciting because it is an actual goal of the OpenTelemetry project, so the potential isn’t out of reach, but it’ll take a lot of coordination.\n\nIn addition, I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. Then you wouldn’t blow up everything with verbose debugging data when deploying to remote servers, but when debugging something locally, you could easily go all the way down to the system call level or even inspect the hardware to get extremely granular views of every interface, no matter how highly abstracted.\n\nJust because a language is high-level doesn’t mean you shouldn’t be able to examine the details when you need or want to. I think we could build languages in the future that allow this ergonomically, letting you instrument code for production while getting rich instrumentation for development, without having to instrument the system twice. Luckily, much of what is described here is an explicit outcome of the upcoming [OpenTelemetry Profiling signal](https:\/\/github.com\/open-telemetry\/opentelemetry-specification\/blob\/main\/oteps\/profiles\/0212-profiling-vision.md), so I hope to see a lot of progress in the next few years.\n\n> Let’s step back and return to reality. The future is fun to think about, but what can we start with today?\n\nIf instrumentation were more tightly embedded into languages, then one could also imagine the uniform integration of other metadata, such as: debugging information, performance profiling, feature flags, marketing data, security events and experimentation data. Instead of each platform building its own SDKs and needing their own implementations, they could use instrumentation features built deeper into the language runtime itself. You could instrument once and feed that data into various platforms — from [observability and monitoring](https:\/\/thenewstack.io\/monitoring-vs-observability-whats-the-difference\/ \"observability and monitoring\") to security and experimentation — all using the same code.\n\nI like to imagine that future as being one where cross-functional collaboration is more accessible and where understanding the complex system being built becomes a truly company-wide endeavor. I’d love to see that happen.\n\n## Getting to Better\nAll of that starry-eyed and sparkly future musing is great, but we might not realistically see those types of changes for years or even decades. It’d also require a lot of coordination, and it’s not clear whether the communities involved even want this to happen. So let’s step back and return to reality. The future is fun to think about, but what can we start with today?\n\nHere’s my thinking: Since events already exist in OpenTelemetry, and since almost everything is events under the hood, we could build support for “just sending events” as an OpenTelemetry specification — think of it as an alternative representation of spans, traces, logs and span events. This would give us a ton of freedom to write whatever library SDKs are needed for a language while retaining full compatibility with vendors. We’re pretty close to being able to do this today, as all it would require would be a modified SDK implementation and a modified stateful OTel Collector. If those two things happened, vendor compatibility would stay the same, and we’d get to experiment with what an event-based representation could look like.\n\nSome observability vendors are already adopting this telemetry flexibility mindset in their products, particularly those involved in the mobile space. One great example of that is [Embrace’s User Journeys](https:\/\/embrace.io\/blog\/user-journeys-walkthrough\/?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) functionality, where you can create custom user flows from existing telemetry you’re already collecting without having to restructure your code. If you’re interested in learning more, you can check out their [upcoming live webinar](https:\/\/get.embrace.io\/user-journeys-webinar?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) on Sept. 16 at 10 a.m. PT\/1 p.m. ET.\n\nAn event-based representation of telemetry data would also facilitate interoperating between traces, spans, logs and span events. It would also allow us to more easily migrate from logs to traces using the same code. This doesn’t mean that I think we’re going to get rid of the current SDK, however. It’s very useful for the backend and also represents a well-done “pay now” API where the client does some more work to handle the stateful nature of telemetry and, in exchange, the collector can be stateless. That means it’s very easy for vendors to be OpenTelemetry-compatible.\n\nI can easily see a future in which people choose between the “pay now” model, where state complexity lives on the client, versus a “pay later” model, where state complexity is in the collector, depending on what makes sense for their environment. High-volume microservices likely benefit from a “pay now” model, and the frontend works best with a “pay later” model.\n\nPutting the two together and being able to tie it all into a coherent context would unlock the next generation of understanding our systems. I can already see bits of this starting to happen, and it makes me really excited for the future of OpenTelemetry in the browser.\n\nI’ve mentioned in other blog posts that the [Cloud Native Computing Foundation (CNCF)](https:\/\/cncf.io\/?utm_content=inline+mention) has a new dedicated Browser Special Interest Group (SIG) for it, which is actively working on improving browser support. I think that is going to create fascinating developments, and I truly look forward to seeing what it becomes one day. If you’d like to learn more about what the Browser SIG is working on, check out this [on-demand webinar](https:\/\/get.embrace.io\/web-otel-panel-typ?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js).\n\nCreated with Sketch.","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

4 days ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0.1 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/
Last Crawled	2026-04-08 09:28:47 (4 days ago)
First Indexed	2025-09-04 12:04:04 (7 months ago)
HTTP Status Code	200
Meta Title	How to Make OpenTelemetry Better in the Browser - The New Stack
Meta Description	Addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, but just improving isn't enough.
Meta Canonical	null
Boilerpipe Text	This is the second of two parts. Read Part 1: Why OpenTelemetry Is So Clunky for the Frontend In Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with OpenTelemetry’s model of spans and traces . I’ll pick up where I left off by sharing another approach to make OpenTelemetry more ergonomic for JavaScript . I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today. Now, as a reminder of where we left off last time, remember that traces, spans, span events and logs are all built on top of the same underlying primitive. That is, they’re all basically just events. Don’t Make Me Think If we accept that OpenTelemetry is just events all the way down, then in theory, all you really have to do is write something like trace.info() and pass in an object. That’s it. You can have trace.info , trace.error , trace.warn and so on. Given the ubiquity of logging information, it shouldn’t be terribly surprising that most logging-like APIs are a quite natural interface for instrumentation. It works perfectly for JavaScript and many other languages , including those that don’t have the ability to provide metaprogramming-style abstractions, thread-local state or other facilities that make OpenTelemetry’s API more ergonomic. While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. It’s a huge improvement! But certain additional functions would be really helpful. It’s still challenging to design telemetry and propagate it in a way that’s maximally useful. Taking inspiration from other types of instrumentation can give us some ideas of what might be useful here: What if there were a function to add metadata to the root span, regardless of where it is? Implementing this function would be tricky because span immutability is deeply central to the OpenTelemetry API, and violating that would break other things. However, another way to approach that would be durable reference values to sets of attributes, which could then be mutable. That would also potentially massively cut down on network bandwidth. TRENDING STORIES Going further into the inspiration and ideas: What if there was a function to add a new span, but only if a parent span didn’t already exist, or otherwise attach things to the existing span? What if there were a function to take data and add it to every child span, maybe even recursively? What if there were a way to write instrumentation for a single function, but have that instrumentation remain useful when that function is called in a loop? And how could you write all of this without having to create custom processors or custom code to glue everything together in a way that makes sense for your use case? Imagining the Future This brings up a fascinating design space for me: If I were to look far into the future and imagine what telemetry could look like, what might be possible? Let’s take a step into this hypothetical future and imagine: What if the instrumentation library didn’t really exist in the traditional sense, and the code you were writing was actually going to be generated on the fly and rewritten by the compiler? You could use this to make instrumentation code very lightweight and minimal, essentially being custom-built for your application at compile time. You could use the compiler’s information to insert code structure automatically, add lifetime annotations, control flow information, call stack data and maybe even rewrite the telemetry to make more sense for your application’s needs. This could facilitate very advanced instrumentation rewriting, minimization and compression as well; imagine a source map-style construct where you send binary pointers to certain common sets of data. You could even imagine normalizing or denormalizing telemetry automatically. Or enabling code to be written for both streaming and batch use cases without code changes. Collectors could roll and unroll telemetry for you, collapse certain pieces of data or even completely rewrite the telemetry tree as needed. Browsers and language runtimes could also improve existing limitations by ensuring proper thread-local storage support, context propagation and support for context propagation inside async-like scopes. I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. The ability to propagate information in a “magical” metadata object could also be a huge facilitator for building these types of structures, which could be thought of as similar to the reference of metadata idea I brought up earlier. If the language runtimes included explicit instrumentation support as well, then that instrumentation could be written in a heavily optimized manner, which would enable garbage-collected languages to benefit from low-to-zero overhead instrumentation. I find this exciting because it is an actual goal of the OpenTelemetry project, so the potential isn’t out of reach, but it’ll take a lot of coordination. In addition, I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. Then you wouldn’t blow up everything with verbose debugging data when deploying to remote servers, but when debugging something locally, you could easily go all the way down to the system call level or even inspect the hardware to get extremely granular views of every interface, no matter how highly abstracted. Just because a language is high-level doesn’t mean you shouldn’t be able to examine the details when you need or want to. I think we could build languages in the future that allow this ergonomically, letting you instrument code for production while getting rich instrumentation for development, without having to instrument the system twice. Luckily, much of what is described here is an explicit outcome of the upcoming OpenTelemetry Profiling signal , so I hope to see a lot of progress in the next few years. Let’s step back and return to reality. The future is fun to think about, but what can we start with today? If instrumentation were more tightly embedded into languages, then one could also imagine the uniform integration of other metadata, such as: debugging information, performance profiling, feature flags, marketing data, security events and experimentation data. Instead of each platform building its own SDKs and needing their own implementations, they could use instrumentation features built deeper into the language runtime itself. You could instrument once and feed that data into various platforms — from observability and monitoring to security and experimentation — all using the same code. I like to imagine that future as being one where cross-functional collaboration is more accessible and where understanding the complex system being built becomes a truly company-wide endeavor. I’d love to see that happen. Getting to Better All of that starry-eyed and sparkly future musing is great, but we might not realistically see those types of changes for years or even decades. It’d also require a lot of coordination, and it’s not clear whether the communities involved even want this to happen. So let’s step back and return to reality. The future is fun to think about, but what can we start with today? Here’s my thinking: Since events already exist in OpenTelemetry, and since almost everything is events under the hood, we could build support for “just sending events” as an OpenTelemetry specification — think of it as an alternative representation of spans, traces, logs and span events. This would give us a ton of freedom to write whatever library SDKs are needed for a language while retaining full compatibility with vendors. We’re pretty close to being able to do this today, as all it would require would be a modified SDK implementation and a modified stateful OTel Collector. If those two things happened, vendor compatibility would stay the same, and we’d get to experiment with what an event-based representation could look like. Some observability vendors are already adopting this telemetry flexibility mindset in their products, particularly those involved in the mobile space. One great example of that is Embrace’s User Journeys functionality, where you can create custom user flows from existing telemetry you’re already collecting without having to restructure your code. If you’re interested in learning more, you can check out their upcoming live webinar on Sept. 16 at 10 a.m. PT/1 p.m. ET. An event-based representation of telemetry data would also facilitate interoperating between traces, spans, logs and span events. It would also allow us to more easily migrate from logs to traces using the same code. This doesn’t mean that I think we’re going to get rid of the current SDK, however. It’s very useful for the backend and also represents a well-done “pay now” API where the client does some more work to handle the stateful nature of telemetry and, in exchange, the collector can be stateless. That means it’s very easy for vendors to be OpenTelemetry-compatible. I can easily see a future in which people choose between the “pay now” model, where state complexity lives on the client, versus a “pay later” model, where state complexity is in the collector, depending on what makes sense for their environment. High-volume microservices likely benefit from a “pay now” model, and the frontend works best with a “pay later” model. Putting the two together and being able to tie it all into a coherent context would unlock the next generation of understanding our systems. I can already see bits of this starting to happen, and it makes me really excited for the future of OpenTelemetry in the browser. I’ve mentioned in other blog posts that the Cloud Native Computing Foundation (CNCF) has a new dedicated Browser Special Interest Group (SIG) for it, which is actively working on improving browser support. I think that is going to create fascinating developments, and I truly look forward to seeing what it becomes one day. If you’d like to learn more about what the Browser SIG is working on, check out this on-demand webinar . Group Created with Sketch.
Markdown	TNS OK SUBSCRIBE Join our community of software engineering leaders and aspirational developers. Always stay in-the-know by getting the most important news and exclusive content delivered fresh to your inbox to learn more about at-scale software development. EMAIL ADDRESS REQUIRED SUBSCRIBE RESUBSCRIPTION REQUIRED It seems that you've previously unsubscribed from our newsletter in the past. Click the button below to open the re-subscribe form in a new tab. When you're done, simply close that tab and continue with this form to complete your subscription. RE-SUBSCRIBE The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our [Terms of Use](https://thenewstack.io/terms-of-use/) and [Privacy Policy](https://thenewstack.io/privacy-policy/). Welcome and thank you for joining The New Stack community\! Please answer a few simple questions to help us deliver the news and resources you are interested in. FIRST NAME REQUIRED LAST NAME REQUIRED COMPANY NAME REQUIRED COUNTRY REQUIRED ZIPCODE REQUIRED Great to meet you\! Tell us a bit about your job so we can cover the topics you find most relevant. What is your job level? REQUIRED Which of these most closely describes your job role? REQUIRED How many employees are in the organization you work with? REQUIRED What option best describes the type of organization you work for? REQUIRED Which of the following best describes your organization's primary industry? REQUIRED LINKEDIN PROFILE URL Welcome\! We’re so glad you’re here. You can expect all the best TNS content to arrive Monday through Friday to keep you on top of the news and at the top of your game. What’s next? Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups. Follow TNS on your favorite social media networks. Become a [TNS follower on LinkedIn](https://www.linkedin.com/company/the-new-stack). Check out [the latest featured and trending stories](https://thenewstack.io/) while you wait for your first TNS newsletter. PREV 1 of 2 NEXT VOXPOP As a JavaScript developer, what non-React tools do you use most often? ✓ Angular 0% ✓ Astro 0% ✓ Svelte 0% ✓ Vue.js 0% ✓ Other 0% ✓ I only use React 0% ✓ I don't use JavaScript 0% Thanks for your opinion! Subscribe below to get the final results, published exclusively in our TNS Update newsletter: SUBMIT NEW! Try Stackie AI LOGIN ARCHITECTURE [Cloud Native Ecosystem](https://thenewstack.io/cloud-native/) [Containers](https://thenewstack.io/containers/) [Databases](https://thenewstack.io/databases/) [Edge Computing](https://thenewstack.io/edge-computing/) [Infrastructure as Code](https://thenewstack.io/infrastructure-as-code/) [Linux](https://thenewstack.io/linux/) [Microservices](https://thenewstack.io/microservices/) [Open Source](https://thenewstack.io/open-source/) [Networking](https://thenewstack.io/networking/) [Storage](https://thenewstack.io/storage/) ENGINEERING [AI](https://thenewstack.io/ai/) [AI Engineering](https://thenewstack.io/ai-engineering/) [API Management](https://thenewstack.io/api-management/) [Backend development](https://thenewstack.io/backend-development/) [Data](https://thenewstack.io/data/) [Frontend Development](https://thenewstack.io/frontend-development/) [Large Language Models](https://thenewstack.io/llm/) [Security](https://thenewstack.io/security/) [Software Development](https://thenewstack.io/software-development/) [WebAssembly](https://thenewstack.io/webassembly/) OPERATIONS [AI Operations](https://thenewstack.io/ai-operations/) [CI/CD](https://thenewstack.io/ci-cd/) [Cloud Services](https://thenewstack.io/cloud-services/) [DevOps](https://thenewstack.io/devops/) [Kubernetes](https://thenewstack.io/kubernetes/) [Observability](https://thenewstack.io/observability/) [Operations](https://thenewstack.io/operations/) [Platform Engineering](https://thenewstack.io/platform-engineering/) PROGRAMMING [C++](https://thenewstack.io/c/) [Developer tools](https://thenewstack.io/developer-tools/) [Go](https://thenewstack.io/go/) [Java](https://thenewstack.io/java/) [JavaScript](https://thenewstack.io/javascript/) [Programming Languages](https://thenewstack.io/programming-languages/) [Python](https://thenewstack.io/python/) [Rust](https://thenewstack.io/rust/) [TypeScript](https://thenewstack.io/typescript/) CHANNELS [Podcasts](https://thenewstack.io/podcasts/) [Ebooks](https://thenewstack.io/ebooks/) [Events](https://thenewstack.io/events/) [Webinars](https://thenewstack.io/webinars/) [Newsletter](https://thenewstack.io/newsletter/) [TNS RSS Feeds](https://thenewstack.io/rss-feeds/) THE NEW STACK [About / Contact](https://thenewstack.io/about-and-contact-info/) [Sponsors](https://thenewstack.io/sponsors/) [Advertise With Us](https://thenewstack.io/sponsorship/) [Contributions](https://thenewstack.io/contributions/) [PODCASTS](https://thenewstack.io/podcasts/) [EBOOKS](https://thenewstack.io/ebooks/) [EVENTS](https://thenewstack.io/events/) [WEBINARS](https://thenewstack.io/webinars/) [NEWSLETTER](https://thenewstack.io/newsletter/) [CONTRIBUTE](https://thenewstack.io/contributions/) [ARCHITECTURE](https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/) [ENGINEERING](https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/) [OPERATIONS](https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/) [PROGRAMMING](https://thenewstack.io/how-to-make-opentelemetry-better-in-the-browser/) [Cloud Native Ecosystem](https://thenewstack.io/cloud-native/) [Containers](https://thenewstack.io/containers/) [Databases](https://thenewstack.io/databases/) [Edge Computing](https://thenewstack.io/edge-computing/) [Infrastructure as Code](https://thenewstack.io/infrastructure-as-code/) [Linux](https://thenewstack.io/linux/) [Microservices](https://thenewstack.io/microservices/) [Open Source](https://thenewstack.io/open-source/) [Networking](https://thenewstack.io/networking/) [Storage](https://thenewstack.io/storage/) [WebAssembly is now outperforming containers at the edge Mar 29th 2026 9:00am, by B. Cameron Gain](https://thenewstack.io/webassembly-component-model-future/) [How platform teams are eliminating a \$43,800 "hidden tax" on Kubernetes infrastructure Mar 28th 2026 4:09pm, by Janakiram MSV](https://thenewstack.io/virtual-clusters-kubernetes-cost-isolation/) [Solo.io launches agentevals to solve agentic AI's "biggest unsolved problem" Mar 28th 2026 6:00am, by Steven J. Vaughan-Nichols](https://thenewstack.io/soloio-agentevals-evaluates-ai-agents/) [Why WebAssembly won't replace Kubernetes but makes Helm more secure Mar 21st 2026 8:45am, by B. Cameron Gain](https://thenewstack.io/helm-webassembly-kubernetes-security/) [Why the ‘glorified host’ for AI is exactly the Kubernetes we need Mar 20th 2026 9:00am, by Danielle Cook](https://thenewstack.io/kubernetes-glorified-ai-host/) [Edera spent years calling KVM less secure. Here's why it changed its mind. Mar 25th 2026 2:22pm, by Steven J. Vaughan-Nichols](https://thenewstack.io/edera-adds-kvm-support/) [Minimus aims to solve one of open-source's long-festering problems Mar 24th 2026 3:00am, by Adrian Bridgwater](https://thenewstack.io/minimus-open-source-container-security/) [How to deploy Pi-Hole with Docker and stop ads on every device on your LAN Mar 23rd 2026 7:44am, by Jack Wallen](https://thenewstack.io/pihole-docker-network-adblocking/) [Chainguard has a fix for the open source packages your AI agents keep grabbing Mar 18th 2026 9:24am, by Darryl K. Taft](https://thenewstack.io/chainguard-repository-ai-agents/) [Chainguard thinks most DevOps teams are solving container security the hard way Mar 17th 2026 1:04pm, by Steven J. Vaughan-Nichols](https://thenewstack.io/chainguard-os-packages-containers/) [The reason your pgvector benchmark is lying to you Mar 27th 2026 5:00am, by Naina Ananthaswamy](https://thenewstack.io/why-pgvector-benchmarks-lie/) [Scaling Btrfs to petabytes in production: a 74% cost reduction story Mar 18th 2026 5:00am, by Motiejus Jakštys](https://thenewstack.io/btrfs-petabyte-cost-reduction/) [The “files are all you need” debate misses what's actually happening in agent memory architecture Mar 13th 2026 5:00am, by Mikiko Bazeley](https://thenewstack.io/ai-agent-memory-architecture/) [With GridGain acquisition, MariaDB bets on in-memory computing and Apache Ignite Mar 10th 2026 6:47am, by Paul Sawers](https://thenewstack.io/with-gridgain-acquisition-mariadb-bets-on-in-memory-computing-and-apache-ignite/) [Moving AI apps from prototype to production requires enterprise-grade postgres infrastructure Mar 9th 2026 7:00am, by Meredith Shubel](https://thenewstack.io/ai-prototype-to-production-postgres/) [Edge-forward: Akamai eyes sweet spot between centralized & decentralized AI inference Apr 1st 2026 7:00am, by Adrian Bridgwater](https://thenewstack.io/akamai-edge-ai-inference/) [Developers are coding to a moving target, and nobody knows where AI lands next Mar 3rd 2026 7:33am, by Adrian Bridgwater](https://thenewstack.io/developers-coding-moving-target-ai/) [Cloudflare’s new Markdown support shows how the web is evolving for AI agents Mar 2nd 2026 4:30am, by David Eastman](https://thenewstack.io/intent-engineering-ai-agents/) [React Server Components Vulnerability Found Dec 6th 2025 7:00am, by Loraine Lawson](https://thenewstack.io/react-server-components-vulnerability-found/) [Kubernetes at the Edge: Lessons From GE HealthCare’s Edge Strategy Nov 24th 2025 10:00am, by Vicki Walker](https://thenewstack.io/kubernetes-at-the-edge-lessons-from-ge-healthcares-edge-strategy/) [The operational gap is real, and it's getting wider Mar 26th 2026 8:00am, by Yevgeny Pats](https://thenewstack.io/closing-cloud-operational-gap/) [Why "automated" infrastructure might cost more than you think Feb 24th 2026 4:00am, by Justyn Roberts](https://thenewstack.io/automated-infrastructure-hidden-costs/) [Why 40% of AI projects will be canceled by 2027 (and how to stay in the other 60%) Feb 13th 2026 6:00am, by Alex Drag](https://thenewstack.io/agentic-ai-connectivity-platform/) [Durable Execution: Build reliable software in an unreliable world Feb 2nd 2026 3:23pm, by Charles Humble](https://thenewstack.io/temporal-durable-execution-platform/) [Terraform challenger Formae expands to more clouds Jan 28th 2026 6:00am, by Joab Jackson](https://thenewstack.io/terraform-competitor-formae-expands-to-more-clouds/) [Sparky Linux 9 brings a rolling release to Debian Mar 30th 2026 8:00am, by Jack Wallen](https://thenewstack.io/sparky-linux-9-brings-a-rolling-release-to-debian/) [Edera spent years calling KVM less secure. Here's why it changed its mind. Mar 25th 2026 2:22pm, by Steven J. Vaughan-Nichols](https://thenewstack.io/edera-adds-kvm-support/) [Linux kernel scale is swamping an already-flawed CVE system Mar 20th 2026 4:30am, by Jed Salazar](https://thenewstack.io/linux-kernel-cve-system/) [Scaling Btrfs to petabytes in production: a 74% cost reduction story Mar 18th 2026 5:00am, by Motiejus Jakštys](https://thenewstack.io/btrfs-petabyte-cost-reduction/) [Chainguard thinks most DevOps teams are solving container security the hard way Mar 17th 2026 1:04pm, by Steven J. Vaughan-Nichols](https://thenewstack.io/chainguard-os-packages-containers/) [Tetrate launches open source marketplace to simplify Envoy adoption Mar 11th 2026 10:52am, by Adrian Bridgwater](https://thenewstack.io/tetrate-built-on-envoy/) [OpenTelemetry roadmap: Sampling rates and collector improvements ahead Feb 24th 2026 11:00am, by B. Cameron Gain](https://thenewstack.io/opentelemetry-roadmap-sampling-rates-and-collector-improvements-ahead/) [Merging To Test Is Killing Your Microservices Velocity Dec 16th 2025 7:00am, by Arjun Iyer](https://thenewstack.io/merging-to-test-is-killing-your-microservices-velocity/) [IBM’s Confluent Acquisition Is About Event-Driven AI Dec 11th 2025 6:00am, by Joab Jackson](https://thenewstack.io/ibms-confluent-acquisition-is-about-event-driven-ai/) [Deploy Agentic AI Workflows With Kubernetes and Terraform Nov 26th 2025 9:00am, by Oladimeji Sowole](https://thenewstack.io/deploy-agentic-ai-workflows-with-kubernetes-and-terraform/) [Portkey open-sources its AI gateway after processing 2 trillion tokens a day Mar 31st 2026 3:53pm, by Adrian Bridgwater](https://thenewstack.io/portkey-gateway-open-source/) [Ollama taps Apple’s MLX framework to make local AI models faster on Macs Mar 31st 2026 8:00am, by Paul Sawers](https://thenewstack.io/ollama-taps-apples-mlx/) [96% of codebases rely on open source, and AI slop is putting them at risk Mar 29th 2026 6:00am, by Bill Doerrfeld](https://thenewstack.io/ai-slop-open-source/) [Gitleaks creator returns with Betterleaks, an open source secrets scanner for the agentic era Mar 27th 2026 11:00am, by Paul Sawers](https://thenewstack.io/betterleaks-open-source-secret-scanner/) [How TeamPCP turned Aqua Security's own Trivy scanner into a weapon against millions of developers Mar 27th 2026 10:00am, by Steven J. Vaughan-Nichols](https://thenewstack.io/teampcp-trivy-supply-chain-attack/) [How to deploy Pi-Hole with Docker and stop ads on every device on your LAN Mar 23rd 2026 7:44am, by Jack Wallen](https://thenewstack.io/pihole-docker-network-adblocking/) [Why flat Kubernetes networks fail at scale Mar 20th 2026 7:00am, by Reza Ramezanpour](https://thenewstack.io/kubernetes-network-security-hierarchies/) [GSMA Open Gateway offers developers one API for 300+ mobile networks Mar 4th 2026 10:26am, by Adrian Bridgwater](https://thenewstack.io/gsma-open-gateway-developers/) [How Homepage simplifies monitoring your self-hosted services Feb 6th 2026 8:00am, by Jack Wallen](https://thenewstack.io/how-homepage-simplifies-monitoring-your-self-hosted-services/) [S3 is the new network: Rethinking data architecture for the cloud era Feb 2nd 2026 4:00am, by Max Liu](https://thenewstack.io/tidb-x-open-source-database/) [Scaling Btrfs to petabytes in production: a 74% cost reduction story Mar 18th 2026 5:00am, by Motiejus Jakštys](https://thenewstack.io/btrfs-petabyte-cost-reduction/) [What is KubeVirt and why it’s growing Mar 17th 2026 9:00am, by Tiago Castro](https://thenewstack.io/kubevirt-live-migration-mayastor/) [S3 is the new network: Rethinking data architecture for the cloud era Feb 2nd 2026 4:00am, by Max Liu](https://thenewstack.io/tidb-x-open-source-database/) [Agoda’s secret to 50x scale: Getting the database basics right Jan 28th 2026 7:00am, by Cynthia Dunlop](https://thenewstack.io/agodas-secret-to-50x-scale-getting-the-database-basics-right/) [Chainguard EmeritOSS backs MinIO, other orphaned projects Jan 27th 2026 6:15am, by Steven J. Vaughan-Nichols](https://thenewstack.io/chainguard-emeritoss-backs-minio-other-orphaned-projects/) [AI](https://thenewstack.io/ai/) [AI Engineering](https://thenewstack.io/ai-engineering/) [API Management](https://thenewstack.io/api-management/) [Backend development](https://thenewstack.io/backend-development/) [Data](https://thenewstack.io/data/) [Frontend Development](https://thenewstack.io/frontend-development/) [Large Language Models](https://thenewstack.io/llm/) [Security](https://thenewstack.io/security/) [Software Development](https://thenewstack.io/software-development/) [WebAssembly](https://thenewstack.io/webassembly/) [How to integrate VS Code with Ollama for local AI assistance](https://thenewstack.io/how-to-integrate-vs-code-with-ollama-for-local-ai-assistance/) Apr 1st 2026 8:00am, by [Jack Wallen](https://thenewstack.io/author/jack-wallen/ "Posts by Jack Wallen") [Claude Code users say they’re hitting usage limits faster than normal](https://thenewstack.io/claude-code-usage-limits/) Mar 31st 2026 2:30pm, by [Meredith Shubel](https://thenewstack.io/author/mshubel/ "Posts by Meredith Shubel") [Ollama taps Apple’s MLX framework to make local AI models faster on Macs](https://thenewstack.io/ollama-taps-apples-mlx/) Mar 31st 2026 8:00am, by [Paul Sawers](https://thenewstack.io/author/paul-sawers/ "Posts by Paul Sawers") [Kelsey Hightower at KubeCon 2026: "Everyone is a junior engineer when it comes to AI"](https://thenewstack.io/hightower-ai-open-source-kubecon/) Mar 30th 2026 2:45pm, by [Jennifer Riggins](https://thenewstack.io/author/jennifer-riggins/ "Posts by Jennifer Riggins") [Microsoft's Copilot makes Anthropic's Claude and OpenAI's GPT team up](https://thenewstack.io/microsofts-copilot-llm-team/) Mar 30th 2026 9:00am, by [Frederic Lardinois](https://thenewstack.io/author/frederic-lardinois/ "Posts by Frederic Lardinois") [AI accelerates modernization, but don’t leave human devs behind](https://thenewstack.io/ai-modernization-human-developers/) Mar 31st 2026 12:00pm, by [Matthew Weier O’Phinney](https://thenewstack.io/author/matthew-weier-ophinney/ "Posts by Matthew Weier O’Phinney") [Build it yourself: A data pipeline that trains a real model](https://thenewstack.io/data-pipelines-serve-ai/) Mar 28th 2026 9:00am, by [Jessica Wachtel](https://thenewstack.io/author/jessica-wachtel/ "Posts by Jessica Wachtel") [Why online stores keep showing the wrong products — and why tensors fix it](https://thenewstack.io/tensor-ranking-product-discovery/) Mar 25th 2026 6:00am, by [Tim Young](https://thenewstack.io/author/tim-young/ "Posts by Tim Young") [OpenClaw's biggest security flaw is why Jentic Mini exists](https://thenewstack.io/openclaw-is-a-security-mess-jentic-wants-to-fix-it/) Mar 25th 2026 5:00am, by [Darryl K. Taft](https://thenewstack.io/author/darryl-taft/ "Posts by Darryl K. Taft") [Why most AI projects fail after the demo actually works](https://thenewstack.io/ai-demo-to-production/) Mar 25th 2026 4:00am, by [Oladimeji Sowole](https://thenewstack.io/author/oladimeji-sowole/ "Posts by Oladimeji Sowole") [MCP is everywhere, but don't panic. Here's why your existing APIs still matter.](https://thenewstack.io/api-mcp-agent-integration/) Mar 23rd 2026 5:00am, by [Camille Crowell-Lee](https://thenewstack.io/author/camille-crowell-lee/ "Posts by Camille Crowell-Lee") and [Morgan Fine](https://thenewstack.io/author/morgan-fine/ "Posts by Morgan Fine") [Before you let AI agents loose, you’d better know what they’re capable of](https://thenewstack.io/risk-mitigation-agentic-ai/) Mar 12th 2026 1:22pm, by [Charles Humble](https://thenewstack.io/author/charles-humble/ "Posts by Charles Humble") [GSMA Open Gateway offers developers one API for 300+ mobile networks](https://thenewstack.io/gsma-open-gateway-developers/) Mar 4th 2026 10:26am, by [Adrian Bridgwater](https://thenewstack.io/author/adrian-bridgwater/ "Posts by Adrian Bridgwater") [Your AI strategy is built on layers of API sediment](https://thenewstack.io/ai-strategy-api-sediment/) Feb 17th 2026 9:37am, by [Charles Humble](https://thenewstack.io/author/charles-humble/ "Posts by Charles Humble") [Solving the Problems That Accompany API Sprawl With AI](https://thenewstack.io/solving-the-problems-that-accompany-api-sprawl-with-ai/) Jan 15th 2026 1:00pm, by [Heather Joslyn](https://thenewstack.io/author/hjoslyn/ "Posts by Heather Joslyn") [Backend Development in 2026: What's Changed, What Matters, and What to Learn Next](https://thenewstack.io/introduction-to-backend-development/) Mar 19th 2026 11:37am, by [TNS Staff](https://thenewstack.io/author/tns-staff/ "Posts by TNS Staff") [How To Get DNS Right: A Guide to Common Failure Modes](https://thenewstack.io/how-to-get-dns-right-a-guide-to-common-failure-modes/) Dec 24th 2025 8:00am, by [Sheldon Pereira](https://thenewstack.io/author/sheldon-pereira/ "Posts by Sheldon Pereira") and [Denton Chikura](https://thenewstack.io/author/denton-chikura/ "Posts by Denton Chikura") [Combining Rust and Python for High-Performance AI Systems](https://thenewstack.io/combining-rust-and-python-for-high-performance-ai-systems/) Dec 3rd 2025 1:00pm, by [Zziwa Raymond Ian](https://thenewstack.io/author/zziwa-raymond/ "Posts by Zziwa Raymond Ian") [How MCP Uses Streamable HTTP for Real-Time AI Tool Interaction](https://thenewstack.io/how-mcp-uses-streamable-http-for-real-time-ai-tool-interaction/) Aug 18th 2025 10:34am, by [Janakiram MSV](https://thenewstack.io/author/janakiram/ "Posts by Janakiram MSV") [A Backend for Frontend: Watt for Node.js Simplifies Operations](https://thenewstack.io/a-backend-for-frontend-watt-for-node-js-simplifies-operations/) Aug 14th 2025 6:00am, by [Loraine Lawson](https://thenewstack.io/author/loraine-lawson/ "Posts by Loraine Lawson") [Build it yourself: A data pipeline that trains a real model](https://thenewstack.io/data-pipelines-serve-ai/) Mar 28th 2026 9:00am, by [Jessica Wachtel](https://thenewstack.io/author/jessica-wachtel/ "Posts by Jessica Wachtel") [Fivetran donates its SQLMesh data transformation framework to the Linux Foundation](https://thenewstack.io/fivetran-donates-sqlmesh-lf/) Mar 25th 2026 7:39am, by [Frederic Lardinois](https://thenewstack.io/author/frederic-lardinois/ "Posts by Frederic Lardinois") [Ex-Snowflake engineers say there's a blind spot in data engineering — so they built Tower to fix it](https://thenewstack.io/tower-python-data-pipelines/) Mar 15th 2026 7:00am, by [Paul Sawers](https://thenewstack.io/author/paul-sawers/ "Posts by Paul Sawers") [Why the "bible" of data systems is getting a massive rewrite for 2026](https://thenewstack.io/data-intensive-applications-rewrite-2026/) Mar 4th 2026 5:00am, by [Cynthia Dunlop](https://thenewstack.io/author/cynthiadunlop/ "Posts by Cynthia Dunlop") [How to clone a drive to an image with Clonezilla](https://thenewstack.io/how-to-clone-a-drive-to-an-image-with-clonezilla/) Mar 3rd 2026 1:00pm, by [Jack Wallen](https://thenewstack.io/author/jack-wallen/ "Posts by Jack Wallen") [WebMCP turns any Chrome web page into an MCP server for AI agents](https://thenewstack.io/webmcp-chrome-ai-agents/) Mar 17th 2026 11:50am, by [David Eastman](https://thenewstack.io/author/david-eastman/ "Posts by David Eastman") [Confluent adds A2A support, anomaly detection, and Queues for Kafka in major platform update](https://thenewstack.io/confluent-kafka-a2a-agents/) Mar 3rd 2026 10:21am, by [Jelani Harper](https://thenewstack.io/author/jelani-harper/ "Posts by Jelani Harper") [Google's Chrome browser moves to a two-week release cycle](https://thenewstack.io/chrome-two-week-releases/) Mar 3rd 2026 9:00am, by [Frederic Lardinois](https://thenewstack.io/author/frederic-lardinois/ "Posts by Frederic Lardinois") [Meta gave React its own foundation. But it's not letting go just yet.](https://thenewstack.io/react-foundation-open-source-governance/) Mar 3rd 2026 4:00am, by [Paul Sawers](https://thenewstack.io/author/paul-sawers/ "Posts by Paul Sawers") [The shift left hangover: Why modern platforms are shifting down to cure developer fatigue](https://thenewstack.io/shift-left-hangover-steve-corndell/) Jan 30th 2026 6:22pm, by [Steve Corndell](https://thenewstack.io/author/steve-corndell/ "Posts by Steve Corndell") [Why most AI projects fail after the demo actually works](https://thenewstack.io/ai-demo-to-production/) Mar 25th 2026 4:00am, by [Oladimeji Sowole](https://thenewstack.io/author/oladimeji-sowole/ "Posts by Oladimeji Sowole") [IBM, Red Hat, and Google just donated a Kubernetes blueprint for LLM inference to the CNCF](https://thenewstack.io/llm-d-cncf-kubernetes-inference/) Mar 24th 2026 8:20am, by [Steven J. Vaughan-Nichols](https://thenewstack.io/author/sjvn/ "Posts by Steven J. Vaughan-Nichols") [Andrej Karpathy's 630-line Python script ran 50 experiments overnight without any human input](https://thenewstack.io/karpathy-autonomous-experiment-loop/) Mar 14th 2026 5:00am, by [Janakiram MSV](https://thenewstack.io/author/janakiram/ "Posts by Janakiram MSV") ["Self-healing" IT? HPE research explores how AI-trained models can catch silent infrastructure failures](https://thenewstack.io/hpe-self-healing-ai-infrastructure/) Mar 11th 2026 9:37am, by [Jennifer Riggins](https://thenewstack.io/author/jennifer-riggins/ "Posts by Jennifer Riggins") [How context rot drags down AI and LLM results for enterprises, and how to fix it](https://thenewstack.io/context-rot-enterprise-ai-llms/) Mar 9th 2026 9:00am, by [Todd R. Weiss](https://thenewstack.io/author/todd-r-weiss/ "Posts by Todd R. Weiss") [Inside Claude Code's leaked source: swarms, daemons, and 44 features Anthropic kept behind flags](https://thenewstack.io/claude-code-source-leak/) Apr 1st 2026 7:23am, by [Janakiram MSV](https://thenewstack.io/author/janakiram/ "Posts by Janakiram MSV") [Nvidia's NemoClaw has three layers of agent security. None of them solve the real problem.](https://thenewstack.io/nvidia-nemoclaw-openclaw-security/) Mar 28th 2026 9:30am, by [David Eastman](https://thenewstack.io/author/david-eastman/ "Posts by David Eastman") [Gitleaks creator returns with Betterleaks, an open source secrets scanner for the agentic era](https://thenewstack.io/betterleaks-open-source-secret-scanner/) Mar 27th 2026 11:00am, by [Paul Sawers](https://thenewstack.io/author/paul-sawers/ "Posts by Paul Sawers") [How TeamPCP turned Aqua Security's own Trivy scanner into a weapon against millions of developers](https://thenewstack.io/teampcp-trivy-supply-chain-attack/) Mar 27th 2026 10:00am, by [Steven J. Vaughan-Nichols](https://thenewstack.io/author/sjvn/ "Posts by Steven J. Vaughan-Nichols") [OpenClaw's biggest security flaw is why Jentic Mini exists](https://thenewstack.io/openclaw-is-a-security-mess-jentic-wants-to-fix-it/) Mar 25th 2026 5:00am, by [Darryl K. Taft](https://thenewstack.io/author/darryl-taft/ "Posts by Darryl K. Taft") [How to solve the AI paradox in software development with intelligent orchestration](https://thenewstack.io/solve-ai-paradox-orchestration/) Mar 31st 2026 12:14pm, by [Manav Khurana](https://thenewstack.io/author/manav-khurana/ "Posts by Manav Khurana") [AI accelerates modernization, but don’t leave human devs behind](https://thenewstack.io/ai-modernization-human-developers/) Mar 31st 2026 12:00pm, by [Matthew Weier O’Phinney](https://thenewstack.io/author/matthew-weier-ophinney/ "Posts by Matthew Weier O’Phinney") [Kelsey Hightower at KubeCon 2026: "Everyone is a junior engineer when it comes to AI"](https://thenewstack.io/hightower-ai-open-source-kubecon/) Mar 30th 2026 2:45pm, by [Jennifer Riggins](https://thenewstack.io/author/jennifer-riggins/ "Posts by Jennifer Riggins") [WebAssembly is now outperforming containers at the edge](https://thenewstack.io/webassembly-component-model-future/) Mar 29th 2026 9:00am, by [B. Cameron Gain](https://thenewstack.io/author/bruce-gain/ "Posts by B. Cameron Gain") [96% of codebases rely on open source, and AI slop is putting them at risk](https://thenewstack.io/ai-slop-open-source/) Mar 29th 2026 6:00am, by [Bill Doerrfeld](https://thenewstack.io/author/bill-doerrfeld/ "Posts by Bill Doerrfeld") [Edge-forward: Akamai eyes sweet spot between centralized & decentralized AI inference](https://thenewstack.io/akamai-edge-ai-inference/) Apr 1st 2026 7:00am, by [Adrian Bridgwater](https://thenewstack.io/author/adrian-bridgwater/ "Posts by Adrian Bridgwater") [WebAssembly is now outperforming containers at the edge](https://thenewstack.io/webassembly-component-model-future/) Mar 29th 2026 9:00am, by [B. Cameron Gain](https://thenewstack.io/author/bruce-gain/ "Posts by B. Cameron Gain") [WebAssembly could solve AI agents' most dangerous security gap](https://thenewstack.io/webassembly-sandboxing-ai-agents/) Mar 24th 2026 9:01am, by [B. Cameron Gain](https://thenewstack.io/author/bruce-gain/ "Posts by B. Cameron Gain") [How WebAssembly plugins simplify Kubernetes extensibility](https://thenewstack.io/how-webassembly-plugins-simplify-kubernetes-extensibility/) Mar 3rd 2026 2:00pm, by [B. Cameron Gain](https://thenewstack.io/author/bruce-gain/ "Posts by B. Cameron Gain") [WebAssembly is everywhere. Here's how it works](https://thenewstack.io/webassembly-is-everywhere-heres-how-it-works/) Feb 25th 2026 11:00am, by [Jessica Wachtel](https://thenewstack.io/author/jessica-wachtel/ "Posts by Jessica Wachtel") [AI Operations](https://thenewstack.io/ai-operations/) [CI/CD](https://thenewstack.io/ci-cd/) [Cloud Services](https://thenewstack.io/cloud-services/) [DevOps](https://thenewstack.io/devops/) [Kubernetes](https://thenewstack.io/kubernetes/) [Observability](https://thenewstack.io/observability/) [Operations](https://thenewstack.io/operations/) [Platform Engineering](https://thenewstack.io/platform-engineering/) [JetBrains: AI agents are about to repeat the cloud ROI crisis](https://thenewstack.io/jetbrains-central-ai-agents/) Mar 31st 2026 4:02pm, by Darryl K. Taft [HPE's AI agents cut root cause analysis time in half](https://thenewstack.io/hpes-ai-agents-cut-root-cause-analysis-time-in-half/) Mar 25th 2026 7:14am, by Jennifer Riggins [Why most AI projects fail after the demo actually works](https://thenewstack.io/ai-demo-to-production/) Mar 25th 2026 4:00am, by Oladimeji Sowole [From pillars to platform: How open observability data is changing the industry](https://thenewstack.io/open-observability-ai-platforms/) Mar 20th 2026 6:00am, by Ted Young [Building a Kubernetes-native pattern for AI infrastructure at scale](https://thenewstack.io/kubernetes-native-ai-infrastructure/) Mar 19th 2026 5:00am, by Sachi Desai [How TeamPCP turned Aqua Security's own Trivy scanner into a weapon against millions of developers](https://thenewstack.io/teampcp-trivy-supply-chain-attack/) Mar 27th 2026 10:00am, by Steven J. Vaughan-Nichols [Enterprise dev teams are about to hit a wall. And CI pipelines can't save them.](https://thenewstack.io/ai-agent-validation-bottleneck/) Mar 26th 2026 7:00am, by Anirudh Ramanathan [This simple infrastructure gap is holding back AI productivity](https://thenewstack.io/this-simple-infrastructure-gap-is-holding-back-ai-productivity/) Feb 22nd 2026 8:00am, by Charlotte Fleming [Ramp’s Inspect shows closed-loop AI agents are software’s future](https://thenewstack.io/ramps-inspect-shows-closed-loop-ai-agents-are-softwares-future/) Jan 29th 2026 11:00am, by Arjun Iyer [QCon chat: Is agentic AI killing continuous integration?](https://thenewstack.io/qcon-chat-is-agentic-ai-killing-continuous-integration/) Jan 27th 2026 6:00am, by Joab Jackson [A practical guide to the 6 categories of AI cloud infrastructure in 2026](https://thenewstack.io/ai-cloud-taxonomy-2026/) Mar 15th 2026 5:00am, by Janakiram MSV [Runpod report: Qwen has overtaken Meta's Llama as the most-deployed self-hosted LLM](https://thenewstack.io/runpod-ai-infrastructure-reality/) Mar 12th 2026 6:00am, by Adrian Bridgwater [Snowflake Cortex Code CLI adds dbt and Apache Airflow support for AI-powered data pipelines](https://thenewstack.io/snowflake-cortex-code-dbt-airflow/) Mar 8th 2026 6:00am, by Jelani Harper [Databases weren’t built for agent sprawl – SurrealDB wants to fix it](https://thenewstack.io/surrealdb-3-ai-agents/) Feb 24th 2026 2:07pm, by Paul Sawers [Rising identity complexity: How CISOs can prevent it from becoming an attacker’s roadmap](https://thenewstack.io/ciso-identity-complexity-strategy/) Feb 19th 2026 12:47pm, by Jay Reddy [One developer, team power: The future of AI-driven DevSecOps](https://thenewstack.io/future-ai-driven-devsecops/) Mar 5th 2026 2:29pm, by Bryan Ross [Observability platform migration guide: Prometheus, OpenTelemetry, and Fluent Bit](https://thenewstack.io/observability-platform-migration-guide/) Feb 26th 2026 7:28am, by Katie Greenley [Most platform teams build products, but they don’t know it](https://thenewstack.io/internal-platforms-are-products/) Feb 24th 2026 9:00am, by Oleg Danilyuk [Why "automated" infrastructure might cost more than you think](https://thenewstack.io/automated-infrastructure-hidden-costs/) Feb 24th 2026 4:00am, by Justyn Roberts [The essential shift every ITOps leader must make to survive an unrelenting stream of incidents](https://thenewstack.io/modernizing-itops-incident-management/) Feb 19th 2026 1:46pm, by Ariel Russo [How platform teams are eliminating a \$43,800 "hidden tax" on Kubernetes infrastructure](https://thenewstack.io/virtual-clusters-kubernetes-cost-isolation/) Mar 28th 2026 4:09pm, by Janakiram MSV [Your Kubernetes isn't ready for AI workloads, and drift is the reason](https://thenewstack.io/ai-workloads-kubernetes-infrastructure-drift/) Mar 25th 2026 8:43am, by TNS Staff [Broadcom donates Velero to CNCF — and it could reshape how Kubernetes users handle backup and disaster recovery](https://thenewstack.io/broadcom-velero-cncf-kubernetes/) Mar 24th 2026 8:38am, by B. Cameron Gain [IBM, Red Hat, and Google just donated a Kubernetes blueprint for LLM inference to the CNCF](https://thenewstack.io/llm-d-cncf-kubernetes-inference/) Mar 24th 2026 8:20am, by Steven J. Vaughan-Nichols [Why WebAssembly won't replace Kubernetes but makes Helm more secure](https://thenewstack.io/helm-webassembly-kubernetes-security/) Mar 21st 2026 8:45am, by B. Cameron Gain [Solo.io launches agentevals to solve agentic AI's "biggest unsolved problem"](https://thenewstack.io/soloio-agentevals-evaluates-ai-agents/) Mar 28th 2026 6:00am, by Steven J. Vaughan-Nichols [From pillars to platform: How open observability data is changing the industry](https://thenewstack.io/open-observability-ai-platforms/) Mar 20th 2026 6:00am, by Ted Young [Sampling: the philosopher's stone of distributed tracing](https://thenewstack.io/distributed-tracing-sampling-opentelemetry/) Mar 19th 2026 8:00am, by Michele Mancioppi [Why your observability bill keeps growing (and it's not your vendor's fault)](https://thenewstack.io/why-observability-bills-grow/) Mar 18th 2026 4:00am, by Juraci Paixão Kröhling [Why agentic AI stalls in production — and how a control plane fixes it](https://thenewstack.io/agentic-ai-control-plane-production/) Mar 17th 2026 6:00am, by TNS Staff [Edge-forward: Akamai eyes sweet spot between centralized & decentralized AI inference](https://thenewstack.io/akamai-edge-ai-inference/) Apr 1st 2026 7:00am, by Adrian Bridgwater [The operational gap is real, and it's getting wider](https://thenewstack.io/closing-cloud-operational-gap/) Mar 26th 2026 8:00am, by Yevgeny Pats [HPE's AI agents cut root cause analysis time in half](https://thenewstack.io/hpes-ai-agents-cut-root-cause-analysis-time-in-half/) Mar 25th 2026 7:14am, by Jennifer Riggins [WebAssembly could solve AI agents' most dangerous security gap](https://thenewstack.io/webassembly-sandboxing-ai-agents/) Mar 24th 2026 9:01am, by B. Cameron Gain [Kubernetes co-founder Brendan Burns: AI-generated code will become as invisible as assembly](https://thenewstack.io/ai-generated-code-invisible/) Mar 24th 2026 7:20am, by Frederic Lardinois [How to solve the AI paradox in software development with intelligent orchestration](https://thenewstack.io/solve-ai-paradox-orchestration/) Mar 31st 2026 12:14pm, by Manav Khurana [How platform teams are eliminating a \$43,800 "hidden tax" on Kubernetes infrastructure](https://thenewstack.io/virtual-clusters-kubernetes-cost-isolation/) Mar 28th 2026 4:09pm, by Janakiram MSV [The operational gap is real, and it's getting wider](https://thenewstack.io/closing-cloud-operational-gap/) Mar 26th 2026 8:00am, by Yevgeny Pats [Enterprise dev teams are about to hit a wall. And CI pipelines can't save them.](https://thenewstack.io/ai-agent-validation-bottleneck/) Mar 26th 2026 7:00am, by Anirudh Ramanathan [Your Kubernetes isn't ready for AI workloads, and drift is the reason](https://thenewstack.io/ai-workloads-kubernetes-infrastructure-drift/) Mar 25th 2026 8:43am, by TNS Staff [C++](https://thenewstack.io/c/) [Developer tools](https://thenewstack.io/developer-tools/) [Go](https://thenewstack.io/go/) [Java](https://thenewstack.io/java/) [JavaScript](https://thenewstack.io/javascript/) [Programming Languages](https://thenewstack.io/programming-languages/) [Python](https://thenewstack.io/python/) [Rust](https://thenewstack.io/rust/) [TypeScript](https://thenewstack.io/typescript/) [Open source USearch library jumpstarts ScyllaDB vector search](https://thenewstack.io/open-source-usearch-library-jumpstarts-scylladb-vector-search/) Feb 5th 2026 12:00pm, by Jelani Harper [AWS WAF vs. Google Cloud Armor: A Multicloud Security Showdown](https://thenewstack.io/aws-waf-vs-google-cloud-armor-a-multicloud-security-showdown/) Nov 25th 2025 10:00am, by Advait Patel [Goodbye Dashboards: Agents Deliver Answers, Not Just Reports](https://thenewstack.io/goodbye-dashboards-agents-deliver-answers-not-just-reports/) Nov 23rd 2025 9:00am, by Ketan Karkhanis [Rust vs. C++: a Modern Take on Performance and Safety](https://thenewstack.io/rust-vs-c-a-modern-take-on-performance-and-safety/) Oct 22nd 2025 2:00pm, by Zziwa Raymond Ian [Building a Real-Time System Monitor in Rust Terminal](https://thenewstack.io/building-a-real-time-system-monitor-in-rust-terminal/) Oct 15th 2025 7:05am, by Tinega Onchari [How to integrate VS Code with Ollama for local AI assistance](https://thenewstack.io/how-to-integrate-vs-code-with-ollama-for-local-ai-assistance/) Apr 1st 2026 8:00am, by Jack Wallen [JetBrains: AI agents are about to repeat the cloud ROI crisis](https://thenewstack.io/jetbrains-central-ai-agents/) Mar 31st 2026 4:02pm, by Darryl K. Taft [Claude Code users say they’re hitting usage limits faster than normal](https://thenewstack.io/claude-code-usage-limits/) Mar 31st 2026 2:30pm, by Meredith Shubel [OpenAI's Codex gets plugins](https://thenewstack.io/openais-codex-gets-plugins/) Mar 27th 2026 8:20am, by Frederic Lardinois [GitHub will train AI models on your Copilot data — and share it with Microsoft](https://thenewstack.io/github-copilot-interaction-data/) Mar 27th 2026 6:37am, by Meredith Shubel [Go Experts: 'I Don't Want to Maintain AI-Generated Code'](https://thenewstack.io/go-experts-i-dont-want-to-maintain-ai-generated-code/) Sep 28th 2025 6:00am, by David Cassel [How To Run Kubernetes Commands in Go: Steps and Best Practices](https://thenewstack.io/how-to-run-kubernetes-commands-in-go-steps-and-best-practices/) Jun 27th 2025 8:00am, by Sunny Yadav [Prepare Your Mac for Go Development](https://thenewstack.io/prepare-your-mac-for-go-development/) Apr 12th 2025 7:00am, by Damon M. Garn [Pagoda: A Web Development Starter Kit for Go Programmers](https://thenewstack.io/pagoda-a-web-development-starter-kit-for-go-programmers/) Mar 19th 2025 6:10am, by Loraine Lawson [Microsoft TypeScript Devs Explain Why They Chose Go Over Rust, C\#](https://thenewstack.io/microsoft-typescript-devs-explain-why-they-chose-go-over-rust-c/) Mar 18th 2025 7:00am, by David Cassel [Java 26 lands without an LTS badge. Here's why developers should care anyway.](https://thenewstack.io/java-26-performance-ai/) Mar 18th 2026 9:35am, by Darryl K. Taft [62% of enterprises now use Java to power AI apps](https://thenewstack.io/2026-java-ai-apps/) Feb 10th 2026 12:58pm, by Darryl K. Taft [BellSoft bets Java expertise can beat hardened container wave](https://thenewstack.io/bellsoft-bets-java-expertise-can-beat-hardened-container-wave/) Jan 26th 2026 3:00pm, by Darryl K. Taft [Java Developers Get Multiple Paths To Building AI Agents](https://thenewstack.io/java-developers-get-multiple-paths-to-building-ai-agents/) Dec 26th 2025 7:02am, by Darryl K. Taft [Your Enterprise AI Strategy Must Start With Java, Not Python](https://thenewstack.io/your-enterprise-ai-strategy-must-start-with-java-not-python/) Dec 22nd 2025 1:00pm, by Michael Coté [TypeScript 6.0 RC arrives as a bridge to a faster future](https://thenewstack.io/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future/) Mar 14th 2026 9:00am, by Darryl K. Taft [WebAssembly is everywhere. Here's how it works](https://thenewstack.io/webassembly-is-everywhere-heres-how-it-works/) Feb 25th 2026 11:00am, by Jessica Wachtel [Wasm vs. JavaScript: Who wins at a million rows?](https://thenewstack.io/wasm-vs-javascript-who-wins-at-a-million-rows/) Feb 22nd 2026 6:00am, by Jessica Wachtel [Arcjet reaches v1.0, promises stable security for JavaScript apps](https://thenewstack.io/arcjet-reaches-v1-0-promises-stable-security-for-javascript-apps/) Feb 14th 2026 7:00am, by Darryl K. Taft [How WebAssembly and Web Workers prevent UI freezes](https://thenewstack.io/how-webassembly-and-web-workers-prevent-ui-freezes/) Feb 7th 2026 9:00am, by Jessica Wachtel [Will AI force code to evolve or make it extinct?](https://thenewstack.io/ai-programming-languages-future/) Mar 22nd 2026 6:00am, by David Cassel [Java 26 lands without an LTS badge. Here's why developers should care anyway.](https://thenewstack.io/java-26-performance-ai/) Mar 18th 2026 9:35am, by Darryl K. Taft [TypeScript 6.0 RC arrives as a bridge to a faster future](https://thenewstack.io/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future/) Mar 14th 2026 9:00am, by Darryl K. Taft [Nearly half of all companies now use Rust in production, survey finds](https://thenewstack.io/rust-enterprise-developers/) Mar 6th 2026 10:45am, by Darryl K. Taft [Statistical language R is making a comeback against Python](https://thenewstack.io/statistical-language-r-is-making-a-comeback-against-python/) Feb 12th 2026 2:57pm, by Darryl K. Taft [OpenAI acquires Astral to bring open source Python developer tools to Codex — but details are still fuzzy](https://thenewstack.io/openai-astral-acquisition/) Mar 20th 2026 7:33am, by Meredith Shubel [Python virtual environments: isolation without the chaos](https://thenewstack.io/python-virtual-environments-isolation-without-the-chaos/) Feb 16th 2026 7:00am, by Jessica Wachtel [Statistical language R is making a comeback against Python](https://thenewstack.io/statistical-language-r-is-making-a-comeback-against-python/) Feb 12th 2026 2:57pm, by Darryl K. Taft [Arcjet's Python SDK Embeds Security in Code](https://thenewstack.io/arcjets-python-sdk-embeds-security-in-code/) Jan 16th 2026 2:00pm, by Darryl K. Taft [2025: The Year of the Return of the Ada Programming Language?](https://thenewstack.io/2025-the-year-of-the-return-of-the-ada-programming-language/) Jan 14th 2026 4:00pm, by Darryl K. Taft [Nearly half of all companies now use Rust in production, survey finds](https://thenewstack.io/rust-enterprise-developers/) Mar 6th 2026 10:45am, by Darryl K. Taft [Wasm vs. JavaScript: Who wins at a million rows?](https://thenewstack.io/wasm-vs-javascript-who-wins-at-a-million-rows/) Feb 22nd 2026 6:00am, by Jessica Wachtel [Open source USearch library jumpstarts ScyllaDB vector search](https://thenewstack.io/open-source-usearch-library-jumpstarts-scylladb-vector-search/) Feb 5th 2026 12:00pm, by Jelani Harper [The 'weird' things that happened when Clickhouse replaced C++ with Rust](https://thenewstack.io/the-weird-things-that-happened-when-clickhouse-replaced-c-with-rust/) Feb 4th 2026 7:26am, by B. Cameron Gain [Async Rust: Pinning demystified](https://thenewstack.io/async-rust-pinning-demystified/) Jan 26th 2026 11:00am, by Anshul Gupta [TypeScript 6.0 RC arrives as a bridge to a faster future](https://thenewstack.io/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future/) Mar 14th 2026 9:00am, by Darryl K. Taft [Mastra empowers web devs to build AI agents in TypeScript](https://thenewstack.io/mastra-empowers-web-devs-to-build-ai-agents-in-typescript/) Jan 28th 2026 11:00am, by Loraine Lawson [Inferno Vet Creates Frontend Framework Built With AI in Mind](https://thenewstack.io/inferno-vet-creates-frontend-framework-built-with-ai-in-mind/) Dec 10th 2025 11:00am, by Loraine Lawson [JavaScript Utility Library Lodash Changing Governance Model](https://thenewstack.io/javascript-utility-library-lodash-changing-governance-model/) Nov 1st 2025 7:00am, by Loraine Lawson [Microsoft TypeScript Devs Explain Why They Chose Go Over Rust, C\#](https://thenewstack.io/microsoft-typescript-devs-explain-why-they-chose-go-over-rust-c/) Mar 18th 2025 7:00am, by David Cassel 2025-09-03 10:00:46 How to Make OpenTelemetry Better in the Browser sponsor-embrace,sponsored-post-contributed, [Frontend Development](https://thenewstack.io/category/frontend-development/) / [JavaScript](https://thenewstack.io/category/javascript/) / [Observability](https://thenewstack.io/category/observability/) # How to Make OpenTelemetry Better in the Browser Addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, but just improving isn't enough. Sep 3rd, 2025 10:00am by [Hazel Weakly](https://thenewstack.io/author/hazel-weakly/ "Posts by Hazel Weakly") ![Featued image for: How to Make OpenTelemetry Better in the Browser](https://cdn.thenewstack.io/media/2025/09/e4b442ee-otel-1024x576.jpg) Image from Zakharchuk on Shutterstock. [Embrace](https://embrace.io/?utm_content=sponsor+disclosure) sponsored this post. This is the second of two parts. Read Part 1: - [Why OpenTelemetry Is So Clunky for the Frontend](https://thenewstack.io/building-an-ergonomic-opentelemetry-for-javascript/) In Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with [OpenTelemetry’s model of spans and traces](https://thenewstack.io/opentelemetry-challenges-handling-long-running-spans/). I’ll pick up where I left off by sharing another approach to make [OpenTelemetry](https://thenewstack.io/what-is-opentelemetry-the-ultimate-guide/) more ergonomic for [JavaScript](https://thenewstack.io/30-years-of-javascript-10-milestones-that-changed-the-web/). I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today. Now, as a reminder of where we left off last time, remember that traces, spans, span events and logs are all built on top of the same underlying primitive. That is, they’re all basically just events. ## Don’t Make Me Think If we accept that OpenTelemetry is just events all the way down, then in theory, all you really have to do is write something like `trace.info()` and pass in an object. That’s it. You can have `trace.info`, `trace.error`, `trace.warn` and so on. Given the ubiquity of logging information, it shouldn’t be terribly surprising that most logging-like APIs are a quite natural interface for instrumentation. It [works perfectly for JavaScript and many other languages](https://thenewstack.io/javascript-framework-reality-check-whats-actually-working/), including those that don’t have the ability to provide metaprogramming-style abstractions, thread-local state or other facilities that make OpenTelemetry’s API more ergonomic. > While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. It’s a huge improvement! But certain additional functions would be really helpful. It’s still challenging to design telemetry and propagate it in a way that’s maximally useful. [![](https://cdn.thenewstack.io/media/2024/06/db93b5b0-embrace_logo.svg)](https://embrace.io/?utm_content=sponsor+module) Embrace is the user-focused observability platform that ties technical performance to end-user impact. Powered by OpenTelemetry, Embrace provides real user monitoring for mobile and web, so engineering teams can resolve issues faster, improve performance, and deliver exceptional digital experiences. Learn More The latest from Embrace Taking inspiration from other types of instrumentation can give us some ideas of what might be useful here: What if there were a function to add metadata to the root span, regardless of where it is? Implementing this function would be tricky because span immutability is deeply central to the OpenTelemetry API, and violating that would break other things. However, another way to approach that would be durable reference values to sets of attributes, which could then be mutable. That would also potentially massively cut down on network bandwidth. TRENDING STORIES Going further into the inspiration and ideas: What if there was a function to add a new span, but only if a parent span didn’t already exist, or otherwise attach things to the existing span? What if there were a function to take data and add it to every child span, maybe even recursively? What if there were a way to write instrumentation for a single function, but have that instrumentation remain useful when that function is called in a loop? And how could you write all of this without having to create custom processors or custom code to glue everything together in a way that makes sense for your use case? ## Imagining the Future This brings up a fascinating design space for me: If I were to look far into the future and imagine what telemetry could look like, what might be possible? Let’s take a step into this hypothetical future and imagine: What if the instrumentation library didn’t really exist in the traditional sense, and the code you were writing was actually going to be generated on the fly and rewritten by the compiler? You could use this to make instrumentation code very lightweight and minimal, essentially being custom-built for your application at compile time. You could use the compiler’s information to insert code structure automatically, add lifetime annotations, control flow information, call stack data and maybe even rewrite the telemetry to make more sense for your application’s needs. This could facilitate very advanced instrumentation rewriting, minimization and compression as well; imagine a source map-style construct where you send binary pointers to certain common sets of data. You could even imagine normalizing or denormalizing telemetry automatically. Or enabling code to be written for both streaming and batch use cases without code changes. Collectors could roll and unroll telemetry for you, collapse certain pieces of data or even completely rewrite the telemetry tree as needed. Browsers and language runtimes could also improve existing limitations by ensuring proper thread-local storage support, context propagation and support for context propagation inside async-like scopes. > I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. The ability to propagate information in a “magical” metadata object could also be a huge facilitator for building these types of structures, which could be thought of as similar to the reference of metadata idea I brought up earlier. If the language runtimes included explicit instrumentation support as well, then that instrumentation could be written in a heavily optimized manner, which would enable garbage-collected languages to benefit from low-to-zero overhead instrumentation. I find this exciting because it is an actual goal of the OpenTelemetry project, so the potential isn’t out of reach, but it’ll take a lot of coordination. In addition, I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. Then you wouldn’t blow up everything with verbose debugging data when deploying to remote servers, but when debugging something locally, you could easily go all the way down to the system call level or even inspect the hardware to get extremely granular views of every interface, no matter how highly abstracted. Just because a language is high-level doesn’t mean you shouldn’t be able to examine the details when you need or want to. I think we could build languages in the future that allow this ergonomically, letting you instrument code for production while getting rich instrumentation for development, without having to instrument the system twice. Luckily, much of what is described here is an explicit outcome of the upcoming [OpenTelemetry Profiling signal](https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/profiles/0212-profiling-vision.md), so I hope to see a lot of progress in the next few years. > Let’s step back and return to reality. The future is fun to think about, but what can we start with today? If instrumentation were more tightly embedded into languages, then one could also imagine the uniform integration of other metadata, such as: debugging information, performance profiling, feature flags, marketing data, security events and experimentation data. Instead of each platform building its own SDKs and needing their own implementations, they could use instrumentation features built deeper into the language runtime itself. You could instrument once and feed that data into various platforms — from [observability and monitoring](https://thenewstack.io/monitoring-vs-observability-whats-the-difference/ "observability and monitoring") to security and experimentation — all using the same code. I like to imagine that future as being one where cross-functional collaboration is more accessible and where understanding the complex system being built becomes a truly company-wide endeavor. I’d love to see that happen. ## Getting to Better All of that starry-eyed and sparkly future musing is great, but we might not realistically see those types of changes for years or even decades. It’d also require a lot of coordination, and it’s not clear whether the communities involved even want this to happen. So let’s step back and return to reality. The future is fun to think about, but what can we start with today? Here’s my thinking: Since events already exist in OpenTelemetry, and since almost everything is events under the hood, we could build support for “just sending events” as an OpenTelemetry specification — think of it as an alternative representation of spans, traces, logs and span events. This would give us a ton of freedom to write whatever library SDKs are needed for a language while retaining full compatibility with vendors. We’re pretty close to being able to do this today, as all it would require would be a modified SDK implementation and a modified stateful OTel Collector. If those two things happened, vendor compatibility would stay the same, and we’d get to experiment with what an event-based representation could look like. Some observability vendors are already adopting this telemetry flexibility mindset in their products, particularly those involved in the mobile space. One great example of that is [Embrace’s User Journeys](https://embrace.io/blog/user-journeys-walkthrough/?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) functionality, where you can create custom user flows from existing telemetry you’re already collecting without having to restructure your code. If you’re interested in learning more, you can check out their [upcoming live webinar](https://get.embrace.io/user-journeys-webinar?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) on Sept. 16 at 10 a.m. PT/1 p.m. ET. An event-based representation of telemetry data would also facilitate interoperating between traces, spans, logs and span events. It would also allow us to more easily migrate from logs to traces using the same code. This doesn’t mean that I think we’re going to get rid of the current SDK, however. It’s very useful for the backend and also represents a well-done “pay now” API where the client does some more work to handle the stateful nature of telemetry and, in exchange, the collector can be stateless. That means it’s very easy for vendors to be OpenTelemetry-compatible. I can easily see a future in which people choose between the “pay now” model, where state complexity lives on the client, versus a “pay later” model, where state complexity is in the collector, depending on what makes sense for their environment. High-volume microservices likely benefit from a “pay now” model, and the frontend works best with a “pay later” model. Putting the two together and being able to tie it all into a coherent context would unlock the next generation of understanding our systems. I can already see bits of this starting to happen, and it makes me really excited for the future of OpenTelemetry in the browser. I’ve mentioned in other blog posts that the [Cloud Native Computing Foundation (CNCF)](https://cncf.io/?utm_content=inline+mention) has a new dedicated Browser Special Interest Group (SIG) for it, which is actively working on improving browser support. I think that is going to create fascinating developments, and I truly look forward to seeing what it becomes one day. If you’d like to learn more about what the Browser SIG is working on, check out this [on-demand webinar](https://get.embrace.io/web-otel-panel-typ?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js). Created with Sketch. [![](https://cdn.thenewstack.io/media/2024/10/58af1826-cropped-06daf154-screenshot-2024-10-02-at-10.13.52%E2%80%AFam.png) Hazel Weakly spends her days building out teams of humans as well as the infrastructure, systems, automation and tooling to make life better for others. She’s worked at a variety of companies, across a wide range of tech and knows... Read more from Hazel Weakly](https://thenewstack.io/author/hazel-weakly/) [Embrace](https://embrace.io/?utm_content=sponsor+disclosure) sponsored this post. SHARE THIS STORY TRENDING STORIES SHARE THIS STORY TRENDING STORIES TNS DAILY NEWSLETTER Receive a free roundup of the most recent TNS articles in your inbox each day. SUBSCRIBE The New Stack does not sell your information or share it with unaffiliated third parties. By continuing, you agree to our [Terms of Use](https://thenewstack.io/terms-of-use/) and [Privacy Policy](https://thenewstack.io/privacy-policy/). ARCHITECTURE [Cloud Native Ecosystem](https://thenewstack.io/cloud-native/) [Containers](https://thenewstack.io/containers/) [Databases](https://thenewstack.io/databases/) [Edge Computing](https://thenewstack.io/edge-computing/) [Infrastructure as Code](https://thenewstack.io/infrastructure-as-code/) [Linux](https://thenewstack.io/linux/) [Microservices](https://thenewstack.io/microservices/) [Open Source](https://thenewstack.io/open-source/) [Networking](https://thenewstack.io/networking/) [Storage](https://thenewstack.io/storage/) ENGINEERING [AI](https://thenewstack.io/ai/) [AI Engineering](https://thenewstack.io/ai-engineering/) [API Management](https://thenewstack.io/api-management/) [Backend development](https://thenewstack.io/backend-development/) [Data](https://thenewstack.io/data/) [Frontend Development](https://thenewstack.io/frontend-development/) [Large Language Models](https://thenewstack.io/llm/) [Security](https://thenewstack.io/security/) [Software Development](https://thenewstack.io/software-development/) [WebAssembly](https://thenewstack.io/webassembly/) OPERATIONS [AI Operations](https://thenewstack.io/ai-operations/) [CI/CD](https://thenewstack.io/ci-cd/) [Cloud Services](https://thenewstack.io/cloud-services/) [DevOps](https://thenewstack.io/devops/) [Kubernetes](https://thenewstack.io/kubernetes/) [Observability](https://thenewstack.io/observability/) [Operations](https://thenewstack.io/operations/) [Platform Engineering](https://thenewstack.io/platform-engineering/) CHANNELS [Podcasts](https://thenewstack.io/podcasts/) [Ebooks](https://thenewstack.io/ebooks/) [Events](https://thenewstack.io/events/) [Webinars](https://thenewstack.io/webinars/) [Newsletter](https://thenewstack.io/newsletter/) [TNS RSS Feeds](https://thenewstack.io/rss-feeds/) THE NEW STACK [About / Contact](https://thenewstack.io/about-and-contact-info/) [Sponsors](https://thenewstack.io/sponsors/) [Advertise With Us](https://thenewstack.io/sponsorship/) [Contributions](https://thenewstack.io/contributions/) [roadmap.sh Community created roadmaps, articles, resources and journeys for developers to help you choose your path and grow in your career.](https://roadmap.sh/?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer) [Frontend Developer Roadmap](https://roadmap.sh/frontend?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer) [Backend Developer Roadmap](https://roadmap.sh/backend?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer) [Devops Roadmap](https://roadmap.sh/devops?utm_source=The+New+Stack&utm_medium=Referral&utm_campaign=Footer) © The New Stack 2026 [Disclosures](https://thenewstack.io/disclosure-guidelines/) [Terms of Use](https://thenewstack.io/terms-of-use/) [Advertising Terms & Conditions](https://thenewstack.io/advertising-terms-conditions/) [Privacy Policy](https://thenewstack.io/privacy-policy/) [Cookie Policy](https://thenewstack.io/cookie-policy/) FOLLOW TNS ![](https://www.facebook.com/tr?id=1244424359562950&ev=PageView&noscript=1) ![](https://px.ads.linkedin.com/collect/?pid=4664394&fmt=gif)
Readable Markdown	This is the second of two parts. Read Part 1: - [Why OpenTelemetry Is So Clunky for the Frontend](https://thenewstack.io/building-an-ergonomic-opentelemetry-for-javascript/) In Part 1, I covered some of the reasons why it’s difficult to use OpenTelemetry in the browser, including how the event loop-driven design of JavaScript is at odds with [OpenTelemetry’s model of spans and traces](https://thenewstack.io/opentelemetry-challenges-handling-long-running-spans/). I’ll pick up where I left off by sharing another approach to make [OpenTelemetry](https://thenewstack.io/what-is-opentelemetry-the-ultimate-guide/) more ergonomic for [JavaScript](https://thenewstack.io/30-years-of-javascript-10-milestones-that-changed-the-web/). I’ll then cover some starry-eyed ideas for the future that I’d love to see happen, before wrapping up with some immediate improvements we can make today. Now, as a reminder of where we left off last time, remember that traces, spans, span events and logs are all built on top of the same underlying primitive. That is, they’re all basically just events. ## Don’t Make Me Think If we accept that OpenTelemetry is just events all the way down, then in theory, all you really have to do is write something like `trace.info()` and pass in an object. That’s it. You can have `trace.info`, `trace.error`, `trace.warn` and so on. Given the ubiquity of logging information, it shouldn’t be terribly surprising that most logging-like APIs are a quite natural interface for instrumentation. It [works perfectly for JavaScript and many other languages](https://thenewstack.io/javascript-framework-reality-check-whats-actually-working/), including those that don’t have the ability to provide metaprogramming-style abstractions, thread-local state or other facilities that make OpenTelemetry’s API more ergonomic. > While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. While addressing the OpenTelemetry API’s design might make instrumentation more ergonomic, improving that alone isn’t really sufficient for improved ergonomics. It’s a huge improvement! But certain additional functions would be really helpful. It’s still challenging to design telemetry and propagate it in a way that’s maximally useful. Taking inspiration from other types of instrumentation can give us some ideas of what might be useful here: What if there were a function to add metadata to the root span, regardless of where it is? Implementing this function would be tricky because span immutability is deeply central to the OpenTelemetry API, and violating that would break other things. However, another way to approach that would be durable reference values to sets of attributes, which could then be mutable. That would also potentially massively cut down on network bandwidth. TRENDING STORIES Going further into the inspiration and ideas: What if there was a function to add a new span, but only if a parent span didn’t already exist, or otherwise attach things to the existing span? What if there were a function to take data and add it to every child span, maybe even recursively? What if there were a way to write instrumentation for a single function, but have that instrumentation remain useful when that function is called in a loop? And how could you write all of this without having to create custom processors or custom code to glue everything together in a way that makes sense for your use case? ## Imagining the Future This brings up a fascinating design space for me: If I were to look far into the future and imagine what telemetry could look like, what might be possible? Let’s take a step into this hypothetical future and imagine: What if the instrumentation library didn’t really exist in the traditional sense, and the code you were writing was actually going to be generated on the fly and rewritten by the compiler? You could use this to make instrumentation code very lightweight and minimal, essentially being custom-built for your application at compile time. You could use the compiler’s information to insert code structure automatically, add lifetime annotations, control flow information, call stack data and maybe even rewrite the telemetry to make more sense for your application’s needs. This could facilitate very advanced instrumentation rewriting, minimization and compression as well; imagine a source map-style construct where you send binary pointers to certain common sets of data. You could even imagine normalizing or denormalizing telemetry automatically. Or enabling code to be written for both streaming and batch use cases without code changes. Collectors could roll and unroll telemetry for you, collapse certain pieces of data or even completely rewrite the telemetry tree as needed. Browsers and language runtimes could also improve existing limitations by ensuring proper thread-local storage support, context propagation and support for context propagation inside async-like scopes. > I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. The ability to propagate information in a “magical” metadata object could also be a huge facilitator for building these types of structures, which could be thought of as similar to the reference of metadata idea I brought up earlier. If the language runtimes included explicit instrumentation support as well, then that instrumentation could be written in a heavily optimized manner, which would enable garbage-collected languages to benefit from low-to-zero overhead instrumentation. I find this exciting because it is an actual goal of the OpenTelemetry project, so the potential isn’t out of reach, but it’ll take a lot of coordination. In addition, I’d love to see a world with extremely rich data for local debugging and the ability to naturally reduce that data for production deployment. Then you wouldn’t blow up everything with verbose debugging data when deploying to remote servers, but when debugging something locally, you could easily go all the way down to the system call level or even inspect the hardware to get extremely granular views of every interface, no matter how highly abstracted. Just because a language is high-level doesn’t mean you shouldn’t be able to examine the details when you need or want to. I think we could build languages in the future that allow this ergonomically, letting you instrument code for production while getting rich instrumentation for development, without having to instrument the system twice. Luckily, much of what is described here is an explicit outcome of the upcoming [OpenTelemetry Profiling signal](https://github.com/open-telemetry/opentelemetry-specification/blob/main/oteps/profiles/0212-profiling-vision.md), so I hope to see a lot of progress in the next few years. > Let’s step back and return to reality. The future is fun to think about, but what can we start with today? If instrumentation were more tightly embedded into languages, then one could also imagine the uniform integration of other metadata, such as: debugging information, performance profiling, feature flags, marketing data, security events and experimentation data. Instead of each platform building its own SDKs and needing their own implementations, they could use instrumentation features built deeper into the language runtime itself. You could instrument once and feed that data into various platforms — from [observability and monitoring](https://thenewstack.io/monitoring-vs-observability-whats-the-difference/ "observability and monitoring") to security and experimentation — all using the same code. I like to imagine that future as being one where cross-functional collaboration is more accessible and where understanding the complex system being built becomes a truly company-wide endeavor. I’d love to see that happen. ## Getting to Better All of that starry-eyed and sparkly future musing is great, but we might not realistically see those types of changes for years or even decades. It’d also require a lot of coordination, and it’s not clear whether the communities involved even want this to happen. So let’s step back and return to reality. The future is fun to think about, but what can we start with today? Here’s my thinking: Since events already exist in OpenTelemetry, and since almost everything is events under the hood, we could build support for “just sending events” as an OpenTelemetry specification — think of it as an alternative representation of spans, traces, logs and span events. This would give us a ton of freedom to write whatever library SDKs are needed for a language while retaining full compatibility with vendors. We’re pretty close to being able to do this today, as all it would require would be a modified SDK implementation and a modified stateful OTel Collector. If those two things happened, vendor compatibility would stay the same, and we’d get to experiment with what an event-based representation could look like. Some observability vendors are already adopting this telemetry flexibility mindset in their products, particularly those involved in the mobile space. One great example of that is [Embrace’s User Journeys](https://embrace.io/blog/user-journeys-walkthrough/?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) functionality, where you can create custom user flows from existing telemetry you’re already collecting without having to restructure your code. If you’re interested in learning more, you can check out their [upcoming live webinar](https://get.embrace.io/user-journeys-webinar?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js) on Sept. 16 at 10 a.m. PT/1 p.m. ET. An event-based representation of telemetry data would also facilitate interoperating between traces, spans, logs and span events. It would also allow us to more easily migrate from logs to traces using the same code. This doesn’t mean that I think we’re going to get rid of the current SDK, however. It’s very useful for the backend and also represents a well-done “pay now” API where the client does some more work to handle the stateful nature of telemetry and, in exchange, the collector can be stateless. That means it’s very easy for vendors to be OpenTelemetry-compatible. I can easily see a future in which people choose between the “pay now” model, where state complexity lives on the client, versus a “pay later” model, where state complexity is in the collector, depending on what makes sense for their environment. High-volume microservices likely benefit from a “pay now” model, and the frontend works best with a “pay later” model. Putting the two together and being able to tie it all into a coherent context would unlock the next generation of understanding our systems. I can already see bits of this starting to happen, and it makes me really excited for the future of OpenTelemetry in the browser. I’ve mentioned in other blog posts that the [Cloud Native Computing Foundation (CNCF)](https://cncf.io/?utm_content=inline+mention) has a new dedicated Browser Special Interest Group (SIG) for it, which is actively working on improving browser support. I think that is going to create fascinating developments, and I truly look forward to seeing what it becomes one day. If you’d like to learn more about what the Browser SIG is working on, check out this [on-demand webinar](https://get.embrace.io/web-otel-panel-typ?utm_source=the-new-stack&utm_medium=paid&utm_campaign=ergonomic-js). Created with Sketch.
Shard	197 (laksa)
Root Hash	5306194916123425997
Unparsed URL	io,thenewstack!/how-to-make-opentelemetry-better-in-the-browser/ s443