-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Fix #6886 - Telemetry for New Tab Button on Url Nav bar #7023
Fix #6886 - Telemetry for New Tab Button on Url Nav bar #7023
Conversation
@travis79 I have added an event after and updated the Could you please check the two comments I have added above. They are mainly to do with following question:
|
SwiftLint found issuesWarnings
Errors
Generated by 🚫 Danger |
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 is a Glean Parser lint or error that is preventing it from generating the SDK code, please check the build errors and if you don't see anything there, ping me and I'll take a look at why it's not working for you.
@@ -227,6 +227,12 @@ The event ping contains a list of events ([see event format on readthedocs.io](h | |||
|---------------------------------------------------------------------|----------|-----------|---------|------------------|---------------------------------------------------| | |||
| Allow user to search or add url from tab tray search button | action | tap | start-search-button | -n/a- | -n/a- | | |||
|
|||
### Url Bar | |||
|
|||
| Event | category | method | object | value | extras | |
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.
If the code generation for the Glean SDK went correctly, it would have updated the /docs/metrics.md
file and you should no longer have to manually document your telemetry like this. This should only be necessary for legacy telemetry.
Client/metrics.yaml
Outdated
@@ -325,6 +325,18 @@ tabs: | |||
notification_emails: | |||
- firefox-ios@mozilla.com | |||
expires: "2021-07-01" | |||
add-new-tab-button: |
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 don't see the update to the metrics.md or anything that suggests that this was processed by the glean_parser build step correctly. If you look at the errors to the build, do you see any "Glean Parser" errors or warnings? If so, you need to fix those for the code generation step to work.
Also, just a naming nit, but this means you will be calling this like GleanMetrics.Tabs.addNewTabButton.add()
, which is a little awkward. What if you shortened it to new-tab-button
?
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.
Is this different than the tab open counter above? I understood it to be the event that fired when a new tab is opened, but this is fine if there are multiple ways of opening a new tab and you this is just counting one of the ways.
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.
Yeah we have a new tab button at the tab toolbar and this one is on the url nav bar hence the difference.
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.
@travis79 Took your suggestion and renamed it to be new_tab_pressed
:)
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 LGTM! Please let me know if you run into any more issues :)
No description provided.