Skip to content

Commit a16f719

Browse files
authored
Merge pull request #227931 from MicrosoftDocs/main
Publish to live, Monday 4 AM PST, 2/20
2 parents 389c574 + e4c522d commit a16f719

File tree

69 files changed

+351
-156
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

69 files changed

+351
-156
lines changed

articles/automation/extension-based-hybrid-runbook-worker-install.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in
33
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.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 11/09/2022
6+
ms.date: 02/20/2023
77
ms.topic: how-to
88
#Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
99
---
@@ -35,7 +35,8 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
3535

3636
| Windows | Linux (x64)|
3737
|---|---|
38-
| &#9679; Windows Server 2022 (including Server Core) <br> &#9679; Windows Server 2019 (including Server Core) <br> &#9679; Windows Server 2016, version 1709 and 1803 (excluding Server Core), and <br> &#9679; Windows Server 2012, 2012 R2 | &#9679; Debian GNU/Linux 10 and 11 <br> &#9679; Ubuntu 22.04 LTS <br> &#9679; SUSE Linux Enterprise Server 15.2, and 15.3 <br> &#9679; Red Hat Enterprise Linux Server 7 and 8 |
38+
| &#9679; Windows Server 2022 (including Server Core) <br> &#9679; Windows Server 2019 (including Server Core) <br> &#9679; Windows Server 2016, version 1709 and 1803 (excluding Server Core) <br> &#9679; Windows Server 2012, 2012 R2 <br> &#9679; Windows 10 Enterprise (including multi-session) and Pro | &#9679; Debian GNU/Linux 10 and 11 <br> &#9679; Ubuntu 22.04 LTS <br> &#9679; SUSE Linux Enterprise Server 15.2, and 15.3 <br> &#9679; Red Hat Enterprise Linux Server 7 and 8 |
39+
3940

4041
### Other Requirements
4142

articles/automation/migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Migrate an existing agent-based hybrid workers to extension-based-workers
33
description: This article provides information on how to migrate an existing agent-based hybrid worker to extension based workers.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 12/29/2022
6+
ms.date: 02/20/2023
77
ms.topic: how-to
88
#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.
99
---
@@ -50,7 +50,7 @@ The purpose of the Extension-based approach is to simplify the installation and
5050

5151
| Windows | Linux (x64)|
5252
|---|---|
53-
| &#9679; Windows Server 2022 (including Server Core) <br> &#9679; Windows Server 2019 (including Server Core) <br> &#9679; Windows Server 2016, version 1709 and 1803 (excluding Server Core), and <br> &#9679; Windows Server 2012, 2012 R2 | &#9679; Debian GNU/Linux 10 and 11 <br> &#9679; Ubuntu 22.04 LTS <br> &#9679; SUSE Linux Enterprise Server 15.2, and 15.3 <br> &#9679; Red Hat Enterprise Linux Server 7 and 8 |
53+
| &#9679; Windows Server 2022 (including Server Core) <br> &#9679; Windows Server 2019 (including Server Core) <br> &#9679; Windows Server 2016, version 1709 and 1803 (excluding Server Core) <br> &#9679; Windows Server 2012, 2012 R2 <br> &#9679; Windows 10 Enterprise (including multi-session) and Pro| &#9679; Debian GNU/Linux 10 and 11 <br> &#9679; Ubuntu 22.04 LTS <br> &#9679; SUSE Linux Enterprise Server 15.2, and 15.3 <br> &#9679; Red Hat Enterprise Linux Server 7 and 8 |
5454

5555
### Other Requirements
5656

articles/azure-monitor/autoscale/autoscale-overview.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -139,6 +139,7 @@ The following services are supported by autoscale:
139139
| Azure API Management service | [Automatically scale an Azure API Management instance](../../api-management/api-management-howto-autoscale.md) |
140140
| Azure Data Explorer Clusters | [Manage Azure Data Explorer clusters scaling to accommodate changing demand](/azure/data-explorer/manage-cluster-horizontal-scaling) |
141141
| 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) |
142143
| Azure Machine Learning Workspace | [Autoscale an online endpoint](../../machine-learning/how-to-autoscale-endpoints.md) |
143144
| Azure Spring Apps | [Set up autoscale for applications](../../spring-apps/how-to-setup-autoscale.md) |
144145
| Media Services | [Autoscaling in Media Services](/azure/media-services/latest/release-notes#autoscaling) |

articles/azure-monitor/data-sources.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -123,8 +123,8 @@ The configuration requirements and content of resource logs vary by resource typ
123123

124124
| Destination | Description | Reference |
125125
|:---|:---|:---|
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) |
128128
| 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) |
129129

