Querying a Key Event Notification
Function
This API is used to query a key event notification.
API Calling
For details, see Calling APIs.
URI
GET /v3/{project_id}/notifications/{notification_type}
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details, see Obtaining an Account ID and Project ID. |
notification_type |
Yes |
String |
Notification type. - smn: Simple Message Notification (SMN). - fun: FunctionGraph. Enumerated values: |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
notification_name |
No |
String |
Notification name. If this parameter is not specified, all key event notifications configured in the current tenant account are returned. |
Request Parameters
None
Response Parameters
Status code: 200
Parameter |
Type |
Description |
---|---|---|
notifications |
Array of NotificationsResponseBody objects |
Notification list. |
Parameter |
Type |
Description |
---|---|---|
notification_name |
String |
Notification name. |
operation_type |
String |
Operation type. Possible options include complete and customized. If you choose complete, notifications will be sent when any supported operation occurs on any of the connected cloud services. If you choose customized, notifications will be sent when operations defined in operations occur. Enumerated values: |
operations |
Array of Operations objects |
Operation list. |
notify_user_list |
Array of NotificationUsers objects |
List of users whose operations will trigger notifications. Currently, up to 50 users in 10 user groups can be configured. |
status |
String |
Notification status. Possible options include enabled and disabled. Enumerated values: |
topic_id |
String |
Topic URN or function URN. To obtain the topic_urn, call the SMN API for querying topics. Example URN: urn:smn:regionId:f96188c7ccaf4ffba0c9aa149ab2bd57:test_topic_v2 To obtain the function URN, call the FunctionGraph API for querying functions. Example URN: urn:fss:xxxxxxxxx:7aad83af3e8d42e99ac194e8419e2c9b:function:default:test |
notification_id |
String |
Unique notification ID. |
notification_type |
String |
Notification type identified based on topic_id. Possible options include SMN (smn) and FunctionGraph (fun). Enumerated values: |
project_id |
String |
Project ID. |
create_time |
Long |
Timestamp when a notification was created. |
filter |
Filter object |
Advanced filter of key event notifications. |
Parameter |
Type |
Description |
---|---|---|
service_type |
String |
Cloud service. The value must be the acronym of a cloud service that has been connected with CTS. It is a word composed of uppercase letters. For cloud services that can be connected with CTS, see section "Supported Services and Operations" in Cloud Trace Service User Guide. You can click the document link of each cloud service to view its acronym. |
resource_type |
String |
Resource type. |
trace_names |
Array of strings |
Trace name. |
Parameter |
Type |
Description |
---|---|---|
user_group |
String |
IAM user group. |
user_list |
Array of strings |
IAM user. |
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Format: CTS.XXX. |
error_msg |
String |
Error message. |
Status code: 401
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Format: CTS.XXX. |
error_msg |
String |
Error message. |
Status code: 403
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Format: CTS.XXX. |
error_msg |
String |
Error message. |
Status code: 404
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Format: CTS.XXX. |
error_msg |
String |
Error message. |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Format: CTS.XXX. |
error_msg |
String |
Error message. |
Status code: 503
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. Format: CTS.XXX. |
error_msg |
String |
Error message. |
Example Request
None
Example Response
Status code: 200
The query is successful.
{ "notifications" : [ { "create_time" : 1633933167385, "notify_user_list" : [ { "user_group" : "admin", "user_list" : [ "test1", "test2" ] }, { "user_group" : "CTS view", "user_list" : [ "test3", "test4" ] } ], "notification_id" : "0b98e1c2-2fd6-4e33-a355-f9e12eaab88a", "notification_name" : "test2", "notification_type" : "smn", "operation_type" : "customized", "operations" : [ { "resource_type" : "tracker", "service_type" : "CTS", "trace_names" : [ "createTracker" ] }, { "resource_type" : "notification", "service_type" : "CTS", "trace_names" : [ "deleteNotification", "updateNotification" ] }, { "resource_type" : "pe", "service_type" : "AOM", "trace_names" : [ "createPolicyGroup", "updatePolicyGroup", "deletePolicyGroup" ] } ], "project_id" : "24edf66e79d04187acb99a463e610764", "status" : "enabled", "topic_id" : "urn:smn:{regionid}:24edf66e79d04187acb99a463e610764:test" }, { "create_time" : 1633924057706, "notify_user_list" : [ { "user_group" : "admin", "user_list" : [ "test1", "test2" ] }, { "user_group" : "CTS view", "user_list" : [ "test3", "test4" ] } ], "notification_id" : "6d4a09bb-aa8e-40db-9e87-0d5e203823a8", "notification_name" : "test1", "notification_type" : "smn", "operation_type" : "complete", "operations" : [ ], "project_id" : "24edf66e79d04187acb99a463e610764", "status" : "disabled" } ] }
Status Codes
Status Code |
Description |
---|---|
200 |
The query is successful. |
400 |
The server failed to process the request. |
401 |
The request is rejected due to authentication failure. |
403 |
The server understood the request but refused to authorize it. |
404 |
The server failed to find the requested resource or some key event notifications failed to be deleted. |
500 |
The request failed to be executed or some trackers failed to be deleted. |
503 |
The requested service is invalid. The client should not repeat the request without modifications. |
Error Code
For details, 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