Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

This week metrics and logs join traces in Mastra Studio. • Logs: every event, searchable with full context • Traces: debug any run, end to end • Metrics: cost, latency, errors, and scores at a glance With all three pillars of observability in one place, you can now see... show more

🏴󠁧󠁢󠁥󠁮󠁧󠁿 Paul

2,951 subscribers

10,509 Aufrufe • vor 6 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

[2/5] Introducing Automation Studio 🪩 A dedicated IDE to craft, debug, and deploy browser agents and automations end-to-end. Write code and watch every step in real time with breakpoints and rich logs to fix issues instantly. Editor, live browser, and logs in one place. No context switching, faster iteration.

[2/5] Introducing Automation Studio 🪩 A dedicated IDE to craft, debug, and deploy browser agents and automations end-to-end. Write code and watch every step in real time with breakpoints and rich logs to fix issues instantly. Editor, live browser, and logs in one place. No context switching, faster iteration.

Notte

14,040 Aufrufe • vor 9 Monaten

You can now filter workflow logs to easily view all logs for a workflow run in one place. Jump directly from a run to logs, filter by steps, and quickly find relevant requests.

You can now filter workflow logs to easily view all logs for a workflow run in one place. Jump directly from a run to logs, filter by steps, and quickly find relevant requests.

Vercel Developers

15,146 Aufrufe • vor 5 Monaten

Today, we're making Error Tracking by Better Stack generally available. Sentry-compatible. AI-native. At 1/6th the price. Here's why we built it, and how to get the most out of it. What's wrong with error tracking today? Most teams use Sentry. It's solid! But at scale, the bills get brutal. Just 100M exceptions with 90 day lookback? ~$30,000 on Sentry. We charge ~$5,000 for the exact same thing. The math isn't subtle. And so most teams still end up sampling. Which means missing the exact exception that caused the outage. The bigger problem: errors are orphaned data. Your exception lands in Sentry. Your logs are in Datadog. Your traces are somewhere else. Root cause analysis becomes a multi-tab archaeology project at 3 am. We built error tracking natively inside Better Stack: the same platform where your logs, traces, metrics, uptime checks, and on-call schedules already live. Errors are just another signal. They belong together. The part that changes how your team works: Our AI SRE doesn't just surface errors. It fixes them. See a new exception? One click. The AI SRE analyzes the full context, from stack traces, environment variables, browser sessions, related logs and recent deploys, and opens a pull request. Not a ticket. Not a summary. A pull request with the fix. This is what happens when error tracking is fully integrated with the rest of your observability stack instead of bolted on separately. The AI has everything it needs to actually act. The migration is trivial: 1. Keep your existing Sentry SDK. Don't touch a single line of instrumentation code. 2. Point the DSN at Better Stack. 3. Done. Errors flow in. Your dashboards work. Your alerts work. 4. New exception appears. Click "Fix with AI SRE." Pull request lands in your repo. 5. Review, merge, close. That's the whole workflow. The AI angle is real, not a marketing badge. LLMs are genuinely good at fixing bugs if they have full context. The reason AI coding assistants sometimes frustrate engineers is incomplete information, not the model. We solve that by giving the AI SRE your entire telemetry stack as context. Stack traces, logs, traces, service maps, previous incidents and much more. All of it, in one place, at the moment it matters. Observability tools are only useful if you actually ingest all your data. At current prices of other tools, most teams can't afford to. Now you can, and your AI SRE can actually do something about it.

