Adding a Silence Rule
Function
This API is used to add a silence rule.
Calling Method
For details, see Calling APIs.
URI
POST /v2/{project_id}/alert/mute-rules
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID obtained from IAM. Generally, a project ID contains 32 characters. Minimum: 32 Maximum: 32 |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
User token obtained from IAM. Minimum: 1 Maximum: 40960 |
Content-Type |
Yes |
String |
Content type, which is application/json. Enumeration values:
|
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
create_time |
No |
Long |
Creation time. Minimum: 0 Maximum: 9999999999999 |
desc |
No |
String |
Rule description. Minimum: 0 Maximum: 1024 |
match |
Yes |
Array<Array<Match>> |
Match condition of the rule. Up to 10 serial or parallel conditions can be created. Array Length: 1 - 10 |
mute_config |
Yes |
MuteConfig object |
Time when the rule takes effect. |
name |
Yes |
String |
Rule name. Enter a maximum of 100 characters and do not start or end with an underscore (_). Only letters, digits, and underscores are allowed. Minimum: 1 Maximum: 100 |
timezone |
Yes |
String |
Time zone. Minimum: 1 Maximum: 32 |
update_time |
No |
Long |
Modification time. Minimum: 0 Maximum: 9999999999999 |
user_id |
No |
String |
User ID. Minimum: 32 Maximum: 32 |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
key |
Yes |
String |
Key specified in the metadata for matching. Minimum: 1 Maximum: 128 |
operate |
Yes |
String |
Match mode. EXIST: Exist. REGEX: Regular expression. EQUALS: Equal to. Minimum: 1 Maximum: 100 Enumeration values:
|
value |
No |
Array of strings |
Value corresponding to the key. If operate is set to EXIST, this parameter is left empty. Minimum: 1 Maximum: 256 Array Length: 0 - 5 |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
ends_at |
No |
Long |
End time of the silence rule. Minimum: 0 Maximum: 999999999 |
scope |
No |
Array of integers |
When type is set to WEEKLY or MONTHLY, scope cannot be empty. Minimum: 0 Maximum: 31 Array Length: 1 - 100 |
starts_at |
Yes |
Long |
Start time of the silence rule. Minimum: 0 Maximum: 999999999 |
type |
Yes |
String |
Type of the time for the silence rule to take effect. FIXED: Fixed time. DAILY: Certain time every day. WEEKLY: Certain time every week. MONTHLY: Certain time every month. Minimum: 1 Maximum: 100 Enumeration values:
|
Response Parameters
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Response code. Minimum: 13 Maximum: 13 |
error_msg |
String |
Response message. Minimum: 1 Maximum: 100 |
trace_id |
String |
Response ID. Minimum: 12 Maximum: 12 |
Status code: 401
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Minimum: 12 Maximum: 12 |
error_msg |
String |
Error message. Minimum: 0 Maximum: 1024 |
error_type |
String |
Error type. Minimum: 0 Maximum: 128 |
trace_id |
String |
Request ID. Minimum: 32 Maximum: 32 |
Status code: 403
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Minimum: 12 Maximum: 12 |
error_msg |
String |
Error message. Minimum: 0 Maximum: 1024 |
error_type |
String |
Error type. Minimum: 0 Maximum: 128 |
trace_id |
String |
Request ID. Minimum: 32 Maximum: 32 |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Response code. Minimum: 13 Maximum: 13 |
error_msg |
String |
Response message. Minimum: 1 Maximum: 100 |
trace_id |
String |
Response ID. Minimum: 12 Maximum: 12 |
Example Requests
Add a silence rule whose name is "32255" and user ID is "2xxxxxxxxxxxxxxxxxxxxxxxxxcf".
https://{Endpoint}/v2/{project_id}/alert/mute-rules { "create_time" : 1668147671966, "desc" : "", "match" : [ [ { "key" : "event_severity", "operate" : "EQUALS", "value" : [ "Info" ] } ] ], "mute_config" : { "ends_at" : 86399, "scope" : [ ], "starts_at" : 0, "type" : "DAILY" }, "name" : "32255", "timezone" : "xxx", "update_time" : 1668147671966, "user_id" : "2xxxxxxxxxxxxxxxxxxxxxxxxxcf" }
Example Responses
Status code: 400
Bad Request: Invalid request. The client should not repeat the request without modifications.
{ "error_code" : "AOM.08002001", "error_msg" : "bad request", "trace_id" : "" }
Status code: 401
Unauthorized: The authentication information is incorrect or invalid.
{ "error_code" : "SVCSTG.AMS.2000051", "error_msg" : "auth failed.", "error_type" : "AUTH_FAILED" }
Status code: 403
Forbidden: The request is rejected. The server has received the request and understood it, but the server refuses to respond to it. The client should not repeat the request without modifications.
{ "error_code" : "AOM.0403", "error_msg" : "auth failed.", "error_type" : "AUTH_FAILED" }
Status code: 500
Internal Server Error: The server is able to receive the request but unable to understand the request.
{ "error_code" : "AOM.08002500", "error_msg" : "SC_INTERNAL_SERVER_ERROR", "trace_id" : "" }
Status Codes
Status Code |
Description |
---|---|
204 |
OK: Operation successful. |
400 |
Bad Request: Invalid request. The client should not repeat the request without modifications. |
401 |
Unauthorized: The authentication information is incorrect or invalid. |
403 |
Forbidden: The request is rejected. The server has received the request and understood it, but the server refuses to respond to it. The client should not repeat the request without modifications. |
500 |
Internal Server Error: The server is able to receive the request but unable to understand the request. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot