You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Task]: Video series 10 - Metrics and analytics operations #234
Folder docs/video-series/10-metrics-and-analytics. About four minutes. Assumes video 9. This is the last video in the series.
A load writes timings into the OPS database. Open the resource group load metrics dialog for a retail-sources run: this run, and a short look at history.
Create operational analytics (EDW Journey toolbar or Tools) reads that OPS database and generates a source model, a raw vault, a Business Vault, a dimensional model, and two load workflows under retail-example/models/ops-analytics/. Show the dialog and the generated source model. Do not walk those models table by table.
The generated group is ops-analytics. It stays separate from retail-sources because it describes the platform, not the retail business. The point of the beat is that operations walks the same road as the warehouse, pointed at OPS.
When a business number looks wrong, open retail-example/models/f_orders-upstream.hlv. The lineage view is the path from the fact back to the sources. One still. Do not configure Marquez.
An execution map is the picture of a single run. One sentence. A still only if it is already easy to capture.
Close on where to go next: Getting started — building an EDW, the training modules, and the longer tutorials under docs/video-tutorials/.
Activity
Issue #234 Add the metrics and analytics episode of the getting-start…
Issue #234 Add the metrics and analytics episode translations.