Codex Telemetry 儀表提示| Telemetry

用例證據路徑

Codex instrumentation prompt：從實施到決策

完整的 codex instrumentation prompt 測量迴圈連線一個擁有的工作流程、一個有界事件契約、一個受控裝置和一個有人可以採取行動的問題。

1
設定邊界
生成或複製 Telemetry API 金鑰。
2
捕捉結果
Begin with page_viewed, code_snippet_copied, integration_check_submitted and document the grain of each event.
3
證明行數
查詢 Telemetry 中的新事件並填補剩餘的空白。
4
做出決定
複製設定提示的使用者是否可以更快地啟用？

代理提示

將其貼上到您的編碼代理中

更換 YOUR_API_KEY 註冊後，然後要求代理執行產品流程並驗證第一個事件。

代理提示

Codex instrumentation prompt 設定提示

text

Instrument this project with structured logs using /skill.md. Use this Telemetry API key: YOUR_API_KEY Anonymous keys support logging and synchronous SQL without signup. Claim the existing workspace at https://telemetry.sh/register with the same key before creating dashboards or alerts. If it is unclaimed, query the event to verify delivery and report which features need signup. Please: 1. Find the most important user-facing flows, background jobs, and AI/tooling workflows. 2. Add structured logging with snake_case table and field names. 3. Capture the key signals for each workflow, including status, latency, identifiers, and error context when relevant. 4. Run one real user-facing or operational flow through the instrumented application and verify its event appears 中 Telemetry. Do not use telemetry_quickstart for this milestone. 5. Run a read-only query over that real event, then create a high-level dashboard with charts and tables that summarize the most important signals in this project. 6. Tell me what you instrumented, which real flow you verified, which tables you created, and which dashboard views I should review first. Keep event payloads small and focused. Make dashboard labels and charts easy to scan.

為此提示建立 API 金鑰，預覽工作代理事件，並在應用程式準備就緒時替換範例。

免費開啟此設定