130130
## Operating system (guest)

articles/azure-monitor/logs/basic-logs-configure.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,7 @@ Configure a table for Basic logs if:
5656
| [AMSKeyDeliveryRequests](/azure/azure-monitor/reference/tables/AMSKeyDeliveryRequests) | Azure Media Services HTTP request details for key, or license acquisition. |
5757
| [AMSMediaAccountHealth](/azure/azure-monitor/reference/tables/AMSMediaAccountHealth) | Azure Media Services account health status. |
5858
| [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. |
5960
| [ASCDeviceEvents](/azure/azure-monitor/reference/tables/ASCDeviceEvents) | Azure Sphere devices operations, with information about event types, event categories, event classes, event descriptions etc. |
6061
| [AVNMNetworkGroupMembershipChange](/azure/azure-monitor/reference/tables/AVNMNetworkGroupMembershipChange) | Azure Virtual Network Manager changes to network group membership of network resources. |
6162
| [AZFWNetworkRule](/azure/azure-monitor/reference/tables/AZFWNetworkRule) | Azure Firewalls network rules logs including data plane packet and rule's attributes. |
19.4 KB
Loading

articles/azure-monitor/visualize/workbooks-jsonpath.md

Lines changed: 34 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,23 @@
11
---
22
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.
44
services: azure-monitor
55
ms.workload: tbd
66
ms.tgt_pltfrm: ibiza
77
ms.topic: conceptual
8-
ms.date: 07/05/2022
8+
ms.date: 02/19/2023
99
---
1010

1111
# Use JSONPath to transform JSON data in workbooks
1212

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).
1414

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.
1816

1917
## Use JSONPath
2018

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+
2121
1. Switch the workbook to edit mode by selecting **Edit**.
2222
1. Use the **Add** > **Add query** link to add a query control to the workbook.
2323
1. Select the data source as **JSON**.
@@ -56,9 +56,6 @@ By using JSONPath transformation, workbook authors can convert JSON into a table
5656
}
5757
}
5858
```
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-
6259
1. Select the **Result Settings** tab and switch the result format to **JSON Path**.
6360
1. Apply the following JSON path settings:
6461

@@ -70,12 +67,38 @@ Let's assume we're given the preceding JSON object as a representation of a stor
7067
| Author | `$.author` |
7168
| Price | `$.price` |
7269

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.
7471

75-
1. Apply the preceding settings by selecting **Run Query**.
72+
1. Select **Run Query**.
7673

7774
![Screenshot that shows editing a query item with JSON data source and JSON path result format.](./media/workbooks-jsonpath/query-jsonpath.png)
7875

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+
![Screenshot that shows JSONpath converted to date-time format.](./media/workbooks-jsonpath/workbooks-jsonpath-convert-date-time.png)
79102
## Next steps
80103

81104
- [Workbooks overview](./workbooks-overview.md)

articles/azure-resource-manager/management/tag-resources.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,9 @@ Resource tags support all cost-accruing services. To ensure that cost-accruing s
1919
> [!WARNING]
2020
> 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.
2121
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+
2225
> [!IMPORTANT]
2326
> 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.
2427
>

articles/azure-signalr/signalr-resource-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ sections:
9393
- question: |
9494
Where does my data reside?
9595
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.
9797
9898
- question: |
9999
How do I choose between Azure SignalR service and Azure Web PubSub service?

articles/azure-web-pubsub/resource-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,4 +33,4 @@ Azure Web PubSub service is more suitable for situations where:
3333

3434
## Where does my data reside?
3535

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

Comments
 (0)