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
Copy file name to clipboardExpand all lines: articles/operator-insights/concept-data-quality-monitoring.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ ms.date: 10/24/2023
13
13
14
14
Every Data Product working on Azure Operator Insights platform has built-in support for data quality monitoring. Data quality is crucial because it ensures accurate, reliable, and trustworthy information for decision-making. It prevents costly mistakes, builds credibility with customers and regulators, and enables personalized experiences.
15
15
16
-
Azure Operator Insights platform monitors data quality when data is ingested into Data Product input storage (first AOI Data Product Storage block in following image) and after data is processed and made available to customers (AOI Data Product Compute in following image).
16
+
Azure Operator Insights platform monitors data quality when data is ingested into Data Product input storage (first AOI Data Product Storage block in the following image) and after data is processed and made available to customers (AOI Data Product Compute in following image).
17
17
18
-
:::image type="content" source="media/concept-data-quality-monitoring/operator-insights-architecture.jpg" alt-text="Diagram of Azure Operator Insights Data Product architecture." lightbox="media/concept-data-quality-monitoring/operator-insights-architecture.jpg":::
18
+
:::image type="content" source="media/concept-data-quality-monitoring/operator-insights-architecture.svg" alt-text="Diagram of Azure Operator Insights Data Product architecture. It shows ingestion from on-premises data sources, processing in a Data Product, and analysis and use in Logic Apps and Power BI." lightbox="media/concept-data-quality-monitoring/operator-insights-architecture.svg":::
19
19
20
20
## Quality dimensions
21
21
@@ -24,7 +24,7 @@ Data quality dimensions are the various aspects or characteristics that define t
24
24
- Accuracy - Refers to how well the data reflects reality, for example, correct names, addresses and up-to-date data. High data accuracy allows you to produce analytics that can be trusted and leads to correct reporting and confident decision-making.
25
25
- Completeness - Refers to whether all the data required for a particular use is present and available to be used. Completeness applies not only at the data item level but also at the record level. Completeness helps to understand if missing data will affect the reliability of insights from the data.
26
26
- Uniqueness - Refers to the absences of duplicates in a dataset.
27
-
- Consistency - Refers to whether the same data element does not conflict across different sources or over time. Consistency ensures that data is uniform and can be compared across different sources.
27
+
- Consistency - Refers to whether the same data element doesn't conflict across different sources or over time. Consistency ensures that data is uniform and can be compared across different sources.
28
28
- Timeliness - Refers to whether the data is up-to-date and available when needed. Timeliness ensures that data is relevant and useful for decision-making.
29
29
- Validity - Refers to whether the data conforms to a defined set of rules or constraints.
30
30
@@ -35,7 +35,7 @@ All data quality dimensions are covered by quality metrics produced by Azure Ope
35
35
- Basic - Standard set of checks across all data products.
36
36
- Custom - Custom set of checks, allowing all data products to implement checks that are specific to their product.
37
37
38
-
The basic quality metrics produced by the platform are available in a table below.
38
+
The basic quality metrics produced by the platform are available in the following table.
0 commit comments