Skip to main content
To get the most out of Honeycomb visualizations, you will need to map some of the source fields in your sent data to Honeycomb-specific standard dataset fields. Different dataset fields are available depending on the type of dataset you are sending to Honeycomb.

​
Trace Datasets

Honeycomb will identify a dataset as a trace dataset, if you either:
  • send a source field named trace.trace_id to Honeycomb, or
  • manually map a source field to the Trace ID dataset field in the dataset’s Dataset Definitions.

​
Available Fields

You can map the following dataset fields for a trace dataset:
To allow Honeycomb to detect and map dataset fields automatically, name the data field you send to Honeycomb the value listed in the Source Field Name column.To learn how to map dataset fields manually, visit Map Data.
Dataset FieldDescriptionAllowed Type(s)Source Field NameCan Group By?
ErrorValue that indicates an error occurred. Used to identify errors when calculating the “Total Spans with Errors” visualizations.boolean, string, calculated fielderrorYes
HTTP Status CodeCode that indicates the success, failure, or other status of a request.string, integer, float, calculated fieldresponse.status_codeYes
Metadata: Annotation TypeType of the span annotation, which controls how Honeycomb visualizes this event in a trace. Possible values include span_event (indicates the span is a span event) and link (indicates the span is a span link).string, calculated fieldmeta.annotation_typeNo
Metadata: Link Span IDUnique ID of the span you want to link to the current span. Indicates the span is a span event. Use with Metadata: Link Trace ID.string, calculated fieldtrace.link.span_idNo
Metadata: Link Trace IDUnique ID of the trace you want to link to the current span. Use with Metadata: Link Span ID.string, calculated fieldtrace.link.trace_idNo
NameName of the function or method in which the span was created.string, calculated fieldnameYes
Parent span IDID of the span’s parent span, which is the location from which the span was called.string, calculated fieldparent_idNo
RouteHTTP URL or equivalent route processed by the request.string, calculated fieldNot automatically mappedYes
Service nameName of the instrumented service.string, calculated fieldservice.nameNo
Span durationLength of time the span took in milliseconds (ms). Used to calculate the “95th Percentile Latency” visualizations.float, integer, calculated fieldduration_ms or durationMsNo
Span IDUnique ID of the span.string, calculated fieldspan_idNo
Trace IDUnique ID of the trace to which the span belongs.string, calculated fieldtrace.trace_idNo
UserUser making the request in the system.float, string, integer, calculated fieldNot automatically mappedYes

​
Log Datasets

For Honeycomb to identify a dataset as a logs dataset, either:
  • send a source field named body to Honeycomb, or
  • manually map a source field to the Log Message dataset field in the dataset’s Dataset Definitions.

​
Available Fields

You can map the following dataset fields for a log dataset:
To allow Honeycomb to detect and map dataset fields automatically, name the data field you send to Honeycomb the value listed in the Source Field Name column.To learn how to map dataset fields manually, visit Map Data.
Dataset FieldDescriptionAllowed Type(s)Source Field Name
Log MessageValue containing the log event message. May be a human-readable string message (including multiline) describing the event in free form.string, calculated fieldbody
Log SeveritySeverity level of the event (also known as log level). Supported values include: trace, debug, info, warn, error, fatal, and unspecified.string, calculated fieldseverity