-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(gatsby-admin): track plugin telemetry #26885
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The telemetry parts look good, and the events seem like a great starting point, and in-line with the other events we collect from the OSS side.
Gatsby Cloud Build Reportgatsby 🎉 Your build was successful! See the Deploy preview here. Build Details🕐 Build time: 21m |
test: true, | ||
bla: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bla
is removed in #26916
but i don't see if the test
option used? is this a test leftover?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yea, this is just me playing around with configuring plugins in Admin!
* Set up first service exposing gatsby-telemetry * Run background updates * Move telemetry server to gatsby package * Add body-parser dependency * Start telemetry server on gatsby develop (gatsbyjs#26853) * Revert "Start telemetry server on gatsby develop (gatsbyjs#26853)" This reverts commit 5febd35. * Revert "Revert "Start telemetry server on gatsby develop (gatsbyjs#26853)"" This reverts commit 08bb027. * Track first telemetry from Admin * Update telemetry-server.ts
Based on #26832, this fetches the telemetryserver port from the
/___services
endpoint and adds auseTelemetry
hook to Admin that currently has this API (modeled aftergatsby-telemetry
):@jamo I'm not 100% sure whether the events I'm currently tracking are inline with what you'd expect us to track! Do the shapes/metadata/etc look alright?