Conversation
Handcraft minimal Glean events pings since @mozilla/glean has no Node.js entry point. Tracks initialize and tool_call events. Also fix Netlify venv setup: drop get-pip.py in favor of standard venv with ensurepip (pip 26 no longer bundles setuptools).
akkomar
force-pushed
the
mcp_telemetry
branch
from
b11012b to
d87f5f6
Compare
akkomar
commented
Feb 13, 2026
Comment on lines
-7
to
-10
| python -mvenv venv --without-pip | ||
| wget https://bootstrap.pypa.io/get-pip.py | ||
| venv/bin/python get-pip.py | ||
| venv/bin/pip install wheel |
Contributor
Author
There was a problem hiding this comment.
Pip 26 no longer bundles setuptools so I needed to clean this up a bit to make the build work.
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
1 participant
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.
This adds a way to track MCP endpoint usage by sending lightweight Glean event pings on initialize and tool calls. Since
@mozilla/gleanonly ships browser bundles (no Node.js entry point), we handcraft the ping payload and POST it directly to the ingestion endpoint. This is a quick hack to set up the monitoring as soon as possible, later on I'll look into moving this to use the SDK.Events:
mcp.initialize(client info),mcp.tool_call(tool, app, success). Pings validated against the officialglean v1schema in tests.I have tested this locally with submissions to Debug Viewer: https://debug-ping-preview.firebaseapp.com/stream/mcp-test
See https://mozilla-hub.atlassian.net/browse/DENG-10652