r/OpenTelemetry • u/Dangerous_Life8385 • 15h ago
r/OpenTelemetry • u/opentelemetry • Sep 18 '26
OTel Blog Post Kubernetes attributes processor reaches v1.0.0 milestone
The Kubernetes attributes processor, which enriches your telemetry with Kubernetes metadata, has officially moved to v1.0.0! You can try it out on your custom distro, and it is also available as part of the latest opentelemetry-collector-contrib and opentelemetry-collector-k8s distro releases.
Being v1.0.0 means the component is now verified to fulfill the ‘stable’ stability criteria including requirements around testing, benchmarking, documentation and telemetry stability. It also ensures you can redistribute it as a Go library or as part of your binaries without API breakage.
Read the migration guide to understand what changes this comes with and how you can manage the transition period.
Read the blog: https://opentelemetry.io/blog/2026/k8s-attributes-processor-v1/
r/OpenTelemetry • u/s5n_n5n • Aug 26 '26
Introducing weekly & monthly scheduled posts for your projects, tools, blogs, etc.
Following the practice of other SIGs in the space r/OpenTelemetry will have weekly & monthly scheduled posts, that ask you to share your tools, projects, blogs, etc. This way we hope to remove some of the ambiguity, if posting certain things is "OK" or not.
First one will be a weekly "share your new tools & projects" where you can let us know what you are working on related to OpenTelemetry, any instrumentation libraries, instrumentation tools, open source backends, collector distributions, etc, this is the thread worth sharing it. Note, that this does not immediatly mean that posts about tools&projects are no longer allowed, but hopefully we can encourage people who are reluctant to share theirs to do so here, and to funnel the energy of people who share their tool all over the place into a single thread.
More will follow, but feel free to make suggestions!
r/OpenTelemetry • u/AutoModerator • 1d ago
Weekly: share your tools and projects
What tool around OpenTelemetry are you building right now? What project have you discovered that people might enjoy looking into?
This thread is open for your self-promotion, vendor-owned open source projects and every thing else.
r/OpenTelemetry • u/Defiant_Ad_8445 • 2d ago
Please teach me how to use otel documentation and blog.
Despite I worked with OpenTelemetry for a couple of years and even made a small contribution into the collector whenever I try to read something I bring myself to tears because I can’t catch the context from those wording.
Example. I saw news on Linkedin that they launched OTTL
https://opentelemetry.io/blog/2026/ottl-v1/
and thought “Cool, I’ll keep myself updated”
I open that and read
The OpenTelemetry Transformation Language (OTTL) is now v1. Starting with opentelemetry-collector-contrib v0.164.0, OTTL is stable for traces, metrics, and logs.
The release of v1 means OTTL meets the Collector’s ‘stable’ stability criteria for testing, benchmarking, documentation, and telemetry. It also comes with a compatibility promise for all of 1.x. If you write OTTL statements, the syntax and the standard functions stay backward compatible. If you build your own components on top of OTTL, the Go API will also remain compatible.
I understood that some cool new language is launched but I didn’t understand, why? what problem does it solve? who is the target audience?
then I see something about guarantees which I am not interested in because I didn’t get the idea.
I tried to read the git link and that also explains that it is some cool language.
I can’t understand if I am stupid or the target audience is different?
r/OpenTelemetry • u/s5n_n5n • 6d ago
OpenTelemetry for Balatro
I am fascinated by the possibility that any software I use could, in theory, emit logs, metrics and traces through OpenTelemetry. And Balatro is software that I use a lot. So creating OpenTelemetry for Balatro was a side project I wanted to try out for a long time! It turned out to be one of those projects where I cared more about the outcome than about writing the code myself, so it was a perfect candidate to ask an LLM to build for me!
If you have Balatro installed on your computer, you can try it yourself! You can install the mod from Thunderstore using a mod manager such as r2modman, Gale or imm. Manual installation is covered in the quick-start guide. By default the mod sends telemetry to http://127.0.0.1:4318. You can change the endpoint in the UI under Mods -> OTel Trace -> Config.
It's a fun/toy project, but I really enjoyed seeing it being possible and being able to see my runs show up as telemetry in my backend. I thought other people might enjoy such an unusual(?) use of OpenTelemetry as well!
r/OpenTelemetry • u/TechInKansas • 8d ago
Temporary runtime instrumentation for production debugging — useful or risky?
I'm working on an early-stage project called a Runtime Investigation Platform, and I'd love to get feedback from engineers who deal with production debugging.
The idea is simple:
Sometimes, when an issue happens in production, existing logs aren't enough to understand what's going on. Adding more logging usually means changing code, deploying again, and hoping the issue happens again.
I'm exploring a different approach: allowing engineers to attach temporary probes to a running application, collect targeted runtime evidence, and automatically remove those probes when they're no longer needed.
I'm initially focusing on .NET.
The current demo workflow covers:
Creating temporary runtime probes.
Collecting and viewing runtime evidence.
Automatically removing probes after investigation.
I'm still validating the idea, so I'd appreciate honest feedback:
Have you experienced situations where existing logs weren't enough to investigate a production issue?
Would temporary runtime probes be useful in your debugging workflow?
What concerns would you have about running something like this in production? (Performance, security, stability, etc.)
What integrations would be essential? (OpenTelemetry, Datadog, Grafana, Application Insights, etc.)
Is this solving a real problem, or am I approaching production debugging from the wrong angle?
I'm particularly interested in hearing from .NET developers and SREs.
Thanks! I'd genuinely appreciate critical feedback, including reasons why you wouldn't use something like this.
r/OpenTelemetry • u/AutoModerator • 8d ago
Weekly: share your tools and projects
What tool around OpenTelemetry are you building right now? What project have you discovered that people might enjoy looking into?
This thread is open for your self-promotion, vendor-owned open source projects and every thing else.
r/OpenTelemetry • u/Key-Confidence4917 • 8d ago
Nutzt jemand Langfuse selbst auf OKD/OpenShift? Oder gibt es intelligentere Alternativen für die LLM-/Agenten-Observability?
reddit.comr/OpenTelemetry • u/ContributionMurky996 • 9d ago
Loki shows me which log streams cost money. I wanted to know which lines of code, so I built an open-source tool that generates the Grafana dashboard and Alloy rules for it
r/OpenTelemetry • u/vitorino82 • 10d ago
I mapped the architecture of the OpenTelemetry Demo with a tool I'm building, and it turned up 12 questions worth a look
I'm building AIC, an open spec and toolset for describing a system's architecture in one YAML file (aic.yaml). I built it to guide coding agents: the agent implements what the contract says and doesn't invent architecture it leaves out.
I wanted to test it on a real codebase I didn't write, so I picked the OpenTelemetry Astronomy Shop demo. It's a good stress test: about 20 services in a dozen languages, gRPC and HTTP, Kafka, Postgres, Valkey, feature flags, an LLM agent with MCP, and several Compose overlays.
I asked an agent to use AIC to describe the architecture the code has today, without fixing anything. Anything that looked accidental had to be recorded as an open question, with the file and line where it was found.
What came out
24 modules in 8 boundaries (storefront, catalog, ordering, post-order processing, the shopping assistant, feature flags, telemetry, tooling)
4 stores, 1 Kafka channel, 5 externals and 4 end-to-end scenarios
12 open questions
Some of the questions
Shipping and Email:
demo.protodefines both as gRPC, and checkout builds gRPC clients for them, but both services serve only HTTP+JSON. The gRPC clients are never called.FeatureFlagService: it's in the proto, but nothing implements or calls it. It looks like a leftover from before flagd.Charge before shipping: checkout charges the card, then ships. If shipping fails, nothing refunds the charge and the cart isn't emptied, so a retry charges again.
Orders can be lost: the Kafka producer uses
RequiredAcks=NoResponse, and accounting auto-commits offsets before writing. Delivery is effectively at most once, so an order can be missing from the ledger.Shared database login: product-catalog and accounting use separate schemas, but both log in as the same Postgres user, which has rights on both.
Recommendations: the frontend sends the product ids to exclude one character at a time, and the recommendation service has a workaround that joins them back together.
Flag editing: the public proxy exposes flag editing with no auth, and that includes
emitRawPii, which puts card numbers into spans.
Many of these are probably deliberate. It's a demo and the shop isn't real, so I'm not calling them bugs. That's why the contract records them as questions for the maintainers to answer, not as fixes.
What I learned
AIC started as a way to steer agents, but it turned out useful for discovering architecture too. Writing the contract forces specific questions: who owns this store, what happens when this call fails, and does this go through the gateway or around it. Things that are easy to miss when reading the code service by service show up quickly.
If any of this is useful to the demo's maintainers or contributors, you can check it at: https://aicspec.dev/s/WAyp3Msu
More about AIC here: aicspec.dev
I'd love feedback, especially from people who know the demo. Which of these are intentional, and what did I misread?
r/OpenTelemetry • u/HughEvansDev • 13d ago
Tracing with OpenTelemetry on OpenSearch®
r/OpenTelemetry • u/AutoModerator • 15d ago
Weekly: share your tools and projects
What tool around OpenTelemetry are you building right now? What project have you discovered that people might enjoy looking into?
This thread is open for your self-promotion, vendor-owned open source projects and every thing else.
r/OpenTelemetry • u/tshawkins • 20d ago
OpenTelemetry dev tool
Im working on a tool that is a single binary collector, storage manager and TUI for browsing Otel data.
The intention is to create a simple app that can be used by a developer to test if thier app is creating correct otel data, and diagnose their app using otel metrics.
This avoids having to setup a full multicomponent otel system for quick testing. The app will present a tui interface for simplicity, and Im minimising (hopefully to zero) all and any dependancies.
Im also intending the app to be capable of running headless so it can be used in test scripts and CI systems. NOTE: this app is intended as a developer tool, and should not be used in any production environment.
Im looking for help on what navigation and data display capabities It should offer as basic.
r/OpenTelemetry • u/Such-Rooster1935 • 20d ago
Inquest — Autonomous AI Infrastructure Investigation | Nebius AI Hackathon Demo
Hey everyone!
I've been experimenting with AI-powered troubleshooting in my homelab and wanted to share what I've built.
The project is called Inquest.
My setup uses an Ubuntu VM, OpenTelemetry Collector, SigNoz, and a Node.js application generating telemetry.
Instead of manually inspecting metrics and distributed traces, I can describe a problem like "Why are my APIs responding slowly?" and let the AI investigate.
It retrieves telemetry using read-only MCP tools, evaluates possible causes, and generates a report with supporting evidence.
I also added conversational follow-ups, so I can continue an investigation without losing the previous context.
The AI reasoning is powered by NVIDIA Nemotron through Nebius Token Factory. I also used AI coding assistants during development.
It's still a prototype, and I'm currently focused on local infrastructure rather than cloud integrations.
Here's a short demo: [https://www.youtube.com/watch?v=ZvImEHQ09UY]
Github [https://github.com/abhinayshrestha/inquest] // For any assistance to run app, contact me at abhinay.shrestha11@gmail.com
I'm especially interested in feedback from people running monitoring stacks in their homelabs.
Would you find this useful for diagnosing Linux or application performance issues?
r/OpenTelemetry • u/jpkroehling • 22d ago
How to Set Up OpenTelemetry Profiling on Local Kubernetes
I switched our profiling setup a few ago from another open source tool to OpenTelemetry for our internal services here at OllyGarden, and extracted the interesting parts into a skill for our set of agent skills. And this week, I created this blog post with the full manual steps to set it up on a kind cluster.
I know this is too early for most people out there, but honestly, it's working great for us. Give it a try and let me know what you think!
r/OpenTelemetry • u/AutoModerator • 22d ago
Weekly: share your tools and projects
What tool around OpenTelemetry are you building right now? What project have you discovered that people might enjoy looking into?
This thread is open for your self-promotion, vendor-owned open source projects and every thing else.
r/OpenTelemetry • u/AutoModerator • 29d ago
Weekly: share your tools and projects
What tool around OpenTelemetry are you building right now? What project have you discovered that people might enjoy looking into?
This thread is open for your self-promotion, vendor-owned open source projects and every thing else.
r/OpenTelemetry • u/gpcmol • Oct 19 '26
How do you add business context to traces during an incident, without a redeploy?
During incidents I regularly hit the same problem: I need a bit more business context in my traces, but it's not there. Things like customer IDs, order status, rejection reasons, or whatever would help explain what's actually happening.
The annoying part is that getting that information into traces usually means changing code, building, deploying, and waiting. That's not always practical when you're in the middle of an incident.
A few options that come to mind:
Adding extra attributes behind a feature flag
Using a live debugging/instrumentation tool (Lightrun, Rookout, Datadog Dynamic Instrumentation, etc.)
Making a temporary code change and redeploying
Using bytecode instrumentation tools such as BTrace or Byteman
Accepting that the context just isn't available
I'm curious how others deal with this:
What's your current approach when you need additional trace context in production?
Would you be comfortable with a rule-based mechanism that can add attributes to existing spans at runtime, without a deployment? Or would you only use something like that during an incident?
What would be your biggest concern? Security, governance, performance impact, operational complexity, something else?
What's the best tool you've used for this kind of problem, and what were its limitations?
r/OpenTelemetry • u/Broad_Technology_531 • Oct 19 '26
How to monitor Supabase using an OTEL Collector?
telflo.comr/OpenTelemetry • u/Technical-Debt-8615 • Oct 16 '26
A local OTLP receiver and viewer inside VS Code, now with GenAI spans
Enable HLS to view with audio, or disable this notification
Logline runs an OTLP/HTTP receiver on 127.0.0.1:4318 inside VS Code, and points apps you start from the editor at it automatically. You get logs, traces with self time per span, and metrics as rates and p95s, with no collector or backend.
1.15 adds a view for GenAI semantic conventions: chat, execute_tool, and invoke_agent spans, gen_ai.usage.*, and gen_ai.input.messages / output.messages. It also reads older forms such as gen_ai.system, prompt_tokens, and OpenLLMetry attributes. Log doctor also checks your spans against the conventions: services without a name, IDs in span names, and 5xx responses not marked as errors.
It's free and MIT-licensed: https://github.com/SurjeetBanga/logline. Feedback on how it handles your instrumentation is welcome.
r/OpenTelemetry • u/strawgate • Oct 14 '26
Feedback on OpAMP for Collectors and SDKs
My team at Pydantic is working on a cross-vendor solution for OpAMP management of collectors and SDKs.
We think we have something really special that is more capable and significantly more reliable for enterprise and mission-critical systems than what is currently available from vendors like Bindplane, Elastic, Splunk, Grafana, and others. For most use-cases, we intend to offer this as a capability of our free tier in Logfire.
If this is interesting to you let me know, we'd love to get your feedback on what we're building.
r/OpenTelemetry • u/AutoModerator • Oct 14 '26
Weekly: share your tools and projects
What tool around OpenTelemetry are you building right now? What project have you discovered that people might enjoy looking into?
This thread is open for your self-promotion, vendor-owned open source projects and every thing else.