Today, we're making Error Tracking by Better Stack generally available. Sentry-compatible. AI-native. At 1/6th the price. Here's why we built it, and how to get the most out of it. What's wrong with error tracking today? Most teams use Sentry. It's solid! But at scale, the bills get brutal. Just 100M exceptions with 90 day lookback? ~$30,000 on Sentry. We charge ~$5,000 for the exact same thing. The math isn't subtle. And so most teams still end up sampling. Which means missing the exact exception that caused the outage. The bigger problem: errors are orphaned data. Your exception lands in Sentry. Your logs are in Datadog. Your traces are somewhere else. Root cause analysis becomes a multi-tab archaeology project at 3 am. We built error tracking natively inside Better Stack: the same platform where your logs, traces, metrics, uptime checks, and on-call schedules already live. Errors are just another signal. They belong together. The part that changes how your team works: Our AI SRE doesn't just surface errors. It fixes them. See a new exception? One click. The AI SRE analyzes the full context, from stack traces, environment variables, browser sessions, related logs and recent deploys, and opens a pull request. Not a ticket. Not a summary. A pull request with the fix. This is what happens when error tracking is fully integrated with the rest of your observability stack instead of bolted on separately. The AI has everything it needs to actually act. The migration is trivial: 1. Keep your existing Sentry SDK. Don't touch a single line of instrumentation code. 2. Point the DSN at Better Stack. 3. Done. Errors flow in. Your dashboards work. Your alerts work. 4. New exception appears. Click "Fix with AI SRE." Pull request lands in your repo. 5. Review, merge, close. That's the whole workflow. The AI angle is real, not a marketing badge. LLMs are genuinely good at fixing bugs if they have full context. The reason AI coding assistants sometimes frustrate engineers is incomplete information, not the model. We solve that by giving the AI SRE your entire telemetry stack as context. Stack traces, logs, traces, service maps, previous incidents and much more. All of it, in one place, at the moment it matters. Observability tools are only useful if you actually ingest all your data. At current prices of other tools, most teams can't afford to. Now you can, and your AI SRE can actually do something about it.

Juraj Masar

15,134 Aufrufe • vor 6 Monaten

A production issue shouldn't require a detective Yet that's how most observability works today Most observability tools just dump alerts. Duplicates, no context, and you still fix it yourself Nicolò Magnante (YC P26) and his cofounder Arseniy Shishaev (YC P26) - who spent years building part of Datadog's metrics product - think that's backwards So they built Superlog (YC P26): Observability that's meant never to be opened A wizard scans your repo, installs proper OpenTelemetry, and runs daily to keep up as you ship When something breaks, it groups the errors into one incident, investigates with full context - logs, traces, recent deploys, past Slack threads - and drops a single mergeable PR in Slack. Merge it Ignore it Or open it in Claude Code and tweak it Vendor-neutral, so you keep every log, trace, and metric - even if you leave Not another notification. A fix. Nicolò Magnante (YC P26) CEO & Co-Founder Superlog (YC P26) on Fondo.com START Huge thanks to Eragon for making this episode possible!

A production issue shouldn't require a detective Yet that's how most observability works today Most observability tools just dump alerts. Duplicates, no context, and you still fix it yourself Nicolò Magnante (YC P26) and his cofounder Arseniy Shishaev (YC P26) - who spent years building part of Datadog's metrics product - think that's backwards So they built Superlog (YC P26): Observability that's meant never to be opened A wizard scans your repo, installs proper OpenTelemetry, and runs daily to keep up as you ship When something breaks, it groups the errors into one incident, investigates with full context - logs, traces, recent deploys, past Slack threads - and drops a single mergeable PR in Slack. Merge it Ignore it Or open it in Claude Code and tweak it Vendor-neutral, so you keep every log, trace, and metric - even if you leave Not another notification. A fix. Nicolò Magnante (YC P26) CEO & Co-Founder Superlog (YC P26) on Fondo.com START Huge thanks to Eragon for making this episode possible!

David J Phillips

40,983 Aufrufe • vor 4 Monaten

I just built this CRACKED Cursor MCP extension that makes your IDE fully aware of all the logs in your browser. Was struggling with a few issues recently and kept having to copy/paste logs but with this tool you can: ✅ Check all console logs + errors ✅ Analyze network requests, responses and errors ✅ Make changes to a selected element in your browser ✅ Take screenshots of your browser ... without EVER having to leave your IDE 🦾 Open source, FREE and compatible with Cursor, Cline, Continue and Zed. Link to the docs with setup instructions down below 👇

I just built this CRACKED Cursor MCP extension that makes your IDE fully aware of all the logs in your browser. Was struggling with a few issues recently and kept having to copy/paste logs but with this tool you can: ✅ Check all console logs + errors ✅ Analyze network requests, responses and errors ✅ Make changes to a selected element in your browser ✅ Take screenshots of your browser ... without EVER having to leave your IDE 🦾 Open source, FREE and compatible with Cursor, Cline, Continue and Zed. Link to the docs with setup instructions down below 👇

Ted Werbel

179,971 Aufrufe • vor 1 Jahr

Heres how to get started with the neatlogs MCP ! with this you can access your traces, detections, complete RCA and traige cards right inside Claude Code, Cursor, Windsurf, or whichever you like to build and you dont need to jump between your editor and a bunch of dashboards, you can just debug and fix your agents in one place. :)

