Skip to content

docs: position against the OTel GenAI process-line gap - #7

Merged
minglong51 merged 1 commit into
mainfrom
docs/otel-positioning
Aug 22, 2026
Merged

docs: position against the OTel GenAI process-line gap#7
minglong51 merged 1 commit into
mainfrom
docs/otel-positioning

Conversation

@minglong51

Copy link
Copy Markdown
Owner

One README section, +7/-1, no code.

The competitive framing now names the ground the OTel GenAI semantic conventions leave open: they standardized the semantic half of agent telemetry — what the agent spent — and the vendor dashboards consume it natively, but they stop at the process line. Whether the host process is wedged at 97% CPU, crash-looping, or leaking RSS is modeled by no gen_ai span, and the agent CLIs don't export even their own pid. That half needs its own tool; this is it.

  • Existing htop/Grafana bullets byte-identical; kill-switch bullet stays the closer.
  • Deliberately no version pin in the README ("pre-stable" is exactly why a pin rots).
  • No overreach: this does not claim a session.id↔pid join the tool doesn't yet make — the positioning is about process-health coverage only.
  • Design docs untouched: neither HLD nor LLD names the why-not section as a surface.

Pre-existing, not from this PR: HLD.md:81 cites README.md:377-392 for the systemd unit, but that section already starts at line 393 on main (now 400). Flagging for whoever next touches the HLD.

The 2026 telemetry standard covers what an agent spent (session spans,
token counters, cost rollups) and stops at the process line: wedged,
crash-looping, and leaking processes appear in no GenAI span, and the
agent CLIs don't export even their own pid. Add that bullet to the
why-not section and retitle it to include OTel. Existing htop/Grafana
bullets unchanged; no code touched.
@minglong51
minglong51 merged commit aa6afba into main Aug 22, 2026
4 checks passed
@minglong51
minglong51 deleted the docs/otel-positioning branch August 22, 2026 19:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant