SDK Overview
Pick your platform and instrument your application in minutes.
The Neatlogs SDKs capture traces, spans, token usage, and logs from your LLM application. Initialize the SDK, then use the integration mechanism documented for your library: an explicit wrapper, callback handler, processor, hook, plugin, or (where Python documents it) an auto-instrumentation key.
Pick your SDK
Python
The primary SDK — auto-instrumentation, @span decorator, trace(), log capture, and the full init() reference.
TypeScript / Node.js
Instrument Node.js backends and scripts with explicit wrappers, handlers, processors, hooks, and plugins.
Go
Instrument Go LLM apps — wrap a Google Gemini client or open spans explicitly, on an isolated private OpenTelemetry provider.
Browser
Capture traces from browser applications.
Working without an SDK? Send traces directly over HTTP — see the HTTP API reference — or point any OpenTelemetry exporter at Neatlogs over OTLP.
Configuration
Sessions
Group related traces into user or conversation sessions.
Tags
Label traces for filtering and analytics.
Workflow Name
Name your pipelines for cleaner dashboards.
Multiple Workflows
One process, many features — each its own distinct workflow.
Custom Attributes
Attach business context to spans and traces.
Prompt Templates
Track prompt template versions across traces.
PII Redaction
Scrub sensitive data before it leaves your app.
Flush and Shutdown
Drain telemetry safely in scripts, servers, workers, streams, and tests.