You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a springboot 3 app and configured a SpanExportingPredicate to filter some traces based on business logic. Due to this logic, there are scenarios where the CompositeSpanExporter.export() method is being invoked. However, since the configured predicates may produce empty changedSpanData, there are cases where spanExporter.export(changedSpanData) is called with no data.
This results in errors for some OpenTelemetry providers, such as Honeycomb.io. To prevent such errors and avoid some additional empty requests, it would be beneficial to avoid these empty calls altogether.
My current workaround is to override the CompositeSpanExporter and check if there are spans before calling the exporter:
I'm using a springboot 3 app and configured a
SpanExportingPredicate
to filter some traces based on business logic. Due to this logic, there are scenarios where theCompositeSpanExporter.export()
method is being invoked. However, since the configured predicates may produce emptychangedSpanData
, there are cases wherespanExporter.export(changedSpanData)
is called with no data.This results in errors for some OpenTelemetry providers, such as Honeycomb.io. To prevent such errors and avoid some additional empty requests, it would be beneficial to avoid these empty calls altogether.
My current workaround is to override the CompositeSpanExporter and check if there are spans before calling the exporter:
The text was updated successfully, but these errors were encountered: