As mentioned in CNCF slack, I think MUST is too strong a requirement here without a better understanding of how instrumentation would be expected to access / adhere to configuration. I.e can we force native instrumentation to adhere to file based configuration options?
Some language SIGs may view it useful to provide a model which can be used in code to programmatically define configuration, but others will view it as frivolous duplication of the SDK APIs which already exist.
As mentioned in CNCF slack, I think MUST is too strong a requirement here without a better understanding of how instrumentation would be expected to access / adhere to configuration. I.e can we force native instrumentation to adhere to file based configuration options?
Some language SIGs may view it useful to provide a model which can be used in code to programmatically define configuration, but others will view it as frivolous duplication of the SDK APIs which already exist.
Let's lighten the "MUST" requirement to "MAY".