Langfuse icon

Langfuse

Log LLM traces, spans, generations, and scores to Langfuse, or query traces, prompts, datasets, sessions, and more via the Public API.

Actions28

Ingestion → SDK Log Create

AI-generated

Summary

Create an SDK log event in Langfuse with optional detailed metadata, timestamp, and trace association.

Inputs

  • Name — Human-readable name for the SDK log event.
  • SDK Message (required) — Message content to write to the SDK log event.
  • SDK Level (required) — Log severity level for the SDK log event; options include Debug, Info, Warn, or Error.
  • Trace ID — Trace identifier to attach this log to; if left blank and advanced fields are shown, it auto-fills from the previous step's traceId output or can be set explicitly to start or target a specific trace.
  • Event ID — Optional event ID for idempotency and deduplication of the log event.
  • Observation ID — Optional observation ID; left blank to auto-generate a new ID for create operations.
  • Parent Observation ID — Optional parent observation ID for nested logs or events.
  • Timestamp — Optional ISO 8601 timestamp for the log event; defaults to the current time if omitted.
  • Metadata JSON — Additional JSON-formatted metadata to store with the SDK log event.
  • Fail On Batch Errors — Option to fail the item when Langfuse returns partial ingestion errors.

Output shape

a single record representing the created SDK log event, including any auto-generated IDs and status information

If advanced fields are not shown, only the standard required fields can be set. Partial ingestion errors may be indicated with a 207 status; setting 'Fail On Batch Errors' to true causes the node to error in that case. The operation auto-links traceId and observationId from previous node outputs if left empty, facilitating chained event logging within the same trace.

Links

Discussion