Heres how to get started with the neatlogs MCP ! with this you can access your traces, detections, complete RCA and traige cards right inside Claude Code, Cursor, Windsurf, or whichever you like to build and you dont need to jump between your editor and a bunch of dashboards, you can just debug and fix your agents in one place. :)

simran sachdeva

24,742 Aufrufe • vor 3 Monaten

Your agents can now browse and take actions on the web, just like you can. This lets agents work with sites that don’t have APIs and still complete tasks end to end. Plus, each interaction is streamed live to Studio.

Your agents can now browse and take actions on the web, just like you can. This lets agents work with sites that don’t have APIs and still complete tasks end to end. Plus, each interaction is streamed live to Studio.

Mastra

16,848 Aufrufe • vor 5 Monaten

Watch Cursor control my browser. It can see what's happening, including network and console logs. Now my Cursor can debug and fix web site problems without any copy-pasta. HUGE speed up for web dev - with this Cursor can compete with v0 and replit at autonomous web app dev. This is Open Source and published now on npm: cursor-tools@alpha Full prompts in thread

Watch Cursor control my browser. It can see what's happening, including network and console logs. Now my Cursor can debug and fix web site problems without any copy-pasta. HUGE speed up for web dev - with this Cursor can compete with v0 and replit at autonomous web app dev. This is Open Source and published now on npm: cursor-tools@alpha Full prompts in thread

Andrew Jefferson

346,384 Aufrufe • vor 1 Jahr

did Cloudflare leave the best for last? guess we'll find out tomorrow agent week is almost over and I am still catching up on all the announcements one thing that i wanted to take for a spin was Computer. you shouldn't need a full on VM container to spin up a git repo and read and edit some files. and if you want to test something in a browser, you can now use Kitesurf having this kind of control when building agent harnesses is very cool, from permission management, separating the brain from the hands and performance gains from isolation, im super stoked for where this goes i wanted to see if i can build a Buzz-like environment using Cloudflare primitives, i called it Cuzz. and being able to observe and debug agent activity locally using Sentry helps make sure i can see not just my agent traces, but errors, logs and traces from the rest of my application what was your favourite announcement from Agent Week?

did Cloudflare leave the best for last? guess we'll find out tomorrow agent week is almost over and I am still catching up on all the announcements one thing that i wanted to take for a spin was Computer. you shouldn't need a full on VM container to spin up a git repo and read and edit some files. and if you want to test something in a browser, you can now use Kitesurf having this kind of control when building agent harnesses is very cool, from permission management, separating the brain from the hands and performance gains from isolation, im super stoked for where this goes i wanted to see if i can build a Buzz-like environment using Cloudflare primitives, i called it Cuzz. and being able to observe and debug agent activity locally using Sentry helps make sure i can see not just my agent traces, but errors, logs and traces from the rest of my application what was your favourite announcement from Agent Week?

Serge

14,865 Aufrufe • vor 2 Monaten

Production-ready RAG systems need observability. From tracking latency and throughput to evaluating response quality with human feedback or LLM-as-a-judge, robust observability gives you visibility into both system performance and output quality, on both a component and system-wide level. This lesson from our Retrieval Augmented Generation course breaks down the core components of an effective eval system and how to balance cost, automation, and accuracy when choosing your metrics. 📚 Learn more in the full course:

Production-ready RAG systems need observability. From tracking latency and throughput to evaluating response quality with human feedback or LLM-as-a-judge, robust observability gives you visibility into both system performance and output quality, on both a component and system-wide level. This lesson from our Retrieval Augmented Generation course breaks down the core components of an effective eval system and how to balance cost, automation, and accuracy when choosing your metrics. 📚 Learn more in the full course:

DeepLearning.AI

18,793 Aufrufe • vor 8 Monaten

Introducing Screener Insights! Through this feature, we have brought the business metrics that actually help you understand a company - beyond its financials. Track historical trends and future estimates of critical industry metrics - all in one place.

Introducing Screener Insights! Through this feature, we have brought the business metrics that actually help you understand a company - beyond its financials. Track historical trends and future estimates of critical industry metrics - all in one place.

Screener.in

37,494 Aufrufe • vor 6 Monaten

