CloudServices/Sync/ReDash: Difference between revisions

CloudServices/Sync/ReDash (view source)

Revision as of 18:35, 20 June 2017

1,143 bytes added , 20 June 2017

→‎telemetry.sync_bmk_validation_problems: finished table and added table description

Adavis

53

edits

@@ Line 202: / Line 202: @@
 ==== telemetry.sync_bmk_validation_problems ====
+This table was rolled-up using the following workbook:
+https://gist.github.com/kitcambridge/364f56182f3e96fb3131bf38ff648609
+This table has a row for every validation problem detected during validation.
+'''Example:'''
+If a user has 4 different validation problems, we will log each problem in their own row.
+'''Logic used for format:'''
+This choice was made to avoid having endless amounts of columns representing each validation problem checked (which would mostly all be null) and to avoid having to add columns as we detect new types of validation problems.
 {| class="wikitable"
@@ Line 229: / Line 239: @@
 | status || row(sync varchar, service varchar) || The status of sync after completion, or null is both statuses record success.
 |-
-| engine_name || string || Should always be '''bookmarks''' in this table.
+| engine_name || varchar || Should always be '''bookmarks''' in this table.
 |-
 | engine_status || varchar || The status of this engine after sync completed, or null if the status reflects success.
@@ Line 235: / Line 245: @@
 | engine_failure_reason || row(name varchar, value varchar) || Details of any errors recorded during the sync of this engine, or null on success.
 |-
-| Example || Example || Example
+| engine_has_problems || true/false || engine_has_problems is always going to be true in sync_bmk_validation_problems. Used to filter results out of all_engine_validation_results
 |-
-| Example || Example || Example
+| engine_validation_version || integer || Version of the validator used to get this data.
 |-
-| Example || Example || Example
+| engine_validation_checked || bigint || Number of records the validator checked in this engine.
 |-
-| Example || Example || Example
+| engine_validation_took || bigint || How long validation took for this engine.
 |-
-| Example || Example || Example
+| engine_validation_problem_name || varchar || Name of error recorded during the validation. Will never be null since this table only includes validation problems.
 |-
-| Example || Example || Example
+| engine_validation_problem_count || integer || Number of bookmarks afflicted by the problem during the validation check.
 |-
-| Example || Example || Example
+| run_start_date || integer || Date added to presto. (e.g. 20170331)
 |}