-
Notifications
You must be signed in to change notification settings - Fork 27
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: add telemetry support #136
Conversation
9b6aa87
to
2978904
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.
Know it is still a WIP, but left some comments.
…l refactoring -- incomplete checkpoint
db11c0b
to
c7c87c2
Compare
Do not merge until we have proper endpoint setup. This should be done by hardcoding the endpoint in the code instead of using the |
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.
I think there are some improvements which can still be made. The biggest issue is the lack of a feature flag, which I think is a requirement to opt-out when running tests during CI. We dont want to have GH runs reporting telemetry data.
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.
Looks great! I just left a couple of comments.
Can't wait to see some metrics!
* test: ensure errors propagated (#143) * test: relocate integration tests (#144) * test: relocate integration tests * ci: reduce run time * refactor: remove unused import * refactor: improve feature isolation * refactor: remove unnecessary path prefixes * refactor: invert feature Using `--features=no_telemetry` still resulted in inclusion of pop-telemetry in the dependency tree. Using `telemetry` also makes conditional compilation much simpler.
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.
Looks like the Github Action check has not completed. The PR LGTM. Let's get the checks to pass.
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.
Seems to be regressions, presumably due to resolvign merged conflicts.
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!
This PR introduces ANONYMOUS telemetry to get metrics on the following things:
pop new parachain my_personal_filename
is inputted, onlypop new parachain
will be reported.A new arg has been added to
new parachain
:release_tag
. This was added due to a refactor that enables callinggenerate_parachain_from_template
once, instead of twice in separate flows. The latest release version is used if release_tag is not set. This argument will likely be most useful in a CI.no-telemetry
feature flag.[ ] Provide explicit explanation of how the telemetry works, what it's for, and what it trackswill be in a new PR docs(telemetry): readme explaining what and why we collect #157