Open Bug 1894361 (skylight-how-to-handle-fading-messages) Opened 1 year ago Updated 1 year ago

how should skylight handle long-tail messages?

Categories

(Firefox :: Messaging System, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: dmosedale, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [omc])

Over time, as we have fewer and fewer instances of a given old version in the field, the number of pings we get from a given message tapers off over time.

As an example, here's a message that was shown two times during the last month:

https://mozilla.cloud.looker.com/dashboards/1677?Submission%20Timestamp%20Date=30%20days&Message%20ID=%25FX_100_UPGRADE%25&Locale=&Normalized%20Country%20Code=&Normalized%20Channel=release&Version=&Metadata%20User%20Agent%20OS=&Branch=&Experiment=

We should consider what kind of user stories we want for messages like this. I'm guessing that the next step for a message like this is to file a bug to remove it from mozilla-central. So we might want to display something about that (or maybe send an alert).

Also potentially relevant is how we want to display no-longer live messages (I'm guessing looking at past performance is likely to be interesting/useful before too long), but I think that's probably another epic (which could be spun-off).

Note, too, that there are other currently in-production messages with just a small number of hundreds of impressions. Over time, we'll likely want more user stories than just "it's live" and "it's (almost) dead".

Alias: skylight-how-to-handle-fading-messages
Priority: -- → P2
Whiteboard: [omc]
Priority: P2 → --
Flags: needinfo?(dmosedale)
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.