# Is your Langfuse tracing working as expected?

Canonical: https://brew.new/templates/langfuse/is-your-langfuse-tracing-working-as-expected

Brand: langfuse.com
Category: onboarding

![Preview of Is your Langfuse tracing working as expected?](https://cdn.brew.new/email-preview-873b4120d64985a9-tracking_r57zvasmh69fx0kff75t9jvdxd8gmq3n-1793031738141.png)

## Email content

Hey Alex Reed,

A couple of days ago I shared how to set up tracing. Quick check: Is everything working the way you expected?

This is what a typical trace looks like, explore it in our sample project:

Four things that come up a lot:

Your traces only show LLM calls

The most common one. If you only see model calls, the instrumentation isn't wrapping the full agent run, so tool calls are missing, which is often where the interesting failures live.

Traces are flat, no nesting

A good trace of an agent with multiple steps and turns, is usually nested such that all relevant observations are grouped under the respective parent observation.

No/incorrect cost attached to generations

For good cost transparency, you want to log full info on the used model, token usage and price to each generation.

Nothing is showing up at all

Ask your coding agent to fix it:

Please install the Langfuse skill https://github.com/langfuse/skills and help me in getting to a good tracing setup.

If anything is not covered here, just hit reply, we read every message. Or book a call and we'll look at your setup together.

Best,

Marc

Co-founder, Langfuse (part of Clickhouse)

Links: Roadmap, Docs, Talk to us, Example Project

You are receiving this email because you opted in to receive email from the list Onboarding Journey from Langfuse

Langfuse, Langfuse GmbH, Oranienburger Strasse 91, 10178, Berlin, Germany

Unsubscribe

[Open and remix this design](https://brew.new/templates/langfuse/is-your-langfuse-tracing-working-as-expected)

[Browse email designs](https://brew.new/browse/templates)