Closed Bug 1911104 Opened 4 months ago Closed 1 month ago

Chatbot telemetry for 133 nimbus experiment with onboarding and menus

Categories

(Core :: Machine Learning, task, P2)

task
Points:
5

Tracking

()

VERIFIED FIXED
133 Branch
Tracking Status
firefox130 --- wontfix
firefox131 --- wontfix
firefox132 --- wontfix
firefox133 --- verified

People

(Reporter: asafko, Assigned: Mardak)

References

(Blocks 1 open bug)

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.

Priority: -- → P2

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]

Let me repurpose it for 131-2 then, and remove from this metabug here.

Summary: Chatbot telemetry for 130 → Chatbot telemetry for 131
Version: Firefox 130 → unspecified
Summary: Chatbot telemetry for 131 → Chatbot telemetry for 131-132
No longer blocks: 1905745
Blocks: 1911129

Convert AWSendEventTelemetry to chatbot glean events.

Points: --- → 3

[Tracking Requested - why for this release]: telemetry for the chatbot nimbus experiment (and general usage)

pushing experiment to 133

Blocks: 1922611
Points: 3 → 5
Summary: Chatbot telemetry for 131-132 → Chatbot telemetry for 133 nimbus experiment with onboarding and menus
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
Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 133 Branch
Flags: qe-verify+
QA Contact: rdoghi

This issue is verified as fixed in our latest Nightly build. I was able to trigger the telemetry pings from the "Probes document"

Status: RESOLVED → VERIFIED
Flags: qe-verify+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: