-
Notifications
You must be signed in to change notification settings - Fork 142
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
🔊 Deduplicate telemetry events #2746
Conversation
c7546ff
to
f301a04
Compare
Bundles Sizes Evolution
🚀 CPU Performance
|
f301a04
to
01cad67
Compare
/to-staging |
🚂 Branch Integration: starting soon, merge in < 9m Commit 01cad67ff2 will soon be integrated into staging-19. This build is going to start soon! (estimated merge in less than 9m) Use |
🚂 Branch Integration: This commit was successfully integrated Commit 01cad67ff2 has been merged into staging-19 in merge commit 718caf3dbb. Check out the triggered pipeline on Gitlab 🦊 |
same error message got caught by the deduplication, probably due to missing jasmine frame only for safari
❓ question: Are we not interested in how much a customer is using an API? |
It could be interesting but it is not in the scope of the current initiative (cf RFC). |
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.
Sweet!
Motivation
Avoid to loose some telemetry when a single event is spammed, ex:
Changes
Discard already seen telemetry events
Testing
I have gone over the contributing documentation.