Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add serveless faq #1050

Merged
merged 1 commit into from
Dec 2, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions pages/faq/all/aws-lambda-and-serverless-functions.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
title: How to use Langfuse Tracing in Serverless Functions (AWS Lambda, Vercel, Cloudflare Workers, etc.)
tags: [setup, tracing]
---

# How to use Langfuse Tracing in Serverless Functions (AWS Lambda, Vercel, Cloudflare Workers, etc.)

Langfuse Tracing is optimized to run in the background in order to avoid adding latency to an application. This can cause some difficulties when tracing in serverless environments like AWS Lambda, Vercel Functions, Google Cloud Functions, etc.

The behavior of the Langfuse clients is outlined [here](/docs/tracing).

## What is the root cause of this issue?

The root cause of this issue is that serverless functions are typically short-lived and terminate after execution. This means that the Langfuse agent, which runs in the background, may not have enough time to complete its work before the function exits. Thereby, events might not be sent to Langfuse.

## Use `flush` to ensure events are sent before the function exits

To solve this issue, you can manually flush the events before the function exits. This can be done by calling the `flush` method of the Langfuse client. The flush method is supported across all Langfuse SDKs and integrations.

## Alternative: waitUntil

Vercel and Cloudflare Workers support the [`waitUntil`](https://developer.mozilla.org/en-US/docs/Web/API/ExtendableEvent/waitUntil) method, which allows you to wait for a promise (`flush`) to resolve before the function exits. Thereby you can return a value from your function and still ensure that events are sent to Langfuse.

## Alternative: flushAt

Alternatively, you can configure Langfuse to flush events individually. This can be done by setting the `flushAt` option to a specific number of events.