Abhinav d9c71d41a9 Add OTEL metrics for hook runs (#18026) ...

# Why
We already emit analytics for completed hook runs, but we don't have
matching OTEL metrics to track hook volume and latency.

# What
- add `codex.hooks.run` and `codex.hooks.run.duration_ms`
- tag both metrics with `hook_name`, `source`, and `status`
- emit the metrics from the completed hook path

Verified locally against a dummy OTLP collector

---------

Co-authored-by: Codex <noreply@openai.com>

d9c71d41a9 · 2026-04-16 21:30:38 +00:00

History

..

events

[codex] reduce module visibility (#16978)

2026-04-07 08:03:35 -07:00

metrics

Add OTEL metrics for hook runs (#18026)

2026-04-16 21:30:38 +00:00

config.rs

otel: remove the last workspace crate feature (#16469)

2026-04-01 13:45:23 -07:00

lib.rs

[codex] reduce module visibility (#16978)

2026-04-07 08:03:35 -07:00

otlp.rs

fix(otel): make HTTP trace export survive app-server runtimes (#14300)

2026-03-11 12:33:10 -07:00

provider.rs

chore: clean up argument-comment lint and roll out all-target CI on macOS (#16054)

2026-03-27 19:00:44 -07:00

targets.rs

chore(otel): reorganize codex-otel crate (#13800)

2026-03-06 14:58:18 -08:00

trace_context.rs

chore: clean up argument-comment lint and roll out all-target CI on macOS (#16054)

2026-03-27 19:00:44 -07:00