Closed
Bug 1236464
Opened 10 years ago
Closed 10 years ago
[meta] Report & record the add-on version in Hello's server logs
Categories
(Hello (Loop) :: Client, defect, P1)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: standard8)
References
Details
Now that we're a system add-on, it would be useful to help determine different reports from different versions of the add-on.
For example, when we attempt a fix for a bug for connectivity issues, it would be useful to distinguish reports for the older versions from the new ones, so that we could confirm the new versions don't have the same issues.
This bug will need some definition and breakdown as it'll need some work on the server and on the client side.
Comment 1•10 years ago
|
||
Can we have the add-on version being reported so we can create reports per add-on version? Here are the reporting scenarios I have in mind:
- Compare Funnel rates between add-on X and add-on Y
- Compare session duration between add-on X and add-on Y
- Compare Churn between add-on X and add-on Y
- Compare quality metrics between add-on X and add-on Y
- Compare MAU between add-on X and add-on Y
Rank: 19
Assignee | ||
Updated•10 years ago
|
Rank: 19 → 17
Updated•10 years ago
|
Summary: [meta] Report & record the add-on version in Hello's logs → Report & record the add-on version in Hello's logs
Assignee | ||
Comment 2•10 years ago
|
||
For now, we are using this to record the add-on version in Hello's server logs. We'll consider telemetry & other things elsewhere.
Discussions with Adam and the server folks offline have agreed that we add a special header with the add-on version in. We can then log this easily on the server side.
Summary: Report & record the add-on version in Hello's logs → [meta] Report & record the add-on version in Hello's server logs
Assignee | ||
Comment 3•10 years ago
|
||
For now I'm going with "x-loop-addon-ver" unless people object during review cycles.
Assignee | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•