Skip to content

Honor custom OTLP metrics exporters when analytics is disabled - #52278

Merged
copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/0c61f0f01e2b694db642ac7e7fd1dac9965c7d96
Oct 8, 2026
Merged

copyberry[bot] merged 1 commit into
mainfrom
copyberry/codex-internal-to-codex-oss/0c61f0f01e2b694db642ac7e7fd1dac9965c7d96

Conversation

@copyberry

@copyberry copyberry Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Honor custom OTLP metrics exporters when analytics is disabled

Why

Disabling OpenAI analytics also disabled explicitly configured OTLP metrics collectors. Users should be able to export metrics to their own collectors independently of analytics.enabled.

What changed

Apply the analytics preference only to the built-in statsig metrics exporter. Keep custom OTLP HTTP and gRPC exporters enabled regardless of that preference, and use otel.metrics_exporter = "none" to disable metrics export. Clarify these settings in config documentation and the schema.

Testing

Cover exporter selection across explicit and default analytics preferences. Update app-server and daemon telemetry tests to verify custom metrics export with analytics disabled, and worktree tests to disable metrics through the exporter setting.

## Why

Disabling OpenAI analytics also disabled explicitly configured OTLP metrics collectors. Users should be able to export metrics to their own collectors independently of `analytics.enabled`.

## What changed

Apply the analytics preference only to the built-in `statsig` metrics exporter. Keep custom OTLP HTTP and gRPC exporters enabled regardless of that preference, and use `otel.metrics_exporter = "none"` to disable metrics export. Clarify these settings in config documentation and the schema.

## Testing

Cover exporter selection across explicit and default analytics preferences. Update app-server and daemon telemetry tests to verify custom metrics export with analytics disabled, and worktree tests to disable metrics through the exporter setting.

GitOrigin-RevId: 0c61f0f01e2b694db642ac7e7fd1dac9965c7d96
@copyberry
copyberry Bot force-pushed the copyberry/codex-internal-to-codex-oss/0c61f0f01e2b694db642ac7e7fd1dac9965c7d96 branch from d239333 to 2c3156a Compare October 8, 2026 21:18
@copyberry
copyberry Bot merged commit 2c3156a into main Oct 8, 2026
5 of 8 checks passed
@copyberry
copyberry Bot deleted the copyberry/codex-internal-to-codex-oss/0c61f0f01e2b694db642ac7e7fd1dac9965c7d96 branch October 8, 2026 21:18
@chatgpt-codex-connector

Copy link
Copy Markdown
Contributor

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-08T21:18:39.463928Z d239333 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions github-actions Bot locked and limited conversation to collaborators Oct 8, 2026
@onitorrinco
onitorrinco deployed to issue-triage October 8, 2026 21:29 — with Image GitHub Actions Active
@onitorrinco
onitorrinco deployed to issue-triage October 8, 2026 21:29 — with Image GitHub Actions Active
@onitorrinco
onitorrinco deployed to issue-triage October 8, 2026 21:29 — with Image GitHub Actions Active
@Jer512
Jer512 deployed to issue-triage October 8, 2026 21:31 — with Image GitHub Actions Active
@Jer512
Jer512 deployed to issue-triage October 8, 2026 21:31 — with Image GitHub Actions Active
@Jer512
Jer512 deployed to issue-triage October 8, 2026 21:31 — with Image GitHub Actions Active
@nakano16180
nakano16180 deployed to issue-triage October 8, 2026 21:32 — with Image GitHub Actions Active
@nakano16180
nakano16180 deployed to issue-triage October 8, 2026 21:32 — with Image GitHub Actions Active
@nakano16180
nakano16180 deployed to issue-triage October 8, 2026 21:32 — with Image GitHub Actions Active
@nakano16180
nakano16180 deployed to issue-triage October 8, 2026 21:33 — with Image GitHub Actions Active
@kendonB
kendonB deployed to issue-triage October 8, 2026 21:41 — with Image GitHub Actions Active
@kendonB
kendonB deployed to issue-triage October 8, 2026 21:41 — with Image GitHub Actions Active
@kendonB
kendonB deployed to issue-triage October 8, 2026 21:41 — with Image GitHub Actions Active
@kendonB
kendonB deployed to issue-triage October 8, 2026 21:42 — with Image GitHub Actions Active

This branch was successfully deployed

1 active deployment
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants