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
Workbook authors can use KQL queries that transform the underlying resource data to select a result set that can visualized as text, charts, or grids.
36
+
You can use Kusto query language (KQL) queries that transform the underlying resource data to select a result set that can be visualized as text, charts, or grids.
36
37
37
-

38
+

38
39
39
-
Workbook authors can easily query across multiple resources creating a truly unified rich reporting experience.
40
+
You can easily query across multiple resources to create a unified rich reporting experience.
40
41
41
42
## Metrics
42
43
43
-
Azure resources emit [metrics](../essentials/data-platform-metrics.md) that can be accessed via workbooks. Metrics can be accessed in workbooks through a specialized control that allows you to specify the target resources, the desired metrics, and their aggregation. This data can then be plotted in charts or grids.
44
+
Azure resources emit [metrics](../essentials/data-platform-metrics.md) that can be accessed via workbooks. Metrics can be accessed in workbooks through a specialized control that allows you to specify the target resources, the desired metrics, and their aggregation. You can then plot this data in charts or grids.
44
45
45
-

46
+

46
47
47
-

48
+

48
49
49
50
## Azure Resource Graph
50
51
51
-
Workbooks support querying for resources and their metadata using Azure Resource Graph (ARG). This functionality is primarily used to build custom query scopes for reports. The resource scope is expressed via a KQL-subset that ARG supports – which is often sufficient for common use cases.
52
+
Workbooks support querying for resources and their metadata by using Azure Resource Graph. This functionality is primarily used to build custom query scopes for reports. The resource scope is expressed via a KQLsubset that Resource Graph supports, which is often sufficient for common use cases.
52
53
53
-
To make a query control use this data source, use the Query type drop-down to choose Azure Resource Graph and select the subscriptions to target. Use the Query control to add the ARG KQL-subset that selects an interesting resource subset.
54
+
To make a query control that uses this data source, use the **Query type** dropdown and select **Azure Resource Graph**. Then select the subscriptions to target. Use **Query control** to add the Resource Graph KQLsubset that selects an interesting resource subset.
54
55
55
-

56
+

56
57
57
58
## Azure Resource Manager
58
59
59
-
Workbook supports Azure Resource Manager REST operations. This allows the ability to query management.azure.com endpoint without the need to provide your own authorization header token.
60
+
Azure Workbooks supports Azure Resource Manager REST operations so that you can query the management.azure.com endpoint without providing your own authorization header token.
60
61
61
-
To make a query control use this data source, use the Data source drop-down to choose Azure Resource Manager. Provide the appropriate parameters such as Http method, url path, headers, url parameters and/or body.
62
+
To make a query control that uses this data source, use the **Data source** dropdown and select **Azure Resource Manager**. Provide the appropriate parameters, such as **Http method**, **url path**, **headers**, **url parameters**, and**body**.
62
63
63
64
> [!NOTE]
64
65
> Only GET, POST, and HEAD operations are currently supported.
65
66
66
67
## Azure Data Explorer
67
68
68
69
Workbooks now have support for querying from [Azure Data Explorer](/azure/data-explorer/) clusters with the powerful [Kusto](/azure/kusto/query/index) query language.
69
-
For the **Cluster Name** field, you should add the region name following the cluster name. For example:*mycluster.westeurope*.
70
+
For the **Cluster Name** field, add the region name following the cluster name. An example is*mycluster.westeurope*.
70
71
71
-

72
+

72
73
73
74
## JSON
74
75
75
-
The JSON provider allows you to create a query result from static JSON content. It is most commonly used in Parameters to create dropdown parameters of static values. Simple JSON arrays or objects will automatically be converted into grid rows and columns. For more specific behaviors, you can use the Results tab and JSONPath settings to configure columns.
76
+
The JSON provider allows you to create a query result from static JSON content. It's most commonly used in parameters to create dropdown parameters of static values. Simple JSON arrays or objects will automatically be converted into grid rows and columns. For more specific behaviors, you can use the **Results** tab and JSONPath settings to configure columns.
76
77
77
78
> [!NOTE]
78
-
> Do not include any sensitive information in any fields (headers, parameters, body, url), since they will be visible to all of the Workbook users.
79
+
> Do *not* include sensitive information in fields like headers, parameters, body, and URL, because they'll be visible to all the workbook users.
79
80
80
81
This provider supports [JSONPath](workbooks-jsonpath.md).
81
82
82
83
## Merge
83
84
84
-
Merging data from different sources can enhance the insights experience. An example is augmenting active alert information with related metric data. This 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.
85
+
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.
85
86
86
-
Workbooks allow not just the querying of different data sources, but also provides simple controls that allow you to merge or join the data to provide rich insights. The **merge** control is the way to achieve it.
87
+
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.
87
88
88
-
### Combining alerting data with Log Analytics VM performance data
89
+
### Combine alerting data with Log Analytics VM performance data
89
90
90
-
The example below combines alerting data with Log Analytics VM performance data to get a rich insights grid.
91
+
The following example combines alerting data with Log Analytics VM performance data to get a rich insights grid.
91
92
92
-

93
+

