Add custom BatchExportProcessor to support standard metrics #33715
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating trace exporter to use the custom BatchExportProcessor to let all activities pass on to exporter. This will enable accurate standard metric collection on the exporter side. Activities with
Recorded=false
will be filtered out on the exporter side to prevent sampledOut activities to get transmitted to backend.Custom ApplicationInsights sampler will also be updated to return
RecordOnly
SamplingResult instead ofDrop
when the samplers decision is to drop the telemetry. This will allow activities to be enriched by instrumentation libraries (This is needed for setting dimensions on standard metrics) and also allow correct traceflags(traceparent
header) to be transmitted to downstream services.