היי טוויטר! מלחמה בחוץ אז חשבתי שזה זמן טוב לספר לכם ש-@traceloopdev, החברה ש-@GalKlm ואני הקמנו, נרכשה על-ידי ServiceNow!
איכשהו בין טיל לאזעקה נחתם היום הסכם הרכישה (סיפור משוגע בפני עצמו, שנשמור לימים רגועים יותר)
We're releasing today a cool new open source (link in the comments!)
Over the past 2 years, we've helped teams debug everything from prompt issues to production outages.
We kept running into the same problem: Jumping between our IDEs and our observability dashboards. So, we built an open-source MCP server that connects any OpenTelemetry backend (Grafana, Jaeger, Datadog, Dynatrace, Traceloop) to our dev environment using an MCP.
While there are many MCP servers built for specific providers (like Datadog and others), they’re closed source (so we can’t easily extend them), and they’re locked to a single platform, so organizations that leverage multiple platforms, where data is scattered in between them, can’t really use them.
We’re adding support for more providers every day - feel free to contribute your own.
We would love your feedback and opinions - feel free to connect it to Claude or ChatGPT and try to investigate your own production data. What do you think about the set of tools that we currently expose? Do you think we should expose more or others?
זה די משוגע. פרויקט קטן שאני וגל התחלנו כחלק מ- @traceloopdev לפני שנה ומשהו הגיע למיליון הורדות חודשיות. חברות ענק מסתמכות עליו כדי לבנות מוצרים מבוססי LLM. וכמעט 80 מפתחים מרחבי העולם עוזרים לנו לתחזק אותו ברמה היומיומית. איזה כיף
🚀 @traceloopdev launched! LLM Reliability Platform, Powered by OpenTelemetry
"Know what your AI Agent is doing — and why it’s failing."
🌐 https://t.co/xWs0QclCaB
Congrats @nir_ga@GalKlm!!
Traceloop (@traceloopdev) is bringing OpenTelemetry to LLMs — helping developers trace, debug, and improve agent workflows before they break in production.
Congrats on the launch, @nir_ga & @GalKlm!
https://t.co/3B92udtydx
We just raised $6M at @traceloopdev! 🎉 Fuel to make LLMs production-ready, not just “looks good.” Huge thanks to our investors, users & the team I build with every day.
Peek the new site ➜ https://t.co/GPBd9Wh308
Likes/RTs welcome 🙏
#AI#LLM#OpenSource
היום זה יום ממש מרגש בשבילי. אני ו-@GalKlm גייסנו 6 מיליון דולר עם @traceloopdev, הכפלנו את הצוות שלנו, ואנחנו ממשיכים לעזור למפתחים בחברות הגדולות בעולם לבנות מוצרים אמינים יותר עם AI. >>
@swyx For some reason all api gateways are written in python or ts which is a horrible decision imo. After many failed attempts of using those we’ve decided to build and open source our own in rust - https://t.co/oDAv8pE3nC
Want your LLM app to stay useful in prod? Start measuring.
Enter OpenLLMetry: OpenTelemetry + LLM Models.
Plug into OpenAI, Anthropic, LangChain, vector DBs—track tokens, cost, quality, and flow.
@GalKlm breaks down the tools and mindset you’ll need:
🎧 https://t.co/YNU8sv7LK7
#AINativeDev #DevTools #LLM
🧩 AI SDK Observability Integration: @traceloopdev
Observability and evals are crucial when developing AI applications. You can use Traceloop with the AI SDK to monitor and evaluate your LLM calls:
https://t.co/vt5X3Mc1UM
We’re collaborating with our competitors and it can actually help our business (and our users!).
Last week I met @MarcKlingen, the CEO and co-founder of @langfuse. We recently started collaborating around OpenTelemetry and OpenLLMetry with the goal of standardizing the way customers monitor their LLM-based applications. The idea is simple - to start monitoring, you need to install an SDK. This requires a lot of engineering effort across your entire stack. If you’re using a standard like OpenTelemetry, you only need to do it once. You’re then never vendor-locked to a single platform.
Mark and I are both strong believers in open source and open protocols. Both of our products are open-source based, and we win by building the best product for our users - not by locking them in our own ecosystem. By using OpenTelemetry, we will benefit from consolidating the endless effort of supporting the new advancements in the LLM world. Every day there’s a new model that needs to be supported; a new vector database; or a new breaking change to LangChain. You’ll be surprised, but a significant part of our day-to-day work is actually keeping up with changes. For me, OpenAI DevDay was more of an endless list of backlog tasks that I now need to implement rather than an exciting event (just kidding; it was also super exciting - I’ll write about it more next week).
The future is open; in my opinion, open tools will always win. I always prefer them over closed tools whenever I can. And so should you.
*In the photo: enjoying a cup of coffee at Sighglass SF