Closed
Bug 1911104
Opened 2 years ago
Closed 1 year ago
Chatbot telemetry for 133 nimbus experiment with onboarding and menus
Categories
(Core :: Machine Learning: General, task, P2)
Core
Machine Learning: General
Tracking
()
VERIFIED
FIXED
133 Branch
People
(Reporter: asafko, Assigned: Mardak)
References
Details
(Whiteboard: [genai])
Attachments
(1 file)
To understand baseline adoption and monitor issues with implementation, let's please add additional telemetry to 1the30 Release Labs chatbot implementation. Probes document.
All probes belong to cat 3/low sensitivity interaction data.
| Assignee | ||
Comment 1•2 years ago
|
||
All the shortcuts related telemetry is being added in bug 1910005, so this bug could be for any other telemetry if needed for 130.
Assignee: nobody → edilee
Whiteboard: [genai]
Updated•2 years ago
|
Let me repurpose it for 131-2 then, and remove from this metabug here.
Summary: Chatbot telemetry for 131 → Chatbot telemetry for 131-132
| Assignee | ||
Comment 3•1 year ago
|
||
Convert AWSendEventTelemetry to chatbot glean events.
| Assignee | ||
Updated•1 year ago
|
Points: --- → 3
| Assignee | ||
Comment 4•1 year ago
|
||
[Tracking Requested - why for this release]: telemetry for the chatbot nimbus experiment (and general usage)
tracking-firefox132:
--- → ?
| Assignee | ||
Comment 5•1 year ago
|
||
pushing experiment to 133
status-firefox131:
--- → wontfix
status-firefox132:
--- → fix-optional
status-firefox133:
--- → affected
tracking-firefox132:
? → ---
| Assignee | ||
Updated•1 year ago
|
Points: 3 → 5
Summary: Chatbot telemetry for 131-132 → Chatbot telemetry for 133 nimbus experiment with onboarding and menus
Updated•1 year ago
|
Attachment #9427719 -
Attachment description: Bug 1911104 - Chatbot telemetry for 131-132 r=tarek! → Bug 1911104 - Chatbot telemetry for 133 nimbus experiment with onboarding and menus r=tarek!
Pushed by elee@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fdc3431fee03
Chatbot telemetry for 133 nimbus experiment with onboarding and menus r=tarek
Comment 7•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
Updated•1 year ago
|
Updated•1 year ago
|
Flags: qe-verify+
QA Contact: rdoghi
Comment 8•1 year ago
|
||
This issue is verified as fixed in our latest Nightly build. I was able to trigger the telemetry pings from the "Probes document"
You need to log in
before you can comment on or make changes to this bug.
Description
•