This is sparking from this discussion #5534 (comment) , where @pmcollins spotted a change in behavior from the sdk configured with / without declarative configuration.
In the declarative configuration path ATM we are not setting process.executable.name and I opened #5534 to fix that. Doing so I implemented that differently from what the SDK is currently doing, that is getting the process.executable.name value always from the system and never from an eventually manually set resource attribute.
Semantic conventions people seems to think we are doing it wrong https://cloud-native.slack.com/archives/C041APFBYQP/p1786605693527879
So changing this in the SDK would be a breaking change, not sure how often this behavior has been leveraged though.
cc @hectorhdzg that added this behavior in 0e04658
This is sparking from this discussion #5534 (comment) , where @pmcollins spotted a change in behavior from the sdk configured with / without declarative configuration.
In the declarative configuration path ATM we are not setting
process.executable.nameand I opened #5534 to fix that. Doing so I implemented that differently from what the SDK is currently doing, that is getting theprocess.executable.namevalue always from the system and never from an eventually manually set resource attribute.Semantic conventions people seems to think we are doing it wrong https://cloud-native.slack.com/archives/C041APFBYQP/p1786605693527879
So changing this in the SDK would be a breaking change, not sure how often this behavior has been leveraged though.
cc @hectorhdzg that added this behavior in 0e04658