Currently opentelemetry-application-insights reports all attributes (span and resource attributes) as properties. This means that attributes that are mapped to tags are reported twice, e.g.:
Some tags have stricter length limitations. The property could report the full value while the tag would have a shorter one.
Some tags are made up of multiple attributes, e.g. server.address + server.port form the Dependency Target. The properties still report the individual values.
Disadvantages:
Sending data twice causes more network traffic and storage. Is the amount of data relevant or small enough that it doesn't matter?
Currently
opentelemetry-application-insightsreports all attributes (span and resource attributes) as properties. This means that attributes that are mapped to tags are reported twice, e.g.:device.idanddevice.model.name: https://github.com/frigus02/opentelemetry-application-insights/blob/542e80b24b99f3df1d9420652ae8d615310a1b39/tests/http_requests.rs#L38-L39Advantages:
server.address+server.portform the Dependency Target. The properties still report the individual values.Disadvantages:
Looks like the JS exporter elides some attributes: https://github.com/Azure/azure-sdk-for-js/blob/c66cad23c4b803719db65cb48a453b0adc13307b/sdk/monitor/monitor-opentelemetry-exporter/src/utils/spanUtils.ts#L108-L143