PandaProbe

open source agent engineering platform

905 followers

open source agent engineering platform

905 followers

Visit website

Observability tools

PandaProbe is an open-source agent engineering platform that gives you deep observability into AI agent applications. Use it to trace, evaluate, monitor and debug your AI agents in development and production.

Free

Launch tags:Open Source•Developer Tools•Artificial Intelligence

Launch Team / Built With

Framer — Launch websites with enterprise needs at startup speeds.

Launch websites with enterprise needs at startup speeds.

Promoted

Tobira.ai

Congrats on launching! How does PandaProbe handle sub-agent calls? Like if agent A spins up agent B, do both get traced under the same session tree

Report

22d ago

PandaProbe

Maker

@olia_nemirovski Thank you! Yes — they’re all captured within the same session. If a supervisor agent (A) calls a sub-agent (B), it’s treated as part of the same execution thread. The sub-agent call appears as a span within the parent trace, and that span can expand into its own nested chain of steps. So you get a unified, hierarchical view of the full interaction — making it easy to see how parent and sub-agents relate and where issues emerge.

Report

20d ago

We use LangGraph for these purposes. How is PandaProbe better and why should we switch to it?

Report

22d ago

PandaProbe

Maker

@mykyta_semenov_ That’s a great point — and to clarify, PandaProbe isn’t a replacement for LangGraph. LangGraph is for building and orchestrating agents. PandaProbe is for observing and evaluating them once they run, especially in production. If you’re already using LangGraph, PandaProbe actually plugs in on top of it. It captures traces from your workflows and then helps you: - evaluate behavior across full trajectories (not just outputs) - monitor quality and detect regressions over time - debug failures and understand what went wrong So it’s less “switch from LangGraph” and more “add a layer to understand and improve what you’ve built with it.”

Report

20d ago

We've been running Langfuse for our agent stack for about six months and the trace UI is decent, but session-level evals across multi-agent runs are still where things get messy. Curious how PandaProbe handles that. If a sub-agent fails three turns deep, do you surface root cause at the session level, or do I still have to walk the span tree manually? Also, what's the storage model look like for self-hosted? Postgres only, or something columnar for the trace volume? One more thing: any plans for OpenTelemetry-native ingestion so I don't have to swap out my existing tracing SDK across services?

Report

22d ago

Triforce Todos

Congratulations on the launch @sina_tayebati
BTW, how well does PandaProbe handle tracking regressions across different agent versions over time?

Report

22d ago

PandaProbe

Maker

@abod_rehman Thank you! Great question — this is something we designed PandaProbe to handle explicitly. You can tag traces with things like agent version, prompt version, model, or environment (prod, staging, etc.). From there, monitoring and analytics let you compare behavior across versions side by side. That makes it much easier to spot regressions or subtle drifts when you ship updates — whether it’s quality degradation, tool misuse, latency changes, or cost shifts. In practice, a lot of teams use this to validate new versions against production traffic before fully rolling them out.

Report

22d ago

Origio

Honestly the open source + self hostable combo is what makes this worth a proper look. most observability tools want you locked into their cloud and charging per seat by the time you actually need it. been burned by that before with Datadog at a startup. one instrument() call to trace the whole run is a nice dx too, gonna try this on a side project this week

Report

21d ago

PandaProbe

Maker

@shlokmestry Really appreciate that — and yeah, that exact lock-in/pricing pain is something we wanted to avoid from day one.

That’s why we made it open source + self-hostable, so teams can keep full control as they scale instead of getting boxed into per-seat or per-trace pricing later.

And glad you called out the DX — we’ve been trying to make instrumentation as lightweight as possible.

Would love to hear how it works for your side project 🙌

Report

20d ago