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
AzureMonitorExporter calls Flush on each Span.
It is caused by this commit. It seems that Flush must be called after all Spans collected into batches, outside the Resourse/ Scope/ Spans loop.
Steps to Reproduce
To have constant Spans flow into OTEL Collector with AzureMonitorExporter enabled.
Expected Result
AzureMonitorExporter collects Spans in batches and calls Flush.
Actual Result
AzureMonitorExporter calls Flush on each Span.
Collector version
v0.116.0
The text was updated successfully, but these errors were encountered:
Component(s)
exporter/azuremonitor
What happened?
Description
AzureMonitorExporter calls Flush on each Span.
It is caused by this commit. It seems that Flush must be called after all Spans collected into batches, outside the Resourse/ Scope/ Spans loop.
Steps to Reproduce
To have constant Spans flow into OTEL Collector with AzureMonitorExporter enabled.
Expected Result
AzureMonitorExporter collects Spans in batches and calls Flush.
Actual Result
AzureMonitorExporter calls Flush on each Span.
Collector version
v0.116.0
The text was updated successfully, but these errors were encountered: