Feature Description
This issue is designed to work with otel command from #61
Claude Code will ship OpenTelemetry traces if certain env vars are set. This issue is to offer an easy way to set them up for programs started under authbridge exec.
Proposed Solution
If we are running a Rossoctl-configured OTel collector with otel collect, make that collector available to Claude on the laptop. This will export the env vars needed by Claude.
Note that we might also be running on a different port, or want to write via port-forward or HttpRoute to a real Rossoctl on K8s, so we will need an additional option.
Want to contribute?
Additional Context
Note that other programs might use different variables. This issue is about Claude Code CLI, not every program that ships traces. We will solve those problems through another Issue.
Note that MLflow includes skills and CLI for configuring Claude. These don't work the way Rossoctl works. We need to decide if we want to recommend that way. It might be easier for MLflow-only users if we do things the MLflow way. However, it might then be confusing on K8s, because our K8s config is very different from a local laptop config. This issue is about trying to make the two environments similar. We can discuss the pros and cons of that here.
Feature Description
This issue is designed to work with
otelcommand from #61Claude Code will ship OpenTelemetry traces if certain env vars are set. This issue is to offer an easy way to set them up for programs started under
authbridge exec.Proposed Solution
If we are running a Rossoctl-configured OTel collector with
otel collect, make that collector available to Claude on the laptop. This will export the env vars needed by Claude.Note that we might also be running on a different port, or want to write via
port-forwardor HttpRoute to a real Rossoctl on K8s, so we will need an additional option.Want to contribute?
Additional Context
Note that other programs might use different variables. This issue is about Claude Code CLI, not every program that ships traces. We will solve those problems through another Issue.
Note that MLflow includes skills and CLI for configuring Claude. These don't work the way Rossoctl works. We need to decide if we want to recommend that way. It might be easier for MLflow-only users if we do things the MLflow way. However, it might then be confusing on K8s, because our K8s config is very different from a local laptop config. This issue is about trying to make the two environments similar. We can discuss the pros and cons of that here.