Repository navigation
feat(mcp): send each tool call line to Axiom - #94
Merged
Merged
Conversation
…OM_DATASET are set Sentry stopped accepting spans when the organization's quota ran out, so tool-call latency, size and auth outcomes could not be measured. The same mcp_tool_call line printed to stdout now also goes to an Axiom dataset, batched every 5 s from a background thread, dropped (and counted) instead of ever slowing a tool call. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…he log pump Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
Review (code-review high --fix)
QA
Metrics
Post-deploy check: hourly count of |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Since Nov 12 00:00 UTC the Sentry organization is over its span quota (
span_usage_exceeded), so the MCP's SDK backs off and drops every span (backpressure, ~1M per 6 h). We cannot read tool-call latency, result size or the newmcp.authtag, and the deploys of the MCP speed work (py#88 to py#93, API#8251) cannot be measured. The same data is already printed per call as anmcp_tool_callJSON line on Railway's stdout, which no tool can query.What
AxiomIngestHandleron thelate.mcp.toolslogger: buffers eachmcp_tool_callline and posts batches tohttps://api.axiom.co/v1/datasets/<AXIOM_DATASET>/ingest?timestamp-field=tsevery 5 s (or at 1,000 lines) from a background thread.release(commit),environmentandworker(pid) to each event, so restarts and per-worker behaviour are visible.mcp_axiom_droppedevent; buffered lines are sent on shutdown.AXIOM_TOKENandAXIOM_DATASETare set. Documented indocs/HTTP_DEPLOYMENT.md.Follow-ups
zernio-mcp) and an ingest-only token in Axiom, and setAXIOM_TOKENandAXIOM_DATASETon the Railwaymcp-serverservice.schedule-posts-apiingest) is a separate decision.🤖 Generated with Claude Code