CloudWatch / Client / put_alarm_mute_rule
put_alarm_mute_rule¶
- CloudWatch.Client.put_alarm_mute_rule(**kwargs)¶
Creates or updates an alarm mute rule.
Alarm mute rules automatically mute alarm actions during predefined time windows. When a mute rule is active, targeted alarms continue to evaluate metrics and transition between states, but their configured actions (such as Amazon SNS notifications or Auto Scaling actions) are muted.
You can create mute rules with recurring schedules using
cronexpressions or one-time mute windows usingatexpressions. Each mute rule can target up to 100 specific alarms by name.If you specify a rule name that already exists, this operation updates the existing rule with the new configuration.
Permissions
To create or update a mute rule, you must have the
cloudwatch:PutAlarmMuteRulepermission on two types of resources: the alarm mute rule resource itself, and each alarm that the rule targets.For example, If you want to allow a user to create mute rules that target only specific alarms named “WebServerCPUAlarm” and “DatabaseConnectionAlarm”, you would create an IAM policy with one statement granting
cloudwatch:PutAlarmMuteRuleon the alarm mute rule resource (arn:aws:cloudwatch:[REGION]:123456789012:alarm-mute-rule:*), and another statement grantingcloudwatch:PutAlarmMuteRuleon the targeted alarm resources (arn:aws:cloudwatch:[REGION]:123456789012:alarm:WebServerCPUAlarmandarn:aws:cloudwatch:[REGION]:123456789012:alarm:DatabaseConnectionAlarm).You can also use IAM policy conditions to allow targeting alarms based on resource tags. For example, you can restrict users to create/update mute rules to only target alarms that have a specific tag key-value pair, such as
Team=TeamA.See also: AWS API Documentation
Request Syntax
response = client.put_alarm_mute_rule( Name='string', Description='string', Rule={ 'Schedule': { 'Expression': 'string', 'Duration': 'string', 'Timezone': 'string' } }, MuteTargets={ 'AlarmNames': [ 'string', ] }, Tags=[ { 'Key': 'string', 'Value': 'string' }, ], StartDate=datetime(2015, 1, 1), ExpireDate=datetime(2015, 1, 1) )
- Parameters:
Name (string) –
[REQUIRED]
The name of the alarm mute rule. This name must be unique within your Amazon Web Services account and region.
Description (string) – A description of the alarm mute rule that helps you identify its purpose.
Rule (dict) –
[REQUIRED]
The configuration that defines when and how long alarms should be muted.
Schedule (dict) – [REQUIRED]
The schedule configuration that defines when the mute rule activates and how long it remains active.
Expression (string) – [REQUIRED]
The schedule expression that defines when the mute rule activates. The expression must be between 1 and 256 characters in length.
You can use one of two expression formats:
Cron expressions - For recurring mute windows. Format:
cron(Minutes Hours Day-of-month Month Day-of-week)Examples:cron(0 2 * * *)- Activates daily at 2:00 AMcron(0 2 * * SUN)- Activates every Sunday at 2:00 AM for weekly system maintenancecron(0 1 1 * *)- Activates on the first day of each month at 1:00 AM for monthly database maintenancecron(0 18 * * FRI)- Activates every Friday at 6:00 PMcron(0 23 * * *)- Activates every day at 11:00 PM during nightly backup operations
The characters
*,-, and,are supported in all fields. English names can be used for the month (JAN-DEC) and day of week (SUN-SAT) fields.At expressions - For one-time mute windows. Format:
at(yyyy-MM-ddThh:mm)Examples:at(2024-05-10T14:00)- Activates once on May 10, 2024 at 2:00 PM during an active incident response sessionat(2024-12-23T00:00)- Activates once on December 23, 2024 at midnight during annual company shutdown
Duration (string) – [REQUIRED]
The length of time that alarms remain muted when the schedule activates. The duration must be between 1 and 50 characters in length.
Specify the duration using ISO 8601 duration format with a minimum of 1 minute (
PT1M) and maximum of 15 days (P15D).Examples:
PT4H- 4 hours for weekly system maintenanceP2DT12H- 2 days and 12 hours for weekend muting from Friday 6:00 PM to Monday 6:00 AMPT6H- 6 hours for monthly database maintenancePT2H- 2 hours for nightly backup operationsP7D- 7 days for annual company shutdown
The duration begins when the schedule expression time is reached. For recurring schedules, the duration applies to each occurrence.
Timezone (string) –
The time zone to use when evaluating the schedule expression. The time zone must be between 1 and 50 characters in length.
Specify the time zone using standard timezone identifiers (for example,
America/New_York,Europe/London, orAsia/Tokyo).If you don’t specify a time zone, UTC is used by default. The time zone affects how cron and at expressions are interpreted, as well as start and expire dates you specify
Examples:
America/New_York- Eastern Time (US)America/Los_Angeles- Pacific Time (US)Europe/London- British TimeAsia/Tokyo- Japan Standard TimeUTC- Coordinated Universal Time
MuteTargets (dict) –
Specifies which alarms this rule applies to.
AlarmNames (list) – [REQUIRED]
The list of alarm names that this mute rule targets. You can specify up to 100 alarm names.
Each alarm name must be between 1 and 255 characters in length. The alarm names must match existing alarms in your Amazon Web Services account and region.
(string) –
Tags (list) –
A list of key-value pairs to associate with the alarm mute rule. You can use tags to categorize and manage your mute rules.
(dict) –
A key-value pair associated with a CloudWatch resource.
Key (string) – [REQUIRED]
A string that you can use to assign a value. The combination of tag keys and values can help you organize and categorize your resources.
Value (string) – [REQUIRED]
The value for the specified tag key.
StartDate (datetime) – The date and time after which the mute rule takes effect. If not specified, the mute rule takes effect immediately upon creation and the mutes are applied as per the schedule expression. This date and time is interpreted according to the schedule timezone, or UTC if no timezone is specified.
ExpireDate (datetime) – The date and time when the mute rule expires and is no longer evaluated. After this time, the rule status becomes EXPIRED and will no longer mute the targeted alarms. This date and time is interpreted according to the schedule timezone, or UTC if no timezone is specified.
- Returns:
None
Exceptions