Bug 1843406 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Dan Mosedale (:dmosedale, :dmose) from comment #4)
> Chris, do these look reasonable?
> a) filter out "null" and "other" channels
Can do.

> b) move Undesired Pings to own graph
Should be straightforward.

> c) make "release" and "Windows" the default settings
These values are controlled by the URL of the dashboard. Instead of https://mozilla.cloud.looker.com/dashboards/operational_monitoring::firefox_messaging_system use https://mozilla.cloud.looker.com/dashboards/operational_monitoring::firefox_messaging_system?Normalized+Channel=release&Normalized+Os=Windows

> d) switch alerting to just simple threshhold alerts (we decide that getting the alerts to work based on historical trends without substantial annoying artifacts that it doesn't deserve to be in MVP, especially since just having something basic will be way better than what we have now -- nothing).
Existing thresholdable alerts will remain (pending the investigation of bug 1844360) and should serve.

> e) investigate the usefulness of build ID, parameter, branch columns and consider filtering them if they're unlikely to offer any useful functionality, since they create visual clutter.
This one I will look into, but I have no idea whether there'll be much I can do about it. (I've not changed OpMon itself before. It could be fun.

---
I'll get these done, report back here, then mark as FIXED.
(In reply to Dan Mosedale (:dmosedale, :dmose) from comment #4)
> Chris, do these look reasonable?
> a) filter out "null" and "other" channels

Can do.

> b) move Undesired Pings to own graph

Should be straightforward.

> c) make "release" and "Windows" the default settings

These values are controlled by the URL of the dashboard. Instead of https://mozilla.cloud.looker.com/dashboards/operational_monitoring::firefox_messaging_system use https://mozilla.cloud.looker.com/dashboards/operational_monitoring::firefox_messaging_system?Normalized+Channel=release&Normalized+Os=Windows

> d) switch alerting to just simple threshhold alerts (we decide that getting the alerts to work based on historical trends without substantial annoying artifacts that it doesn't deserve to be in MVP, especially since just having something basic will be way better than what we have now -- nothing).

Existing thresholdable alerts will remain (pending the investigation of bug 1844360) and should serve.

> e) investigate the usefulness of build ID, parameter, branch columns and consider filtering them if they're unlikely to offer any useful functionality, since they create visual clutter.

This one I will look into, but I have no idea whether there'll be much I can do about it. (I've not changed OpMon itself before. It could be fun.

---
I'll get these done, report back here, then mark as FIXED.

Back to Bug 1843406 Comment 5