[TESTING] Usage metrics logging #3063
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This enables Glean logging as soon as the object is instantiated, instead of only when it's intialized. This causes a load of the underlying library, which is why we avoid that in release.
This should allow us to see if a ping is reconstructed at a later point. Should be unique and stable across a run of the app.
We know it's the usage* metrics that we want to look at. We log all sorts of information about storing them.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables Glean logging as soon as the object is instantiated,
instead of only when it's intialized.
This causes a load of the underlying library, which is why we avoid that
in release.