Otel service name not working with dapr scenario

[davidfowl]

Seems like the names aren't right.

[danegsta]

This looks to be a dapr issue; they are hardcoding their OTEL service name to be the sidecar AppID here: https://github.com/dapr/dapr/blob/ed3417223c5ea4654f38df1fc5abee93e52cea6e/pkg/runtime/runtime.go#L386-L389

While the Go OTEL SDK should still automatically pick up OTEL environment config, it merges the hardcoded configurations over the environment config, meaning our OTEL_SERVICE_NAME environment variable is ignored. Theoretically this should be a simple matter of dapr calling r = r.Merge(resource.Environment()) to allow the environment variables to override their defaults.

[davidfowl]

@philliphoff can you take this to the dapr team?

[philliphoff]

@davidfowl It looks like this has been asked for before (see: dapr/dapr#5942) but didn't make the cut for prior versions. I've asked the maintainer if they're still interested.

(Just for fun I tried @danegsta's suggestion but it didn't seem to change the tracing behavior, though that may just be my poor Golang skills.)

[philliphoff]

Also submitted #1272 to make it easier to test changes to the Dapr runtime with Aspire.