Datasets

A dataset is the top-level unit of data organization in Berserk. Each dataset is an independent collection of logs, traces, and metrics — typically representing a service, environment, or team.

Every cluster comes with a default dataset ready for ingestion. You can create additional datasets to separate data by any boundary that makes sense for your organization.

The dataset name is the first element of every query:

default
| where level == "ERROR"
| take 10

Listing Datasets

bzrk dataset list

Datasets:
  default (ID: 019ae8e5-f2aa-79c2-a0a6-41d49b609f9e)

Creating a Dataset

bzrk dataset create myapp

Created dataset: myapp
  ID: 019cd6a4-ab94-7a90-bcc1-c380ae443daf

Ingest Tokens

An ingest token authenticates an OpenTelemetry Collector and routes its data to a specific dataset. Each dataset can have multiple ingest tokens (e.g., one per collector or environment), but each token is bound to exactly one dataset.

Creating an Ingest Token

bzrk ingest-token create --dataset myapp my-ingest-token

Created ingest token: my-ingest-token
  ID: 019cd6a6-5fe5-7a80-be74-9dba27894af8
  Dataset: myapp

  Token: ing_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  Save this token now — it cannot be retrieved again.

Listing Ingest Tokens

bzrk ingest-token list --dataset myapp

Querying a Dataset

bzrk search "myapp | take 10" --since "1h ago"

See Query Reference for the full query language reference.