93
94
94
-
### Using merge control to combine Azure Resource Graph and Log Analytics data
95
+
### Use merge control to combine Resource Graph and Log Analytics data
95
96
96
-
Here is a tutorial on using the merge control to combine Azure Resource Graph and Log Analytics data:
97
+
Watch this tutorial on using the merge control to combine Resource Graph and Log Analytics data:
97
98
98
99
[](https://www.youtube.com/watch?v=7nWP_YRzxHg"Video showing how to combine data from different sources in workbooks.")
99
100
@@ -113,31 +114,35 @@ Workbooks support these merges:
113
114
114
115
## Custom endpoint
115
116
116
-
Workbooks support getting data from any external source. If your data lives outside Azure you can bring it to Workbooks by using this data source type.
117
+
Workbooks support getting data from any external source. If your data lives outside Azure, you can bring it to workbooks by using this data source type.
117
118
118
-
To make a query control use this data source, use the **Data source**drop-down to choose**Custom Endpoint**. Provide the appropriate parameters such as **Http method**, **url**, **headers**, **url parameters**, and/or**body**. Make sure your data source supports [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) otherwise the request will fail.
119
+
To make a query control that uses this data source, use the **Data source**dropdown and select**Custom Endpoint**. Provide the appropriate parameters, such as **Http method**, **url**, **headers**, **url parameters**, and **body**. Make sure your data source supports [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS). Otherwise, the request will fail.
119
120
120
-
To avoid automatically making calls to untrusted hosts when using templates, the user needs to mark the used hosts as trusted. This can be done by either selecting the **Add as trusted**button, or by adding it as a trusted host in Workbook settings. These settings will be saved in [browsers that support IndexDb with web workers](https://caniuse.com/#feat=indexeddb).
121
+
To avoid automatically making calls to untrusted hosts when you use templates, you need to mark the used hosts as trusted. You can either select **Add as trusted** or add it as a trusted host in workbook settings. These settings will be saved in [browsers that support IndexDb with web workers](https://caniuse.com/#feat=indexeddb).
121
122
122
123
This provider supports [JSONPath](workbooks-jsonpath.md).
124
+
123
125
## Workload health
124
126
125
-
Azure Monitor has functionality that proactively monitors the availability and performance of Windows or Linux guest operating systems. Azure Monitor models key components and their relationships, criteria for how to measure the health of those components, and which components alert you when an unhealthy condition is detected. Workbooks allow users to use this information to create rich interactive reports.
127
+
Azure Monitor has functionality that proactively monitors the availability and performance of Windows or Linux guest operating systems. Azure Monitor models key components and their relationships, criteria for how to measure the health of those components, and which components alert you when an unhealthy condition is detected. With workbooks, you can use this information to create rich interactive reports.
126
128
127
-
To make a query control use this data source, use the **Query type**drop-down to choose Workload Health and select subscription, resource group or VM resources to target. Use the health filter drop downs to select an interesting subset of health incidents for your analytic needs.
129
+
To make a query control that uses this data source, use the **Query type**dropdown to select **Workload Health**. Then select subscription, resource group, or VM resources to target. Use the health filter dropdowns to select an interesting subset of health incidents for your analytic needs.
128
130
129
-

131
+

130
132
131
133
## Azure resource health
132
134
133
-
Workbooks support getting Azure resource health and combining it with other data sources to create rich, interactive health reports
135
+
Workbooks support getting Azure resource health and combining it with other data sources to create rich, interactive health reports.
134
136
135
-
To make a query control use this data source, use the **Query type**drop-down to choose Azure health and select the resources to target. Use the health filter drop downs to select an interesting subset of resource issues for your analytic needs.
137
+
To make a query control that uses this data source, use the **Query type**dropdown and select **Azure health**. Then select the resources to target. Use the health filter dropdowns to select an interesting subset of resource issues for your analytic needs.
136
138
137
-

139
+

138
140
139
141
## Azure RBAC
140
-
The Azure RBAC provider allows you to check permissions on resources. It is most commonly used in parameter to check if the correct RBAC are set up. A use case would be to create a parameter to check deployment permission and then notify the user if they don't have deployment permission. Simple JSON arrays or objects will automatically be converted into grid rows and columns or text with a 'hasPermission' column with either true or false. The permission is checked on each resource and then either 'or' or 'and' to get the result. The [operations or actions](../../role-based-access-control/resource-provider-operations.md) can be a string or an array.
142
+
143
+
The Azure role-based access control (RBAC) provider allows you to check permissions on resources. It's most commonly used in parameters to check if the correct RBACs are set up. A use case would be to create a parameter to check deployment permission and then notify the user if they don't have deployment permission.
144
+
145
+
Simple JSON arrays or objects will automatically be converted into grid rows and columns or text with a `hasPermission` column with either true or false. The permission is checked on each resource and then either `or` or `and` to get the result. The [operations or actions](../../role-based-access-control/resource-provider-operations.md) can be a string or an array.
141
146
142
147
**String:**
143
148
```
@@ -151,12 +156,12 @@ The Azure RBAC provider allows you to check permissions on resources. It is most
151
156
152
157
## Change Analysis (preview)
153
158
154
-
To make a query control using [Application Change Analysis](../app/change-analysis.md) as the data source, use the **Data source**drop-down and choose *Change Analysis (preview)* and select a single resource. Changes for up to the last 14 days can be shown. The *Level* drop-down can be used to filter between "Important", "Normal", and "Noisy" changes, and this drop down supports workbook parameters of type [drop down](workbooks-dropdowns.md).
159
+
To make a query control that uses [Application Change Analysis](../app/change-analysis.md) as the data source, use the **Data source**dropdown and select **Change Analysis (preview)**. Then select a single resource. Changes for up to the last 14 days can be shown. Use the **Level** dropdown to filter between **Important**, **Normal**, and **Noisy** changes. This dropdown supports workbook parameters of the type [drop down](workbooks-dropdowns.md).
155
160
156
161
> [!div class="mx-imgBorder"]
157
-
> 
162
+
> 
158
163
159
164
## Next steps
160
165
161
-
-[Getting started with Azure Workbooks](workbooks-getting-started.md)
162
-
-[Create an Azure Workbook](workbooks-create-workbook.md).
166
+
-[Get started with Azure Workbooks](workbooks-getting-started.md)
167
+
-[Create an Azure workbook](workbooks-create-workbook.md)
0 commit comments