Matt Hensley

There is a proposal in #4860 to remove the older gRPC library. Is switching protocols to http/protobuf an option in this case?

New database metric semantic conventions are being worked on and should be stabilized soon. It doesn't look what was proposed in open-telemetry/opentelemetry-specification#2070 made it to the spec You can see...

[From footnote 5 in the db attributes](https://opentelemetry.io/docs/specs/semconv/attributes-registry/db/): > db.operation.parameter: If a parameter has no name and instead is referenced only by index, then SHOULD be the 0-based index. And the...

Additional links: [JavaScript uses `OTEL_NODE_RESOURCE_DETECTORS`](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/metapackages/auto-instrumentations-node#usage-auto-instrumentation) [PHP uses `OTEL_PHP_DETECTORS`](https://opentelemetry.io/docs/languages/php/sdk/#configuration) Also, being able to specify resource detectors via configuration is something end users have requested.

There is an unresolved issue from Alan West on clearer specs for exporter retries: https://github.com/open-telemetry/opentelemetry-specification/issues/3639 Three people have commented on that issue recently asking for the number of retry attempts...