Debugging agents shouldn’t feel like detective work. Today, we’re excited to release two new AI agent interfaces that make agent observability & evaluations even more effective. 🔎 Timeline View – See execution flow and bottlenecks at a glance. No more guessing where your agent gets stuck. 💬 Conversation View – Experience exactly what your users see. Debug from the user's perspective, not just the system's. Combined with last week's Graph View, you now have three complementary ways to debug your agents: → Graph: Visualize decision paths and tool usage → Timeline: Spot performance bottlenecks instantly → Conversation: See the user experience end-to-end AI evaluations + observability are crucial to building reliable AI. These interfaces make it simpler to identify blockers and improve your agents faster. See all three views in action, and try it free with the link below 👇

Debugging agents shouldn’t feel like detective work. Today, we’re excited to release two new AI agent interfaces that make agent observability & evaluations even more effective. 🔎 Timeline View – See execution flow and bottlenecks at a glance. No more guessing where your agent gets stuck. 💬 Conversation View – Experience exactly what your users see. Debug from the user's perspective, not just the system's. Combined with last week's Graph View, you now have three complementary ways to debug your agents: → Graph: Visualize decision paths and tool usage → Timeline: Spot performance bottlenecks instantly → Conversation: See the user experience end-to-end AI evaluations + observability are crucial to building reliable AI. These interfaces make it simpler to identify blockers and improve your agents faster. See all three views in action, and try it free with the link below 👇

Galileo, now part of Cisco

499,481 Aufrufe • vor 1 Jahr

Every single walk-off this season ... all in one place. (And yes, you know which one is at the end 🔥)

Every single walk-off this season ... all in one place. (And yes, you know which one is at the end 🔥)

MLB

265,191 Aufrufe • vor 1 Jahr

messed around to see if you can add full forensic tracing with nothing but a helius endpoint turns out you can this traces all historical txs for a wallet, all wallets it interacted with, and lets you filter by token/amount/date — with no indexer insane

messed around to see if you can add full forensic tracing with nothing but a helius endpoint turns out you can this traces all historical txs for a wallet, all wallets it interacted with, and lets you filter by token/amount/date — with no indexer insane

mert

28,460 Aufrufe • vor 7 Monaten

New in Chrome DevTools: Annotate performance findings with Gemini! You can now ask Gemini to explain performance traces. Specifically you can generate annotations about events in the performance trace. This is a total game-changer. Double-click an event in the Main track, then click Generate label next to the input field. Gemini can suggest a label based on the stack trace and context. Try it out and let us know what you think!

New in Chrome DevTools: Annotate performance findings with Gemini! You can now ask Gemini to explain performance traces. Specifically you can generate annotations about events in the performance trace. This is a total game-changer. Double-click an event in the Main track, then click Generate label next to the input field. Gemini can suggest a label based on the stack trace and context. Try it out and let us know what you think!

Addy Osmani

88,311 Aufrufe • vor 1 Jahr

🔗 New LangChain Academy Course: Introduction to LangChain (Python) 🔗 Learn how to build with LangChain – our open source framework that makes it easy to start building agents with any model provider. In this course, you’ll create agents that can reason, use tools, and take action, and learn how to debug their behavior with LangSmith. Along the way, you’ll: - Build an agent with the `create_agent` abstraction - Use LangChain’s core building blocks: Models, Messages, Memory, and Tools - Customize your agent with middleware - Debug your agent with LangSmith Observability & Studio By the end of the course, you’ll have assembled a full team of personal assistants. Enroll for free ➡️

🔗 New LangChain Academy Course: Introduction to LangChain (Python) 🔗 Learn how to build with LangChain – our open source framework that makes it easy to start building agents with any model provider. In this course, you’ll create agents that can reason, use tools, and take action, and learn how to debug their behavior with LangSmith. Along the way, you’ll: - Build an agent with the `create_agent` abstraction - Use LangChain’s core building blocks: Models, Messages, Memory, and Tools - Customize your agent with middleware - Debug your agent with LangSmith Observability & Studio By the end of the course, you’ll have assembled a full team of personal assistants. Enroll for free ➡️

LangChain

41,214 Aufrufe • vor 9 Monaten

