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/automation/extension-based-hybrid-runbook-worker-install.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in
3
3
description: This article provides information about deploying the extension-based User Hybrid Runbook Worker to run runbooks on Windows or Linux machines in your on-premises datacenter or other cloud environment.
4
4
services: automation
5
5
ms.subservice: process-automation
6
-
ms.date: 11/09/2022
6
+
ms.date: 02/20/2023
7
7
ms.topic: how-to
8
8
#Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
9
9
---
@@ -35,7 +35,8 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
35
35
36
36
| Windows | Linux (x64)|
37
37
|---|---|
38
-
|● Windows Server 2022 (including Server Core) <br> ● Windows Server 2019 (including Server Core) <br> ● Windows Server 2016, version 1709 and 1803 (excluding Server Core), and <br> ● Windows Server 2012, 2012 R2 |● Debian GNU/Linux 10 and 11 <br> ● Ubuntu 22.04 LTS <br> ● SUSE Linux Enterprise Server 15.2, and 15.3 <br> ● Red Hat Enterprise Linux Server 7 and 8 |
38
+
|● Windows Server 2022 (including Server Core) <br> ● Windows Server 2019 (including Server Core) <br> ● Windows Server 2016, version 1709 and 1803 (excluding Server Core) <br> ● Windows Server 2012, 2012 R2 <br> ● Windows 10 Enterprise (including multi-session) and Pro |● Debian GNU/Linux 10 and 11 <br> ● Ubuntu 22.04 LTS <br> ● SUSE Linux Enterprise Server 15.2, and 15.3 <br> ● Red Hat Enterprise Linux Server 7 and 8 |
Copy file name to clipboardExpand all lines: articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Migrate an existing agent-based hybrid workers to extension-based-workers
3
3
description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers.
4
4
services: automation
5
5
ms.subservice: process-automation
6
-
ms.date: 12/29/2022
6
+
ms.date: 02/20/2023
7
7
ms.topic: how-to
8
8
#Customer intent: As a developer, I want to learn about extension so that I can efficiently migrate agent based hybrid workers to extension based workers.
9
9
---
@@ -50,7 +50,7 @@ The purpose of the Extension-based approach is to simplify the installation and
50
50
51
51
| Windows | Linux (x64)|
52
52
|---|---|
53
-
|● Windows Server 2022 (including Server Core) <br> ● Windows Server 2019 (including Server Core) <br> ● Windows Server 2016, version 1709 and 1803 (excluding Server Core), and <br> ● Windows Server 2012, 2012 R2 |● Debian GNU/Linux 10 and 11 <br> ● Ubuntu 22.04 LTS <br> ● SUSE Linux Enterprise Server 15.2, and 15.3 <br> ● Red Hat Enterprise Linux Server 7 and 8 |
53
+
|● Windows Server 2022 (including Server Core) <br> ● Windows Server 2019 (including Server Core) <br> ● Windows Server 2016, version 1709 and 1803 (excluding Server Core)<br> ● Windows Server 2012, 2012 R2 <br> ● Windows 10 Enterprise (including multi-session) and Pro|● Debian GNU/Linux 10 and 11 <br> ● Ubuntu 22.04 LTS <br> ● SUSE Linux Enterprise Server 15.2, and 15.3 <br> ● Red Hat Enterprise Linux Server 7 and 8 |
Copy file name to clipboardExpand all lines: articles/azure-monitor/autoscale/autoscale-overview.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,6 +139,7 @@ The following services are supported by autoscale:
139
139
| Azure API Management service |[Automatically scale an Azure API Management instance](../../api-management/api-management-howto-autoscale.md)|
140
140
| Azure Data Explorer Clusters |[Manage Azure Data Explorer clusters scaling to accommodate changing demand](/azure/data-explorer/manage-cluster-horizontal-scaling)|
141
141
| Azure Stream Analytics |[Autoscale streaming units (Preview)](../../stream-analytics/stream-analytics-autoscale.md)|
142
+
| Azure SignalR Service (Premium tier) |[Automatically scale units of an Azure SignalR service](https://learn.microsoft.com/azure/azure-signalr/signalr-howto-scale-autoscale)|
142
143
| Azure Machine Learning Workspace |[Autoscale an online endpoint](../../machine-learning/how-to-autoscale-endpoints.md)|
143
144
| Azure Spring Apps |[Set up autoscale for applications](../../spring-apps/how-to-setup-autoscale.md)|
144
145
| Media Services |[Autoscaling in Media Services](/azure/media-services/latest/release-notes#autoscaling)|
Copy file name to clipboardExpand all lines: articles/azure-monitor/data-sources.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -123,8 +123,8 @@ The configuration requirements and content of resource logs vary by resource typ
123
123
124
124
| Destination | Description | Reference |
125
125
|:---|:---|:---|
126
-
| Azure Monitor Logs | Send resource logs to Azure Monitor Logs for analysis with other collected log data. |[Collect Azure resource logs in Log Analytics workspace in Azure Monitor](essentials/resource-logs.md#send-to-azure-storage)|
127
-
| Storage | Send resource logs to Azure Storage for archiving. |[Archive Azure resource logs](essentials/resource-logs.md#send-to-log-analytics-workspace)|
126
+
| Azure Monitor Logs | Send resource logs to Azure Monitor Logs for analysis with other collected log data. |[Collect Azure resource logs in Log Analytics workspace in Azure Monitor](essentials/resource-logs.md#send-to-log-analytics-workspace)|
127
+
| Storage | Send resource logs to Azure Storage for archiving. |[Archive Azure resource logs](essentials/resource-logs.md#send-to-azure-storage)|
128
128
| Event Hubs | Stream resource logs to other locations using Event Hubs. |[Stream Azure resource logs to an event hub](essentials/resource-logs.md#send-to-azure-event-hubs)|
Copy file name to clipboardExpand all lines: articles/azure-monitor/logs/basic-logs-configure.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,7 @@ Configure a table for Basic logs if:
56
56
|[AMSKeyDeliveryRequests](/azure/azure-monitor/reference/tables/AMSKeyDeliveryRequests)| Azure Media Services HTTP request details for key, or license acquisition. |
57
57
|[AMSMediaAccountHealth](/azure/azure-monitor/reference/tables/AMSMediaAccountHealth)| Azure Media Services account health status. |
58
58
|[AMSStreamingEndpointRequests](/azure/azure-monitor/reference/tables/AMSStreamingEndpointRequests)| Azure Media Services information about requests to streaming endpoints. |
59
+
|[ASCAuditLogs](/azure/azure-monitor/reference/tables/ASCAuditLogs)| Azure Sphere audit logs generated by Azure Sphere service and devices. |
59
60
|[ASCDeviceEvents](/azure/azure-monitor/reference/tables/ASCDeviceEvents)| Azure Sphere devices operations, with information about event types, event categories, event classes, event descriptions etc. |
60
61
|[AVNMNetworkGroupMembershipChange](/azure/azure-monitor/reference/tables/AVNMNetworkGroupMembershipChange)| Azure Virtual Network Manager changes to network group membership of network resources. |
61
62
|[AZFWNetworkRule](/azure/azure-monitor/reference/tables/AZFWNetworkRule)| Azure Firewalls network rules logs including data plane packet and rule's attributes. |
Copy file name to clipboardExpand all lines: articles/azure-monitor/visualize/workbooks-jsonpath.md
+34-11Lines changed: 34 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,23 @@
1
1
---
2
2
title: Azure Monitor workbooks - Transform JSON data with JSONPath
3
-
description: Learn how to use JSONPath in Azure Monitor workbooks to transform the results of JSON data returned by a queried endpoint to the format that you want.
3
+
description: Use JSONPath in Azure Monitor workbooks to transform the JSON data results to a different data format.
4
4
services: azure-monitor
5
5
ms.workload: tbd
6
6
ms.tgt_pltfrm: ibiza
7
7
ms.topic: conceptual
8
-
ms.date: 07/05/2022
8
+
ms.date: 02/19/2023
9
9
---
10
10
11
11
# Use JSONPath to transform JSON data in workbooks
12
12
13
-
Workbooks can query data from many sources. Some endpoints, such as [Azure Resource Manager](../../azure-resource-manager/management/overview.md) or custom endpoint, can return results in JSON. If the JSON data returned by the queried endpoint isn't configured in a format that you want, JSONPath can be used to transform the results.
13
+
Workbooks can query data from many sources. Some endpoints, such as [Azure Resource Manager](../../azure-resource-manager/management/overview.md) or custom endpoints can return results in JSON. If the JSON data returned by the queried endpoint is in a format that you don't want, you can use JSONPath transformation to convert the JSON to a table structure. You can then use the table to plot [workbook visualizations](./workbooks-overview.md#visualizations).
14
14
15
-
JSONPath is a query language for JSON that's similar to XPath for XML. Like XPath, JSONPath allows for the extraction and filtration of data out of JSON structure.
16
-
17
-
By using JSONPath transformation, workbook authors can convert JSON into a table structure. The table can then be used to plot [workbook visualizations](./workbooks-overview.md#visualizations).
15
+
JSONPath is a query language for JSON that's similar to XPath for XML. Like XPath, JSONPath allows for the extraction and filtration of data out of the JSON structure.
18
16
19
17
## Use JSONPath
20
18
19
+
In this example, the JSON object represents a store's inventory. We're going to create a table of the store's available books listing their titles, authors, and prices.
20
+
21
21
1. Switch the workbook to edit mode by selecting **Edit**.
22
22
1. Use the **Add** > **Add query** link to add a query control to the workbook.
23
23
1. Select the data source as **JSON**.
@@ -56,9 +56,6 @@ By using JSONPath transformation, workbook authors can convert JSON into a table
56
56
}
57
57
}
58
58
```
59
-
60
-
Let's assume we're given the preceding JSON object as a representation of a store's inventory. Our task is to create a table of the store's available books by listing their titles, authors, and prices.
61
-
62
59
1. Select the **Result Settings** tab and switch the result format to **JSON Path**.
63
60
1. Apply the following JSON path settings:
64
61
@@ -70,12 +67,38 @@ Let's assume we're given the preceding JSON object as a representation of a stor
70
67
| Author | `$.author` |
71
68
| Price | `$.price` |
72
69
73
-
Column IDs will be the column headers. Column JSON paths fields represent the path from the root of the table to the column value.
70
+
Column IDs are the column headers. Column JSON paths fields represent the path from the root of the table to the column value.
74
71
75
-
1. Apply the preceding settings by selecting **Run Query**.
72
+
1. Select **Run Query**.
76
73
77
74

78
75
76
+
## Use regular expressions to covert values
77
+
78
+
You may have some data that isn't in a standard format. To use that data effectively, you would want to convert that data into a standard format.
79
+
80
+
In this example, the published date is in YYYMMMDD format. The code interprets this value as a numeric value, not text, resulting in right-justified numbers, instead of as a date.
81
+
82
+
You can use the **Type**, **RegEx Match** and **Replace With** fields in the result settings to convert the result into true dates.
83
+
84
+
|Result setting field |Description |
85
+
|---------|---------|
86
+
|Type|Allows you to explicitly change the type of the value returned by the API. This field us usually left unset, but you can use this field to force the value to a different type. |
87
+
|Regex Match|Allows you to enter a regular expression to take part (or parts) of the value returned by the API instead of the whole value. This field is usually combined with the **Replace With** field. |
88
+
|Replace With|Use this field to create the new value along with the regular expression. If this value is empty, the default is `$&`, which is the match result of the expression. See string.replace documentation to see other values that you can use to generate other output.|
89
+
90
+
91
+
To convert YYYMMDD format into YYYY-MM-DD format:
92
+
93
+
1. Select the Published row in the grid.
94
+
1. In the **Type** field, select Date/Time so that the column is usable in charts.
95
+
1. In the **Regex Match** field, use this regular expression: `([0-9]{4})([0-9]{2})([0-9]{2})`. This regular expression:
96
+
- matches a four digit number, then a two digit number, then another two digit number.
97
+
- The parentheses form capture groups to use in the next step.
98
+
1.In the **Replace With**, use this regular expression: `$1-$2-$3. This expression creates a new string with each captured group, with a hyphen between them, turning "12345678" into "1234-56-78").
99
+
1. Run the query again.
100
+
101
+

Copy file name to clipboardExpand all lines: articles/azure-resource-manager/management/tag-resources.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,9 @@ Resource tags support all cost-accruing services. To ensure that cost-accruing s
19
19
> [!WARNING]
20
20
> Tags are stored as plain text. Never add sensitive values to tags. Sensitive values could be exposed through many methods, including cost reports, commands that return existing tag definitions, deployment histories, exported templates, and monitoring logs.
21
21
22
+
> [!WARNING]
23
+
> Please be careful while using non-English language in your tags. It can cause decoding progress failure while loading your VM's metadata from IMDS (Instance Metadata Service).
24
+
22
25
> [!IMPORTANT]
23
26
> Tag names are case-insensitive for operations. A tag with a tag name, regardless of the casing, is updated or retrieved. However, the resource provider might keep the casing you provide for the tag name. You'll see that casing in cost reports.
Copy file name to clipboardExpand all lines: articles/azure-signalr/signalr-resource-faq.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -93,7 +93,7 @@ sections:
93
93
- question: |
94
94
Where does my data reside?
95
95
answer: |
96
-
Azure SignalR service works as a data processor service and doesn't store any customer content. Azure SignalR service processes customer data within the region the customer deploys the service instance in. If you use Azure SignalR Service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
96
+
Azure SignalR service works as a data processor service and doesn't store any customer data. Azure SignalR service processes customer data within the region the customer deploys the service instance in. If you use Azure SignalR Service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
97
97
98
98
- question: |
99
99
How do I choose between Azure SignalR service and Azure Web PubSub service?
Copy file name to clipboardExpand all lines: articles/azure-web-pubsub/resource-faq.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,4 +33,4 @@ Azure Web PubSub service is more suitable for situations where:
33
33
34
34
## Where does my data reside?
35
35
36
-
Azure Web PubSub service works as a data processor service and doesn't store any customer content. Azure Web PubSub service processes customer data within the region the customer deploys the service instance in. If you use Azure Web PubSub service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
36
+
Azure Web PubSub service works as a data processor service and doesn't store any customer data. Azure Web PubSub service processes customer data within the region the customer deploys the service instance in. If you use Azure Web PubSub service together with other Azure services, like Azure Storage for diagnostics, see [this white paper](https://azure.microsoft.com/resources/achieving-compliant-data-residency-and-security-with-azure/) for guidance about how to keep data residency in Azure regions.
0 commit comments