-
Notifications
You must be signed in to change notification settings - Fork 2
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(analytics-module-segment): create the analytics plugin module for segment #12
Conversation
9cb9a7e
to
52dc681
Compare
"backstage": { | ||
"role": "frontend-plugin-module", | ||
"pluginId": "app", | ||
"pluginPackage": "@backstage/plugin-app-backend" | ||
}, |
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.
this config was stolen (with love) from the backstage-community analytics plugins. This is what they set, so thats what I'll set.
34e19cc
to
9b4a643
Compare
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.
Nice and tidy! My feedback is mostly docs, so nothing blocking. I do note that SHA256 alone isn't really enough for anonymization, but that is definitely a problem to tackle separately, and having what's here now is better than having no hashing at all.
…r segment Signed-off-by: Alec Jacobs <[email protected]>
Signed-off-by: Alec Jacobs <[email protected]>
Signed-off-by: Alec Jacobs <[email protected]>
1b97955
to
d39a9ca
Compare
Description
This PR implements a custom Backstage analytics module plugin specifically geared around Segment analytics.
Seeing as this is Segment's open-source backstage plugin library, it seems prudent that Segment contributes an analytics library for our own product!
This is definitely a v0.1.0 version, with much more support possibly planned for the future:
For now, we simply look at the core supported key events and primarily handle the following:
navigate
events to analytics.page() eventscreate
events as analytics.track() events where the event name is the name of the thing created (e.g. the software template executed)analytics.track()
events with the action as the event name