The use of the field
meta.span_type to identify Span Events and Span Links (hereafter called Span Annotations) is deprecated and will be removed in an upcoming release. Note that this only applies to using the field
meta.span_type to identify Span Annotations.
Note: this only applies to you if you are using the field named
meta.span_type for annotations, if you are using the field for your own use, you can disregard this.
What deprecation means
Datasets that use the field meta.span_type to identify Span Annotations will continue to work as they do now.
Teams are encouraged to migrate their systems to use
meta.annotation_typeto identify Span Annotations.
Honeycomb will no longer provide feature enhancements or bug fixes for Span Annotations that use
meta.span_typeas their identifying field.
How to migrate your instrumentation if you use Span Annotations
Note: if you do not use Span Annotations, no migration is required.
OpenTelemetry Exporter Users
Upgrade to the latest version of your Open Telemetry Exporter
Secure Tenancy Users (regardless of what instrumentation library you use)
Identify which field represents the Span Annotation. Go to your Dataset Settings, Definitions tab and set the field Metadata: Annotation Type to the field name that identifies Span Annotations. If you are only using the field
Metadata: Kindfor Span Annotations, set it to blank (click the X to remove assignment on this field). Save your changes.
Users of Other Instrumentation Types (e.g. Beelines, OpenTracing, etc.)
Update your instrumentation code to replace the field name
meta.span_typewith the field name
If you use your own field name to identify Span Annotations, simply go to your Dataset Settings, Definitions tab and set the field
Metadata: Annotation Typeto the your field name. Set the field
Metadata: Kindto blank (click the X to remove assignment on this field). Save your changes. You do not need to change your instrumentation code. For more information the Definitions tab, see here.