feat(telemetry): support OTLP HTTP transports

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.

[danielkov]

Summary

Add configurable OTLP trace export over gRPC, HTTP/protobuf, and HTTP/JSON. Expose protocol selection through CLI, TOML, and standard OpenTelemetry environment variables, and propagate the resolved transport to nested Kit processes.

Motivation

OTLP collectors such as Gram expose standard HTTP trace ingestion endpoints rather than gRPC. Supporting both HTTP encodings lets Kit export its existing GenAI spans directly to those collectors.

Impact

OTLP/gRPC remains the default, so existing configurations retain their current transport. HTTP configurations treat otel_endpoint as a base endpoint and append /v1/traces when needed; trace export remains disabled when no endpoint is configured.

Technical details

Configuration precedence

Protocol resolution uses CLI, then config.toml, then OTEL_EXPORTER_OTLP_TRACES_PROTOCOL, then OTEL_EXPORTER_OTLP_PROTOCOL, and finally the gRPC default. kit init leaves the protocol unset so environment selection remains effective.

HTTP export

The HTTP exporters preserve the standard generic and trace-specific OTLP header variables. The implementation enables the pinned OpenTelemetry HTTP protobuf and JSON features and reuses Kit's existing reqwest/rustls client stack.

Batch processing

HTTP transports use the SDK Tokio-backed batch span processor so the async reqwest exporter is driven by a compatible runtime. gRPC retains the existing thread-backed batch processor.

HTTP shutdown is independently bounded to five seconds so a stalled collector cannot delay Kit exit beyond the provider deadline.

[kit-code-agent]

Found two issues: the new HTTP exporters select a client incompatible with the default batch processor, and malformed standard protocol environment values abort startup instead of falling back.

[kit-code-agent]

The previous HTTP exporter/runtime incompatibility is addressed, and the protocol-environment behavior is an accepted intentional requirement. One new shutdown-bound issue remains.

[kit-code-agent]

The prior HTTP shutdown-deadline finding is addressed for normal operation. One constrained thread-creation failure path can still bypass the bound.

[kit-code-agent]

No issues found. The changes look good to merge.