Closed Bug 1241560 Opened 9 years ago Closed 2 years ago

Collect and visualize metrics on the distribution of Sync server errors and their reasons over time

Categories

(Cloud Services Graveyard :: Server: Sync, defect, P3)

Product:
Cloud Services Graveyard
Component:
Server: Sync
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ckarlof, Unassigned)

References

Details

(Whiteboard: [sync-metrics])

List of sync storage error codes and reasons: https://docs.services.mozilla.com/storage/apis-1.5.html#http-status-codes List of token server error codes and reasons: https://docs.services.mozilla.com/token/apis.html#error-responses On particular interest are likely: * 400 * 401 * 409 (at least when we would've returned 409: https://bugzilla.mozilla.org/show_bug.cgi?id=1234379) * 413 (https://bugzilla.mozilla.org/show_bug.cgi?id=569295) * 5xx
Flags: firefox-backlog+
Blocks: 1241563
Priority: P1 → P2
Whiteboard: [sync-metrics]
Priority: P2 → P3
Assignee: dcoates → nobody
Bob, did you have a more recent dashboard that would be relevant here?
Flags: needinfo?(bobm)
(In reply to Ryan Kelly [:rfkelly] from comment #1) > Bob, did you have a more recent dashboard that would be relevant here? The Sync App Log Kibana dashboard would be the closest to this intended purpose. However, it needs some query TLC, and not all the log fields are present to make the correlation. As part of the migration to a deployment pipeline we'll be switching to Logging 2.0 (and the latest mozlog format) which should provide a dashboard that will cover this.
Flags: needinfo?(bobm)

We track errors now in our dev and SRE monitoring.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.