Skip to content
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

Telemetry: don't track implicitly run schematics #14190

Closed
StephenFluin opened this issue Apr 16, 2019 · 1 comment · Fixed by #14417
Closed

Telemetry: don't track implicitly run schematics #14190

StephenFluin opened this issue Apr 16, 2019 · 1 comment · Fixed by #14417
Labels
Milestone

Comments

@StephenFluin
Copy link
Contributor

StephenFluin commented Apr 16, 2019

  • We should only track user entered commands (like schematics), not implied schematics. IE when a user runs ng new we should track that, but not the fact that they implicitly invoked ng generate workspace or ng generate project
  • Aliases should be combined (ng generate c and ng generate component should be combined into a single type of GA telemetry report)
  • Several of our custom metrics (at least Bundle Sizes / build times / ngOnInit) aren't being reported / I can't figure out how to see them :)
@ngbot ngbot bot added this to the Backlog milestone Apr 16, 2019
@alexeagle alexeagle modified the milestones: Backlog, 8.0 Apr 16, 2019
@alexeagle alexeagle changed the title CLI Telemetry update requests Telemetry: don't track implicitly run schematics May 7, 2019
clydin added a commit to clydin/angular-cli that referenced this issue May 13, 2019
@clydin clydin self-assigned this May 14, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
@clydin clydin removed their assignment Jun 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants