Original Summary

Solo founder here. When an AI feature breaks in prod, the error is in Sentry, the spans are somewhere else, and the model call is in a third tool. axonpush puts them together: point your existing OpenTelemetry exporter or Sentry DSN at it, no new SDK app spans, exceptions and model/tool calls on one trace; errors grouped into issues hand a failing run to Claude Code or Codex with the trace attached optional gateway for AI traffic: block or redact risky tool calls and PII, and cap spend per agent (falls back to a cheaper model instead of killing the run) It's early, and I'm looking for the first few teams to try it. I'll set it up with you personally. What would make you trust a new tool with your production traces? That's what I'm trying to figure out. axonpush.xyz   submitted by   /u/dank_as_fuck_ [link]   [comments]

中文概览

中文标题： 我打造了一种在单条 trace 中查看应用、AI 调用与错误的方式

独立创始人推出 axonpush，将应用 span、异常与模型/工具调用放在同一条 trace 中；可将现有 OpenTelemetry exporter 或 Sentry DSN 指向它，无需新 SDK。错误会分组为 issue，并可将失败运行连同 trace 交给 Claude Code 或 Codex；可选网关能拦截或脱敏高风险工具调用与 PII，并按 agent 限制花费，超限时回退到更便宜模型。目前尚早，寻找首批团队试用。

  • 情报分类：开源项目与落地
  • 分类依据：独立开发者发布 AI 应用可观测性工具，整合追踪、错误与模型调用。
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/27 03:36:03