- Print
- PDF
UpdateRuleGroup
- Print
- PDF
The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.
Available in Classic and VPC
Update an event rule.
Request
This section describes the request format. The method and URI are as follows:
Method | URI |
---|---|
POST | /cw_fea/real/cw/api/rule/group/ruleGrp/update |
Request headers
For information about the headers common to all Cloud Insight APIs, see Cloud Insight request headers.
Request body
For more information on the request body fields, see CreateOrUpdateRuleGroupDto.
Request example
The request example is as follows:
curl --location --request POST 'https://cw.apigw.ntruss.com/cw_fea/real/cw/api/rule/group/ruleGrp/update' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'Content-Type: application/json' \
--data '{
"id": "**********",
"groupName": "server-test",
"monitorGroupKey": [
"**********"
],
"metricsGroupKey": [
"**********"
],
"groupDesc": "Edit server event rule.",
"prodKey": "**********",
"suspendRuleItems": [
{
"resourceId": "**********",
"metricGroupItemId": "**********"
}
],
"recipientNotifications": [
{
"groupName": "test-nr",
"groupNum": ****,
"notifyTypes": [
"SMS",
"EMAIL"
]
}
]
}
'
Response
This section describes the response format.
Response status codes
For response status codes common to NAVER Cloud Platform, see Cloud Insight API response status codes.
Response example
If the response is successful, the event rule is updated along with the message 200 OK
.