Codex Agent Telemetry Integration

minware can receive telemetry data from the OpenAI Codex CLI via the OpenTelemetry Protocol (OTLP/HTTP). This lets you capture detailed usage data — logs, metrics, and traces — directly in minware as a custom data source, without any schema mapping or transformation.

Codex telemetry data is fully queryable via minQL and can be used in any custom report.

Prerequisites

• You must be an account owner to create integrations.
• You need a minware API key to authenticate telemetry requests. You can create one at Settings > API Keys.

Create an Open Telemetry Integration

1. In minware, go to Settings > Data Sources > Integrations.
2. Under AI Usage, click Codex (Otel).
3. The Integration Display Name and lowerCamelCase minQL Reference Name (used to query the data in reports) are pre-filled for Codex. Edit them if you like, or keep the defaults.
4. Click Create.

After creation, the Setup dialog will display your endpoint URL. You can reopen this dialog at any time by clicking Setup next to the integration.

Configure Codex

Personal setup

To configure Codex for your own account, add the following to your user-level ~/.codex/config.toml file:

otel
environment = "production"
log_user_prompt = true
exporter = { otlp-http = {
  endpoint = "<YOUR_ENDPOINT_URL>/v1/logs",
  protocol = "json",
  headers = { Authorization = "Bearer <YOUR_API_KEY>" }
} }

metrics_exporter = { otlp-http = {
  endpoint = "<YOUR_ENDPOINT_URL>/v1/metrics",
  protocol = "json",
  headers = { Authorization = "Bearer <YOUR_API_KEY>" }
} }

trace_exporter = { otlp-http = {
  endpoint = "<YOUR_ENDPOINT_URL>/v1/traces",
  protocol = "json",
  headers = { Authorization = "Bearer <YOUR_API_KEY>" }
} }

The correct endpoint URL is shown in the Setup dialog after creating the integration — you can copy it directly from there, or download a pre-filled config.toml using the Download Codex config.toml button.

Note that Codex requires a per-signal path on each endpoint: append /v1/logs, /v1/metrics, and /v1/traces to the base endpoint URL as shown above.

Tip: log_user_prompt = true enables raw user prompt logging so you can see the prompts that were issued to Codex. Set it to false if you prefer not to capture that data — prompts will then appear as <REDACTED> in your reports.

Organization-wide setup (managed configuration)

Administrators can push this configuration to all users without requiring individual setup by using Codex's managed configuration file. Settings in the managed file have higher precedence than the user's ~/.codex/config.toml and cannot be overridden by users or by --config CLI flags.

Please follow the Codex managed configuration documentation to set up the managed configuration.

Authentication

minware API keys are used to authenticate telemetry requests. Pass your API key as a Bearer token in the Authorization header of each OTLP exporter:

Authorization: Bearer <YOUR_API_KEY>

API keys carry the permissions of the user who created them. Only users with owner permissions can send data to an integration. If the API key is expired or the user is removed from the org, requests will be rejected.

Treat your API key like a password. Keep it secret and rotate it regularly.

Note: Only OTLP/JSON is supported. OTLP/Protobuf (binary format) is NOT supported.