Description

This PR optimizes the internal-logs feature in opentelemetry-otlp by changing its dependency from opentelemetry-http/internal-logs to opentelemetry/internal-logs.

Problem

Currently, enabling the internal-logs feature in opentelemetry-otlp requires opentelemetry-http even when only using gRPC transport (grpc-tonic). This creates an unnecessary dependency since:

1. All internal logging macros (otel_debug!, otel_warn!, otel_error!, otel_info!) are defined in the opentelemetry crate
2. The opentelemetry-http/internal-logs feature simply forwards to opentelemetry/internal-logs
3. Users who only need gRPC transport are forced to pull in HTTP transport dependencies

Solution

Changed the internal-logs feature definition in opentelemetry-otlp/Cargo.toml:

-internal-logs = ["tracing", "opentelemetry_sdk/internal-logs", "opentelemetry-http/internal-logs"]
+internal-logs = ["tracing", "opentelemetry_sdk/internal-logs", "opentelemetry/internal-logs"]

Benefits

• Reduced dependencies: When using grpc-tonic with internal-logs enabled (and disabling default features), opentelemetry-http is no longer compiled
• More logical dependency: Depends directly on where internal logging macros are defined
• No breaking changes: HTTP transport users are unaffected as http-proto and http-json features still properly depend on opentelemetry-http

Testing

Verified the following scenarios:

• ✅ grpc-tonic + logs + internal-logs: opentelemetry-http not compiled
• ✅ grpc-tonic + logs (no internal-logs): Builds successfully
• ✅ http-proto + logs + internal-logs: opentelemetry-http properly included
• ✅ Default features: All dependencies work correctly
• ✅ All 29 unit tests pass
• ✅ Examples compile successfully

Fixes #[issue_number]

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.