Skip to content

Commit 5b1d419

Browse files
authored
Apply suggestions from PR review
1 parent 767431b commit 5b1d419

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/azure-monitor/visualize/workbooks-data-sources.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -98,12 +98,12 @@ This provider supports [JSONPath](workbooks-jsonpath.md).
9898

9999
Merging data from different sources can enhance the insights experience. An example is augmenting active alert information with related metric data. Merging data allows users to see not just the effect (an active alert) but also potential causes, for example, high CPU usage. The monitoring domain has numerous such correlatable data sources that are often critical to the triage and diagnostic workflow.
100100

101-
With workbooks, you can query different data sources. Workbooks also provide simple controls that you can use to merge or join data to provide rich insights. The *merge* control is the way to achieve it. A single merge data source can do many merges in one step. For example, a *single* merge data source can merge results from a step using Azure Resource Graph with Azure Metrics, and then merge that result with another step using the Azure Resource Manager (ARM) data source in one query item.
101+
With workbooks, you can query different data sources. Workbooks also provide simple controls that you can use to merge or join data to provide rich insights. The *merge* control is the way to achieve it. A single merge data source can do many merges in one step. For example, a *single* merge data source can merge results from a step using Azure Resource Graph with Azure Metrics, and then merge that result with another step using the Azure Resource Manager data source in one query item.
102102

103103
> [!NOTE]
104-
> While hidden query and metrics steps will run if referenced by a merge step, hidden query items using the merge data source do not run while hidden.
105-
> A step using merge that attempts to reference a hidden step using merge data source will not run until that hidden step becomes visible.
106-
> A single merge step can merge many data sources at once. There is very rarely a case where a merge data source will reference another merge data source.
104+
> Although hidden query and metrics steps run if they're referenced by a merge step, hidden query items that use the merge data source don't run while hidden.
105+
> A step that uses merge and attempts to reference a hidden step by using merge data source won't run until that hidden step becomes visible.
106+
> A single merge step can merge many data sources at once. There's rarely a case where a merge data source will reference another merge data source.
107107
108108

109109
### Combine alerting data with Log Analytics VM performance data

0 commit comments

Comments
 (0)