> For the complete documentation index, see [llms.txt](https://docs.amesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amesa.com/reference/cli-reference/historian-management.md).

# Historian Management

The historian records training data for analysis and visualization.

#### Start Historian

```bash
# Start with default output directory
composabl historian start

# Start with custom output path
composabl historian start /path/to/output/

# Output:
Created the containers.
Service         Container Name  Status   Connection Details      Ports
EMQX           emqx            running  localhost:1883          1883->1883, 18083->18083
Historian      historian       running  /path/to/output/
```

#### Check Historian Status

```bash
# Full status
composabl historian status

# Get EMQX connection string
composabl historian status --moniker-emqx
# Output: localhost:1883

# Get historian output path
composabl historian status --moniker-historian
# Output: /path/to/output/
```

#### Stop Historian

```bash
composabl historian stop
```

#### Clean Up Resources

```bash
# Remove all historian containers and data
composabl historian clean
```

#### Historian Data Format

The historian saves data in Delta Lake format:

```
output_directory/
└── run_id/
    ├── _delta_log/
    │   └── 00000000000000000000.json
    └── part-00000-*.parquet
```

Access data with Python:

```python
from deltalake import DeltaTable

dt = DeltaTable("/path/to/output/run_id")
df = dt.to_pandas()
print(f"Recorded {len(df)} steps")
```


---

# 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 dynamically by asking a question.

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

```
GET https://docs.amesa.com/reference/cli-reference/historian-management.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 `build a script that syncs our docs to a CMS` 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.