> For the complete documentation index, see [llms.txt](https://docs.zenml.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenml.io/kitaru/import-your-traces.md).

# Import your traces

- [Overview](https://docs.zenml.io/kitaru/import-your-traces/import-your-traces.md): Bring the traces you already collect. Langfuse stays your system of record, Kitaru gets a runnable copy.
- [Post-import insights](https://docs.zenml.io/kitaru/import-your-traces/post-import-insights.md): Generate insights after an import on a local, self-hosted, or managed Kitaru server.
- [Langfuse](https://docs.zenml.io/kitaru/import-your-traces/import-langfuse-traces.md): Langfuse JSONL imports end to end: the accepted export, dedup semantics, and how imports execute on your worker.
- [LangSmith](https://docs.zenml.io/kitaru/import-your-traces/import-langsmith-traces.md): Turn LangSmith runs into replayable Kitaru sessions: the accepted export shapes, how threads group into sessions, dedup semantics, and what the importer cannot recover.
- [Braintrust](https://docs.zenml.io/kitaru/import-your-traces/import-braintrust-traces.md): Import Braintrust project logs into Kitaru: accepted export shapes, how spans become nodes, multi-turn grouping, and what the importer marks as lossy.
- [Logfire](https://docs.zenml.io/kitaru/import-your-traces/import-logfire-traces.md): Import Pydantic Logfire records-query exports into Kitaru: accepted export shapes, how OpenTelemetry GenAI spans become nodes, conversation grouping, and what the importer marks as lossy.
- [Arize Phoenix](https://docs.zenml.io/kitaru/import-your-traces/import-phoenix-traces.md): Import Arize Phoenix trace exports into Kitaru: supported UI and CLI files, span mapping, source identity, and known limits.
- [MLflow](https://docs.zenml.io/kitaru/import-your-traces/import-mlflow-traces.md): Import MLflow traces into Kitaru: accepted export shapes, how MLflow spans become nodes, session grouping, fetching from a tracking server, and what the importer marks as lossy.
- [Kitaru JSONL](https://docs.zenml.io/kitaru/import-your-traces/importing-sessions.md): Import provider traces or portable Kitaru session JSONL into a workspace.
- [No importer for your format](https://docs.zenml.io/kitaru/import-your-traces/custom-importer.md): No built-in importer for your format? An importer is one Python callable: scaffold it, test it offline, register it, and your export imports like any other.
- [Provider connections](https://docs.zenml.io/kitaru/import-your-traces/provider-connections.md): Store provider credentials once on the server and let importer, analyzer, and evaluator tasks pick them up automatically, instead of setting them in every worker's environment.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zenml.io/kitaru/import-your-traces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.