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

# Map Your Data

> Map your dataset fields to Honeycomb's standard source fields manually or automatically, so visualizations like the trace waterfall work correctly.

Honeycomb automatically maps source data fields for you if you follow Honeycomb [field naming conventions](/send-data/standardize/honeycomb-dataset-fields/).
Otherwise, you must map your dataset fields manually.

## Mapping Sent Data Manually

If you have already sent data into a Honeycomb dataset or you are unable to change field names in your source data, you can use [Dataset Definitions](/configure/datasets/definitions/) to manually map the standard fields in your Honeycomb dataset to the source fields in your sent data:

1. In the left navigation menu, select **Manage Data**.
2. In the list, locate and select **Datasets**.
3. Select the name of your target dataset to access its settings.
4. Select the **Definitions** view.
5. Locate the appropriate Honeycomb **Dataset Field**, then select the source field in your data that you want to map it to from the corresponding **Field name** dropdown.
6. Select **Update**.

## Mapping Visualization Components

Honeycomb visualizations rely on fields in your source data being mapped to Honeycomb standard fields.
If you ever see an unpopulated visualization in Honeycomb, check your dataset definitions first!
Unmapped data is the main cause of visualizations missing data.

### Trace Dropdowns

Each trace chart visualization's accompanying dropdown is populated with source fields mapped to Honeycomb dataset fields.
You can [map your source fields](#mapping-sent-data-manually) to the selected dataset's fields using [Dataset Definitions](/configure/datasets/definitions/).

Dataset fields you can map include:

* **Error**: Value that indicates an error occurred.
* **HTTP Status Code**: Code that indicates the success, failure, or other status of a request.
* **Name**: Name of the function or method in which the span was created.
* **Route**: HTTP URL or equivalent route processed by the request.
* **User**: User making the request in the system.

For datasets with Kubernetes metadata, the following fields are included (if available):

* `k8s.pod.name`, `source.k8s.pod.name`, or `destination.k8s.pod.name`: Name of the Kubernetes pod.
* `k8s.container.name`, `source.k8s.container.name`, or `destination.k8s.container.name`: Name of the Kubernetes container.
* `k8s.node.name`, `source.k8s.node.name`, or `destination.node.name`: Name of the Kubernetes node.
* `k8s.namespace.name`, `source.k8s.namespace.name`, or `destination.k8s.namespace.name`: Name of the Kubernetes namespace.
* `source.k8s.service.name` or `destination.k8s.service.name`: Name of the Kubernetes service.

To learn more about sending Kubernetes data to Honeycomb, visit [Send Data from Kubernetes](/send-data/kubernetes/).

### Exceptions

Exception visualizations are populated by [OpenTelemetry Exception](https://opentelemetry.io/docs/specs/otel/trace/exceptions/) source fields. If your exception visualizations are empty, make sure you include the `exception.type` and `exception.message` fields in your instrumentation.