Repository navigation
feat(opencode): support managed OTLP exporter settings - #47353
lennyvaknine43 wants to merge 1 commit into
Conversation
|
The following comment was made by an LLM, it may be inaccurate: Based on my search, I found two potentially related PRs (excluding the current PR #47353):
However, these appear to be older PRs addressing related but distinct aspects of observability. The current PR (47353) is specifically focused on adding managed-only OTLP configuration support for endpoint-managed deployments, which appears to be a new feature rather than a duplicate of existing work. |
|
We will definitely support this ty. |
|
Automated PR Cleanup Thank you for contributing to opencode. Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions. This PR was closed because it matched the following cleanup criteria:
PRs created within the last month are not affected by this cleanup. If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate. Thanks again for taking the time to contribute. |
Issue for this PR
Closes #47351
Type of change
What does this PR do?
Adds managed-only OTLP exporter settings for endpoint-managed OpenCode deployments:
{ "telemetry": { "otlp": { "endpoint": "https://otel.example.com", "headers": "Authorization=Bearer token", "resourceAttributes": "deployment.environment.name=production" } } }OpenCode reads these values from the system-managed configuration directory and macOS
ai.opencode.managedpreferences before initializing observability.Every value supplied by the macOS managed profile has the highest precedence. Profile values override the system-managed file and inherited
OTEL_*environment variables. Values omitted from the profile may fall back to those lower-precedence sources.User and project configuration cannot configure or redirect the managed OTLP exporter. Existing environment-only behavior remains unchanged when no managed OTLP settings are present.
How did you verify your code works?
bun typecheckinpackages/corebun typecheckinpackages/opencodebun test test/effect/observability.test.tsinpackages/corebun test test/config/config.test.tsinpackages/opencodebun run buildinpackages/webgit diff --checkTests cover managed OTLP parsing and managed settings overriding inherited process values.
Screenshots / recordings
N/A, configuration-only change.
Checklist