💥 OSS product analytics for LLM apps. Launching PostHog x langfuse.com integration 🤝 🫳 Day 1 drop of Langfuse Launch Week: We’re marrying product analytics and LLM observability. This integration pipes Langfuse events/metrics/evals into your PostHog project. This allows you to access all of your LLM metrics straight from your Posthog dashboards. I've used it to reality-check our evaluations by correlating them with user retention and ingestion metrics that we already measure in PostHog. This integration is now in public-beta and you can enable it within your Langfuse project settings. Thank you james hawkins, timgl and Lior Neu-ner for working on this over the past couple of weeks and to everyone who joined the private beta. More details: Quick tour of the integration 👇

💥 OSS product analytics for LLM apps. Launching PostHog x langfuse.com integration 🤝 🫳 Day 1 drop of Langfuse Launch Week: We’re marrying product analytics and LLM observability. This integration pipes Langfuse events/metrics/evals into your PostHog project. This allows you to access all of your LLM metrics straight from your Posthog dashboards. I've used it to reality-check our evaluations by correlating them with user retention and ingestion metrics that we already measure in PostHog. This integration is now in public-beta and you can enable it within your Langfuse project settings. Thank you james hawkins, timgl and Lior Neu-ner for working on this over the past couple of weeks and to everyone who joined the private beta. More details: Quick tour of the integration 👇

Marc Klingen

15,676 Aufrufe • vor 2 Jahren

Introducing: Sazabi (Sazabi). The AI-native observability platform for fast moving engineering teams. Backed by engineering leaders from the world's top AI and dev tool companies: Graphite, Vercel, Browserbase, LangChain, Browserbase, and more. Sazabi is taking a radically different approach to observability, centered on three core principles: 1. LESS IS MORE Product engineers don't need more observability bells and whistles. They need clear, actionable answers. The best UX for observability is chat. 2. LOGS ARE ALL YOU NEED The "Three Pillars of Observability" is an outdated idea. Logs can do everything traces can do, and more. 3. MONITORING IS DEAD Creating static monitors for fast-evolving systems is a fool's errand. The future is something different entirely: agentic anomaly detection. I started Sazabi out of desperation. After years of working on observability systems at Crunchbase, Brex, and 11x, I was all too familiar with the toil and complexity. Dashboards. Monitors. Session recordings. Error tracking. APM. RUM. Instrumentation. OpenTelemetry. Endless screens and configuration. It was too much. And despite everything, my teams still struggled to find and fix production issues. I was fed up. I dreamed about a better way. AI makes it possible. Today, I'm proud to introduce Sazabi to the world and announce our closed alpha program. We're selecting 10 startups to participate. Learn more:

Introducing: Sazabi (Sazabi). The AI-native observability platform for fast moving engineering teams. Backed by engineering leaders from the world's top AI and dev tool companies: Graphite, Vercel, Browserbase, LangChain, Browserbase, and more. Sazabi is taking a radically different approach to observability, centered on three core principles: 1. LESS IS MORE Product engineers don't need more observability bells and whistles. They need clear, actionable answers. The best UX for observability is chat. 2. LOGS ARE ALL YOU NEED The "Three Pillars of Observability" is an outdated idea. Logs can do everything traces can do, and more. 3. MONITORING IS DEAD Creating static monitors for fast-evolving systems is a fool's errand. The future is something different entirely: agentic anomaly detection. I started Sazabi out of desperation. After years of working on observability systems at Crunchbase, Brex, and 11x, I was all too familiar with the toil and complexity. Dashboards. Monitors. Session recordings. Error tracking. APM. RUM. Instrumentation. OpenTelemetry. Endless screens and configuration. It was too much. And despite everything, my teams still struggled to find and fix production issues. I was fed up. I dreamed about a better way. AI makes it possible. Today, I'm proud to introduce Sazabi to the world and announce our closed alpha program. We're selecting 10 startups to participate. Learn more:

Sherwood

117,900 Aufrufe • vor 8 Monaten

With Opus 4.7 out, I wanted to remind you that there is an official Supabase connector, and it is the easiest way to add a backend to your app! You can - Run SQL - Create database migrations - Deploy Edge Functions - Access logs to debug - Fetch the security advisor output All while chatting with it!

With Opus 4.7 out, I wanted to remind you that there is an official Supabase connector, and it is the easiest way to add a backend to your app! You can - Run SQL - Create database migrations - Deploy Edge Functions - Access logs to debug - Fetch the security advisor output All while chatting with it!

Tyler Shukert

26,531 Aufrufe • vor 5 Monaten