I can't see some of my traces

[MazarSayed]

I generated a report using a graph and it's trace got logged.

Then I do an api call to get the summary of the report using the technique below.
summary = self.summary_chain.invoke(text=text,config={"callbacks": [langfuse_handler],"metadata": {"langfuse_user_id": user}})

But It throws an error.

[dosubot[bot]]

I couldn't find specific information about the errors that the self.summary_chain.invoke method might throw. However, you can use the Langfuse CallbackHandler to help trace and debug the issue. The handler logs various actions, including errors, which can be useful for identifying the problem. Make sure that the langfuse_handler is correctly configured with the necessary keys and host URL. Additionally, check that the text parameter and config dictionary are correctly formatted and contain valid data. If the error persists, reviewing the logs generated by the CallbackHandler might provide more insights into the issue ^[1][2].

To continue talking to Dosu, mention @dosu.

[MazarSayed]

@dosu It's not throwing any error, but I can't see the traces. I see the traces of the report only, not the trace of the summary of the report.

I am using a single defined langfuse handler to both report and summary generation

[dosubot[bot]]

To ensure that traces for the summary generation are logged correctly, verify the following:

1. Configuration: Make sure that the langfuse_handler is properly configured with the necessary credentials (secret key, public key, and host) and that the integration is enabled. The enabled parameter should be set to true.

2. Sampling Rate: Check the sample_rate setting in your configuration. If it's set too low, some traces might not be logged.

3. Metadata: Ensure that the config dictionary for the invoke method includes the correct metadata. You can set attributes like trace_name, user_id, session_id, and tags to help identify and log the trace.

4. Telemetry: If applicable, enable telemetry by setting experimental_telemetry in the config dictionary. This can help capture additional metadata and ensure the trace is logged.

5. Troubleshooting: If traces are still not appearing, you can follow these troubleshooting steps:

   • Check the Langfuse Web logs for any errors.
   • Validate that the event was uploaded correctly to your storage.
   • Review the Langfuse Worker logs for processing errors.
   • Verify the event's presence in ClickHouse tables like traces, observations, or scores ^[1].

These steps should help in identifying why the traces for the summary generation are not appearing as expected.

To continue talking to Dosu, mention @dosu.

[marcklingen]

@MazarSayed thanks for reporting, please create an issue including the error logs and more context/code to help reproduce this