openlayer export command downloads monitoring data from an inference pipeline
for a specified time period.
It supports flexible ways to specify date ranges and optional filters to refine the
exported dataset.
Usage
dataset.json and config.json file in ./openlayer-exports/{pipeline_name}_{start}_{end}.
Date ranges
You can specify time ranges in multiple ways:Filters
You can refine the exported dataset using--filter flags or a JSON file.
Simple syntax
JSON file (advanced)
For more complex filters, pass a JSON file:Output format
--format (or -f) controls the file format of the exported data:
Test scores
By default the export contains no score columns. Pass--include-scores all to add each
test’s score and explanation as columns:
openlayer_llm_rubric_score_78812226. The hash keeps two tests that share a name in
separate columns, and changing an evaluator starts a new column.
When an export contains score columns, config.json includes metricColumns. This applies
to all-scores exports and to exports that include score columns through filters. Each entry
maps a hashed column to its test name and test id:
scoreColumn is the column name in the exported rows. An entry can include additional test
metadata. Session-level LLM judge columns and columns created by an evaluator’s earlier
configuration may not have a mapping.
The same config.json file lists the columns actually written to the data files under
columnNames: base columns first, followed by sorted score and explanation columns. For
split CSV exports, this list matches the headers across all data_partNNNN.csv files.
Combining
--format csv with --include-scores all splits the output into
several data_partNNNN.csv files instead of a single file. The CLI prints a
note when it does.