Skip to content

Commit

Permalink
docs: add missing trace faq to datasets
Browse files Browse the repository at this point in the history
Fixes: LFE-1284
  • Loading branch information
marcklingen committed Jun 1, 2024
1 parent e2422f2 commit 4d84420
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 2 deletions.
6 changes: 6 additions & 0 deletions pages/docs/datasets/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -369,3 +369,9 @@ direction LR
comment
}
```

## FAQ

import { FaqPreview } from "@/components/faq/FaqPreview";

<FaqPreview tags={["datasets"]} />
4 changes: 2 additions & 2 deletions pages/faq/all/missing-traces.mdx
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: I have setup Langfuse, but I do not see any traces in the dashboard. How to solve this?
tags: [setup, tracing]
tags: [setup, tracing, datasets]
---

# I have setup Langfuse, but I do not see any traces in the dashboard. How to solve this?
Expand All @@ -11,7 +11,7 @@ Langfuse runs all tracing integrations asynchronously ([learn more](/docs/tracin
2. **Check API Credentials**: Make sure that the API credentials used in your application match those created in your Langfuse project settings.
3. **Inspect Tracing Configuration**: Ensure that your tracing configuration is correctly set up. For example, verify that the `LANGFUSE_HOST` (Python) or `LANGFUSE_BASEURL` (JS/TS) is set to the correct endpoint.
4. **Review Logs**: Check the logs of your application to see if there are any errors related to Langfuse. This can help identify issues with the integration or network connectivity. Optionally, you can enable debug logging to get more detailed information.
5. **Manual Flushing**: If you are using short-lived applications like serverless functions, ensure that you are manually flushing the events before the application exits. This is important to avoid losing events. Read more on this [here](/docs/tracing).
5. **Manual Flushing**: If you are using short-lived applications like serverless functions, local batch scripts or Jupyter Notebooks, ensure that you are manually flushing the events before the application exits. This is important to avoid losing events. Read more on this [here](/docs/tracing).
6. **Network Issues**: Check for any network issues that might be preventing your application from sending data to Langfuse. Ensure that your firewall or network settings allow outbound connections to Langfuse endpoints.
7. **Batching Configuration**: In high throughput applications, verify the batching configuration to ensure that events are being sent in a timely manner. You can adjust the `flushAt` and `flushInterval` settings to suit your needs.

Expand Down

0 comments on commit 4d84420

Please sign in to comment.