Honeycomb automatically maps source data fields for you if you follow Honeycomb field naming conventions. Otherwise, you must map your dataset fields 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 to manually map the standard fields in your Honeycomb dataset to the source fields in your sent data:
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.
Each trace chart visualization’s accompanying dropdown is populated with source fields mapped to Honeycomb dataset fields. You can map your source fields to the selected dataset’s fields using Dataset Definitions.
Dataset fields you can map include:
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.
Exception visualizations are populated by OpenTelemetry Exception source fields. If your exception visualizations are empty, make sure you include the exception.type
and exception.message
fields in your instrumentation.