Skip to content

Commit 7547933

Browse files
authored
ttl required
1 parent 141e1c8 commit 7547933

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/defender-for-iot/organizations/references-work-with-defender-for-iot-apis.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2501,13 +2501,15 @@ Define conditions under which alerts won't be sent. For example, define and upda
25012501

25022502
The APIs that you define here appear in the on-premises management console's Alert Exclusions window as a read-only exclusion rule.
25032503

2504+
This API is supported for maintenance purposes only and is not meant to be used instead of [alert exclusion rules](/azure/defender-for-iot/organizations/how-to-work-with-alerts-on-premises-management-console#create-alert-exclusion-rules). Use this API for one-time maintenance operations only.
2505+
25042506
#### Method - POST
25052507

25062508
#### Query parameters
25072509

25082510
- **ticketId**: Defines the maintenance ticket ID in the user's systems.
25092511

2510-
- **ttl**: Defines the TTL (time to live), which is the duration of the maintenance window in minutes. After the period of time that this parameter defines, the system automatically starts sending alerts.
2512+
- **ttl**: Required. Defines the TTL (time to live), which is the duration of the maintenance window in minutes. After the period of time that this parameter defines, the system automatically starts sending alerts.
25112513

25122514
- **engines**: Defines from which security engine to suppress alerts during the maintenance process:
25132515

0 commit comments

Comments
 (0)