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/azure-monitor/agents/data-collection-text-log.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
@@ -122,12 +122,12 @@ To create the data collection rule in the Azure portal:
122
122
123
123
1. Specify the following information:
124
124
125
-
-**File Pattern** - Identifies where the log files are located on the local disk. You can enter multiple file patterns separated by commas if your AMA is using Fluent Bit v1.5.1 or more.
125
+
-**File Pattern** - Identifies where the log files are located on the local disk. You can enter multiple file patterns separated by commas (on Linux, AMA version 1.26 or higher is required to collect from a comma-separated list of file patterns).
126
126
127
127
Examples of valid inputs:
128
128
- 20220122-MyLog.txt
129
129
- ProcessA_MyLog.txt
130
-
- ErrorsOnly_MyLog.txt, WarningOnly_MyLog.txt
130
+
- ErrorsOnly_MyLog.txt, WarningOnly_MyLog.txt
131
131
132
132
> [!NOTE]
133
133
> Multiple log files of the same type commonly exist in the same directory. For example, a machine might create a new file every day to prevent the log file from growing too large. To collect log data in this scenario, you can use a file wildcard. Use the format `C:\directoryA\directoryB\*MyLog.txt` for Windows and `/var/*.log` for Linux. There is no support for directory wildcards.
Copy file name to clipboardExpand all lines: articles/azure-video-indexer/release-notes.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,6 +20,15 @@ To stay up-to-date with the most recent Azure Video Indexer developments, this a
20
20
21
21
## May 2023
22
22
23
+
### API breaking change
24
+
25
+
We're introducing a change in behavior that may break your existing query logic. The change is in the **List** and **Search** APIs, find a detailed change between the current and the new behavior in a table that follows. You may need to update your code to utilize the [new APIs](https://api-portal.videoindexer.ai/).
26
+
27
+
|API |Current|New|The breaking change|
28
+
|---|---|---|---|
29
+
|List Videos|• List all videos/projects according to 'IsBase' boolean parameter. If 'IsBase' is not defined, list both.<br/>• Returns videos in all states (In progress/Proccessed/Failed). |• List Videos API will Return only videos (with paging) in all states.<br/>• List Projects API will return only projects (with paging).|• List videos API was divided into two new API’s **List Videos** and **List Projects**<br/>• The 'IsBase' parameter no longer has a meaning. |
30
+
|Search Videos|• Search all videos/projects according to 'IsBase' boolean parameter. If 'IsBase' is not defined, search both. <br/>• Search videos in all states (In progress/Proccessed/Failed). |Search only processed videos.|• Search Videos API will only search videos and not projects.<br/>• The 'IsBase' parameter no longer has a meaning.<br/>• Search Videos API will only search Processed videos (and not Failed/InProgress ones.)|
31
+
23
32
### Support for HTTP/2
24
33
25
34
Added support for HTTP/2 for our [Data Plane API](https://api-portal.videoindexer.ai/). [HTTP/2](https://en.wikipedia.org/wiki/HTTP/2) offers several benefits over HTTP/1.1, which continues to be supported for backwards compatibility. One of the main benefits of HTTP/2 is increased performance, better reliability and reduced system resource requirements over HTTP/1.1. With this change we now support HTTP/2 for both the Video Indexer [Portal](https://videoindexer.ai/) and our Data Plane API. We advise to update your code to take advantage of this change.
2. Use the [Add Member API](https://microsoft.github.io/meds-samples/rest-apis/index.html?page=/meds-samples/rest-apis/entitlements_openapi.yaml#/add-member-api/addMemberUsingPOST) to add the application ID of the user-assigned managed identity to the appropriate entitlement groups.
101
+
2. Use the [Add Member API](https://microsoft.github.io/adme-samples/rest-apis/index.html?page=/adme-samples/rest-apis/M12/entitlements_openapi.yaml#/add-member-api) to add the application ID of the user-assigned managed identity to the appropriate entitlement groups.
102
102
103
103
> [!NOTE]
104
104
> In the following commands, be sure to use the application ID of the managed identity and not the object ID.
Copy file name to clipboardExpand all lines: articles/virtual-machines/image-builder-api-update-release-notes.md
+21-2Lines changed: 21 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: kof-f
5
5
ms.service: virtual-machines
6
6
ms.topic: conceptual
7
7
ms.workload: infrastructure
8
-
ms.date: 04/04/2022
8
+
ms.date: 05/08/2023
9
9
ms.reviewer: erd
10
10
ms.subservice: image-builder
11
11
ms.custom: references_regions
@@ -17,11 +17,30 @@ ms.custom: references_regions
17
17
18
18
**Applies to:**:heavy_check_mark: Linux VMs :heavy_check_mark: Windows VMs :heavy_check_mark: Flexible scale sets :heavy_check_mark: Uniform scale sets
19
19
20
-
This article contains all major API changes and feature updates for the Azure VM Image Builder service.
20
+
This article contains all major API changes and feature updates for the Azure VM Image Builder (AIB) service.
21
21
22
22
## API releases
23
23
24
24
25
+
### Version 2022-07-01
26
+
27
+
**Improvements**
28
+
- Added support to use the latest image version stored in Azure Compute Gallery as the source for the image template
29
+
- Added `versioning` to support generating version numbers for image distributions. For more information, see [properties: versioning](../virtual-machines/linux/image-builder-json.md#versioning)
30
+
- Added support for per region configuration when distributing to Azure Compute Gallery. For more information, see [Distribute:targetRegions](../virtual-machines/linux/image-builder-json.md#distribute-targetregions)
31
+
- Added new 'File' validation type. For more information, see [validate properties](../virtual-machines/linux/image-builder-json.md#properties-validate)
32
+
- VHDs can now be distributed to a custom blob or container in a custom storage account. For more information, see [Distribute: VHD](../virtual-machines/linux/image-builder-json.md#distribute-vhd)
33
+
- Added support for using a [Direct Shared Gallery](/azure/virtual-machines/shared-image-galleries?tabs=azure-cli#sharing) image as the source for the image template
34
+
35
+
36
+
**Changes**
37
+
-`replicationRegions` is now deprecated for gallery distributions. For more information, use [gallery-replicated-regions](/cli/azure/image/builder/output?view=azure-cli-latest#az-image-builder-output-add-examples&preserve-view=true)
38
+
- VHDs can now be distributed to a custom blob or container in a custom storage account
39
+
-`targetRegions` array added and applied only to "SharedImage" type distribute. For more information on `targetRegions`, see [Azure Compute Gallery](../../articles/virtual-machines/azure-compute-gallery.md)
40
+
- Added support for using a [Direct Shared Gallery](/azure/virtual-machines/shared-image-galleries?tabs=azure-cli#sharing) image as the source for the image template. Direct Shared Gallery is currently in preview.
0 commit comments