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
# Customer intent: As a user or dev ops administrator, I want to understand how set up autoscale with more than one profile so I can scale my resources with more flexibility.
@@ -35,18 +35,18 @@ Each time the autoscale service runs, the profiles are evaluated in the followin
35
35
1. Recurring profiles
36
36
1. Default profile
37
37
38
-
If a profile's date and time settings match the current time, autoscale will apply that profile's rules and capacity limits. Only the first applicable profile is used.
38
+
If a profile's date and time settings match the current time, autoscale applies that profile's rules and capacity limits. Only the first applicable profile is used.
39
39
40
-
The example below shows an autoscale setting with a default profile and recurring profile.
40
+
The following example shows an autoscale setting with a default profile and recurring profile.
41
41
42
42
:::image type="content" source="./media/autoscale-multiple-profiles/autoscale-default-recurring-profiles.png" lightbox="./media/autoscale-multiple-profiles/autoscale-default-recurring-profiles.png" alt-text="A screenshot showing an autoscale setting with default and recurring profile or scale condition.":::
43
43
44
-
In the above example, on Monday after 3 AM, the recurring profile will cease to be used. If the instance count is less than 3, autoscale scales to the new minimum of three. Autoscale continues to use this profile and scales based on CPU% until Monday at 8 PM. At all other times scaling will be done according to the default profile, based on the number of requests. After 8 PM on Monday, autoscale switches to the default profile. If for example, the number of instances at the time is 12, autoscale scales in to 10, which the maximum allowed for the default profile.
44
+
In the example above, on Monday after 3 AM, the recurring profile will cease to be used. If the instance count is less than 3, autoscale scales to the new minimum of three. Autoscale continues to use this profile and scales based on CPU% until Monday at 8 PM. At all other times scaling is done according to the default profile, based on the number of requests. After 8 PM on Monday, autoscale switches to the default profile. If for example, the number of instances at the time is 12, autoscale scales in to 10, which the maximum allowed for the default profile.
45
45
46
46
## Multiple contiguous profiles
47
47
Autoscale transitions between profiles based on their start times. The end time for a given profile is determined by the start time of the following profile.
48
48
49
-
In the portal, the end time field becomes the next start time for the default profile. You can't specify the same time for the end of one profile and the start of the next. The portal will force the end time to be one minute before the start time of the following profile. During this minute, the default profile will become active. If you don't want the default profile to become active between recurring profiles, leave the end time field empty.
49
+
In the portal, the end time field becomes the next start time for the default profile. You can't specify the same time for the end of one profile and the start of the next. The portal forces the end time to be one minute before the start time of the following profile. During this minute, the default profile becomes active. If you don't want the default profile to become active between recurring profiles, leave the end time field empty.
50
50
51
51
> [!TIP]
52
52
> To set up multiple contiguous profiles using the portal, leave the end time empty. The current profile will stop being used when the next profile becomes active. Only specify an end time when you want to revert to the default profile.
@@ -60,16 +60,16 @@ When creating multiple profiles using templates, the CLI, and PowerShell, follow
60
60
61
61
See the autoscale section of the [ARM template resource definition](/azure/templates/microsoft.insights/autoscalesettings) for a full template reference.
62
62
63
-
There is no specification in the template for end time. A profile will remain active until the next profile's start time.
63
+
There's no specification in the template for end time. A profile will remain active until the next profile's start time.
64
64
65
65
66
66
## Add a recurring profile using ARM templates
67
67
68
-
The example below shows how to create two recurring profiles. One profile for weekends from 00:01 on Saturday morning and a second Weekday profile starting on Mondays at 04:00. That means that the weekend profile will start on Saturday morning at one minute passed midnight and end on Monday morning at 04:00. The Weekday profile will start at 4am on Monday and end just after midnight on Saturday morning.
68
+
The following example shows how to create two recurring profiles. One profile for weekends from 00:01 on Saturday morning and a second Weekday profile starting on Mondays at 04:00. That means that the weekend profile starts on Saturday morning at one minute passed midnight and end on Monday morning at 04:00. The Weekday profile will start at 4am on Monday and end just after midnight on Saturday morning.
69
69
70
70
Use the following command to deploy the template:
71
71
`az deployment group create --name VMSS1-Autoscale-607 --resource-group rg-vmss1 --template-file VMSS1-autoscale.json`
72
-
where *VMSS1-autoscale.json* is the file containing the JSON object below.
72
+
where *VMSS1-autoscale.json* is the file containing the following JSON object.
73
73
74
74
```JSON
75
75
{
@@ -85,7 +85,7 @@ where *VMSS1-autoscale.json* is the file containing the JSON object below.
PowerShell can be used to create multiple profiles in your autoscale settings.
269
270
270
-
See the [PowerShell Az.Monitor Reference](/powershell/module/az.monitor/#monitor) for the full set of autoscale PowerShell commands.
271
+
See the [PowerShell Az PowerShell module.Monitor Reference](/powershell/module/az.monitor/#monitor) for the full set of autoscale PowerShell commands.
271
272
272
273
The following steps show how to create an autoscale profile using PowerShell.
273
274
@@ -277,13 +278,14 @@ The following steps show how to create an autoscale profile using PowerShell.
277
278
278
279
## Add a recurring profile using PowerShell
279
280
280
-
The example below shows how to create default profile and a recurring autoscale profile, recurring on Wednesdays and Fridays between 09:00 and 23:00.
281
+
The following example shows how to create default profile and a recurring autoscale profile, recurring on Wednesdays and Fridays between 09:00 and 23:00.
281
282
The default profile uses the `CpuIn` and `CpuOut` Rules. The recurring profile uses the `BandwidthIn` and `BandwidthOut` rules.
Copy file name to clipboardExpand all lines: articles/azure-monitor/autoscale/autoscale-webhook-email.md
+20-20Lines changed: 20 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Learn how to use autoscale actions to call web URLs or send email n
4
4
author: EdB-MSFT
5
5
ms.author: edbaynash
6
6
ms.topic: conceptual
7
-
ms.date: 06/21/2023
7
+
ms.date: 08/25/2024
8
8
ms.subservice: autoscale
9
9
ms.reviewer: akkumari
10
10
---
@@ -15,7 +15,11 @@ This article shows you how to set up notifications so that you can call specific
15
15
Webhooks allow you to send HTTP requests to a specific URL endpoint (callback URL) when a certain event or trigger occurs. Using webhooks, you can automate and streamline processes by enabling the automatic exchange of information between different systems or applications. Use webhooks to trigger custom code, notifications, or other actions to run when an autoscale event occurs.
16
16
17
17
## Email
18
-
You can send email to any valid email address when an autoscale event occurs. Administrators and co-administrators of the subscription where the rule is running are also notified.
18
+
You can send email to any valid email address when an autoscale event occurs.
19
+
20
+
> [!NOTE]
21
+
> Starting April 3, 2024, you won't be able to add any new Co-Administrators for Azure Autoscale Notifications. Azure Classic administrators will be retired on August 31, 2024, and you would not be able to send Azure Autoscale Notifications using Administrators and Co-Administrators after August 31, 2024. For moe information, see [Prepare for Co-administrators retirement](/azure/role-based-access-control/classic-administrators?WT.mc_id=Portal-Microsoft_Azure_Monitoring&tabs=azure-portal#prepare-for-co-administrators-retirement)
22
+
19
23
20
24
## Configure Notifications
21
25
@@ -27,7 +31,7 @@ Use the Azure portal, CLI, PowerShell, or Resource Manager templates to configur
27
31
28
32
Select the **Notify** tab on the autoscale settings page to configure notifications.
29
33
30
-
Select the check boxes to send an email to the subscription administrator or co-administrators. You can also enter a list of email addresses to send notifications to.
34
+
Enter a list of email addresses to send notifications to.
31
35
32
36
Enter a webhook URI to send a notification to a web service. You can also add custom headers to the webhook request. For example, you can add an authentication token in the header, query parameters, or add a custom header to identify the source of the request.
33
37
@@ -42,19 +46,16 @@ Use the `az monitor autoscale update` or the `az monitor autoscale create` comma
42
46
43
47
The following parameters are used to configure notifications:
44
48
45
-
+`--add-action` - The action to take when the autoscale rule is triggered. The value must be `email` or `webhook`.
46
-
+`--email-administrator {false, true}` - Send email to the subscription administrator.
47
-
+`--email-coadministrators {false, true}` - Send email to the subscription co-administrators.
49
+
+`--add-action` - The action to take when the autoscale rule is triggered. The value must be `email` or `webhook`, and followed by the email address or webhook URI.
48
50
+`--remove-action` - Remove an action previously added by `--add-action`. The value must be `email` or `webhook`. The parameter is only relevant for the `az monitor autoscale update` command.
49
51
50
52
51
-
For example, the following command adds an email notification and a webhook notification to and existing autoscale setting. The command also sends email to the subscription administrator.
53
+
For example, the following command adds an email notification and a webhook notification to and existing autoscale setting.
0 commit comments