Overview
Latitude can import the traces you already have in another observability platform, so you do not start from an empty project when you switch. Imports run from Project settings → Imports and finish in the background — you can close the tab.Importing is for history. Data produced from now on should arrive through
live tracing, which is what powers evaluations, monitors and
signals in real time.
Langfuse
Langfuse Cloud, using your public and secret keys.
LangSmith
Runs from a LangSmith project, with configurable session grouping.
Braintrust
Project logs, queried through BTQL.
How an import runs
1
Connect your platform
Pick the platform and the region your account is in, then enter its credentials.
Latitude tests them before continuing and discards them once the import finishes.
2
Preview
Choose the source project, the time range and how many traces to import. Latitude
shows a sample of what will come through before anything is written.
3
Start
The import runs in the background. Progress, counts and any errors appear in the
imports table, which refreshes while it runs.
What gets imported
Imported spans carry
import.* metadata (platform, source project, and the original trace
and span ids), so you can always tell imported history from live telemetry. If your
organization has a PII redaction policy, it applies to imported traces exactly as it
does to live ones.
An imported trace goes through the same pipeline as one that arrives live: it is grouped
into sessions, embedded for semantic search, indexed, and evaluated by flaggers. Because of
that it is billed the same way: one credit per trace. Re-importing the same trace does
not charge twice.
Limits
Traces are imported newest first, so an import that stops early — it reached your trace
limit or your plan’s remaining usage — keeps the most recent history rather than an
arbitrary slice. A stopped import is marked capped, everything imported stays, and
Continue resumes it from where it stopped.