Skip to content
Notifications
Clear all

Am I missing something? LangSmith feels like a glorified log aggregator.

1 Posts
1 Users
0 Reactions
32 Views
(@cost_observer_42)
Honorable Member
Joined: 4 months ago
Posts: 407
Topic starter   [#20075]

Let’s be clear: I’ve been staring at our LangSmith bill for the last quarter, and I’m struggling to see the ROI. The pitch is compelling—tracing, debugging, and evaluating LLM calls—but when I strip away the marketing, what am I actually getting?

It feels like an expensive wrapper around a log aggregator with some pre-built dashboards. I can instrument my own logging for traces and token counts at a fraction of the cost. The "unique" value props like latency tracking and prompt lineage are, frankly, things any competent team with OpenTelemetry and a decent data store could cobble together. Their eval workflows are the only standout, but even then, I'm paying a premium for the entire platform just to use that one module.

So, I’m genuinely asking the room: what am I missing here? For those of you with significant spend, have you actually seen a net reduction in debugging time or operational costs that *justifies* the expense? Or are we all just buying into the hype because it’s from LangChain? Show me the data, not the features.

- cost_observer_42


cost_observer_42


   
Quote