53
edits
CloudServices/Sync/ReDash: Difference between revisions
Jump to navigation
Jump to search
Added validation data table
(describe some events) |
(Added validation data table) |
||
| Line 180: | Line 180: | ||
* every repair should emit event_object="repair", event_method="started" as it starts, and either event_object="repair", event_method="finished/failed" as the last event. | * every repair should emit event_object="repair", event_method="started" as it starts, and either event_object="repair", event_method="finished/failed" as the last event. | ||
* There may be any number of repairResponse events written (including zero events if there are no suitable devices). Each of these should result in a event_object="repairResponse", event_method="finished/aborted" | * There may be any number of repairResponse events written (including zero events if there are no suitable devices). Each of these should result in a event_object="repairResponse", event_method="finished/aborted" | ||
=== Validation Data Roll-ups === | |||
==== telemetry.sync_bmk_total_per_day ==== | |||
This table is a roll-up of all bookmark validations (success and failures). | |||
{| class="wikitable" | |||
|- | |||
! Column name !! Data format !! Description | |||
|- | |||
| sync_day || integer (e.g. 20170518) || The day we ran validation on the user | |||
|- | |||
| total_bookmark_validations || integer || Number of times we ran bookmark validation per day. This includes successful validations. | |||
|- | |||
| total_validated_users || integer || Number of users we ran bookmark validation on for each day. | |||
|- | |||
| total_bookmarks_checked || integer || Number of bookmarks we checked for validation problems. | |||
|- | |||
| run_start_date || integer || Date we imported the data to Presto. | |||
|} | |||
=== Query Examples === | === Query Examples === | ||