> ## Documentation Index
> Fetch the complete documentation index at: https://docs.honeyhive.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Namespaces

> Commands in the CLI are organized into namespaces. Explore the namespaces below to learn more about each command.

<CardGroup cols={2}>
  <Card title="Alerts" href="/v2/cli-reference/ref/alerts">
    Define and manage alerts. Alerts evaluate event metrics on a schedule and trigger notifications when configured thresholds are crossed. (3 commands)
  </Card>

  <Card title="Charts" href="/v2/cli-reference/ref/charts">
    Define and manage saved charts. Charts are visualizations that aggregate metrics over time with bucketing, filters, and groupings. (5 commands)
  </Card>

  <Card title="Data Plane Api Keys" href="/v2/cli-reference/ref/data-plane-api-keys">
    Create fine-grained data plane API keys for a project from a provisioning flow, using an organization-rooted key that is permitted to create keys. (1 command)
  </Card>

  <Card title="Datapoints" href="/v2/cli-reference/ref/datapoints">
    Manage individual records inside datasets, including batch creation and mapping to source events. (6 commands)
  </Card>

  <Card title="Datasets" href="/v2/cli-reference/ref/datasets">
    Curate collections of datapoints used as test sets for evaluations and experiments. (6 commands)
  </Card>

  <Card title="Events" href="/v2/cli-reference/ref/events">
    Read and write trace events. Events are the spans that capture every step of an AI application's execution. (5 commands)
  </Card>

  <Card title="Experiments" href="/v2/cli-reference/ref/experiments">
    Run, retrieve, and compare evaluation runs to measure how prompt or configuration changes affect agent performance. (11 commands)
  </Card>

  <Card title="Ingestion Api Keys" href="/v2/cli-reference/ref/ingestion-api-keys">
    Create ingestion API keys for a project from a provisioning flow, using an organization-rooted data plane key that is permitted to create keys. An ingestion key is the credential an application sends traces with. (1 command)
  </Card>

  <Card title="Metric Versions" href="/v2/cli-reference/ref/metric-versions">
    Snapshot, list, and deploy versions of a metric's definition so changes can be reviewed and rolled back without losing history. (3 commands)
  </Card>

  <Card title="Metrics" href="/v2/cli-reference/ref/metrics">
    Define and run evaluators, i.e. automated quality checks that score traces against criteria like accuracy, safety, or correctness. (5 commands)
  </Card>

  <Card title="Projects" href="/v2/cli-reference/ref/projects">
    Create and manage projects within a workspace. A project is the container for the events, datasets, evaluations, and alerts logged against it. (4 commands)
  </Card>

  <Card title="Sessions" href="/v2/cli-reference/ref/sessions">
    Group related trace events into sessions, the top-level container for a multi-step or multi-service AI interaction. (2 commands)
  </Card>

  <Card title="Virtual Dataplanes" href="/v2/cli-reference/ref/virtual-dataplanes">
    Create and manage virtual data planes. A virtual data plane is a logical tenant boundary inside an organization, hosted on a physical cluster; several virtual data planes commonly share one cluster. Workspaces live inside a virtual data plane. (4 commands)
  </Card>

  <Card title="Workspaces" href="/v2/cli-reference/ref/workspaces">
    Read and manage workspaces. A workspace groups the projects belonging to one team or environment, and owns the API keys and AI provider secrets its projects share. (4 commands)
  </Card>
</CardGroup>


## Related topics

- [Namespaces](/v2/sdk-reference/typescript/ref/namespaces.md)
- [Schema Reference](/v2/tracing/enrichment-schema.md)
- [How to Enrich Traces with Metadata and Metrics](/v2/tracing/enrich-traces.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.