[AzureMonitorExporter] cleanup nullable in Exporter classes and Transmitter #33962
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.
Towards #34013
Changes
#nullable disable
in Exporter classes and resolve issues#nullable disable
in Transmitter class and resolve issuesNotes
The biggest change here is that the
AzureMonitorResource
in theExporter
could be null.This is provided to the
TelemetryItem
constructor which is eventually used to set Tags.The Tags were already checking for null so I think this change is safe.
azure-sdk-for-net/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter/src/Customizations/Models/TelemetryItem.cs
Lines 99 to 102 in b6eb01b