Serverless Application Engine events-阿里云帮助中心

This topic describes the types of Serverless App Engine events that are ingested by Cloud Config and published to EventBridge as an event source.

Event types

Serverless App Engine (SAE) can publish the following event types to EventBridge.

Event type	Value of the type parameter
Application runtime health check failure	sae:Runtime:SaeK8sUnhealthyEvent
Task execution failure	sae:Runtime:SaeJobFailEvent
Task execution success	sae:Runtime:SaeJobSuccessEvent
Instance restart during application runtime	sae:Runtime:SaeInstanceRestartEvent
OOM error during application runtime	sae:Runtime:SaeK8sOomKilledEvent
Elastic scaling during application runtime	sae:Runtime:SaeK8sSuccessfulRescaleEvent
Health check failure during application change	sae:ChangeOrder:SaeK8sUnhealthyEvent
The product configuration does not match the CLB console configuration	sae:System:SaeAppSlbConfigResetWarning
Gateway routing configuration mismatch with SLB console	sae:System:SaeSlbConfigResetWarning
Release order execution failure	sae:ChangeOrder:SaeChangeOrderFailEvent
Delayed batch in manual phased release	sae:ChangeOrder:SaeWaitBatchConfirmEvent

For more information about the parameters defined in the CloudEvents specification, see Event overview.

Application runtime health check failure

When an application runtime health check fails, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeK8sUnhealthyEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "RUNTIME",
        "type": "SAE_K8S_UNHEALTHY_EVENT",
        "level": "WARNING",
        "namespaceId": "cn-beijing:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "instanceId": "****-fe4f9fa1-0eef-4957-91a0-081b625efe9b-****",
        "message": "Your SAE application: ****-MSGGATE(cn-beijing:****) had a health check failure (Readiness) at 2022-04-15 13:23:29!",
        "detail": "Readiness probe failed: check http://127.0.XX.XX:10010/im-msg-gate/actuator/health failed\n"
    }
}

The following table describes the parameters in the data field.

Parameter	Type	Sample value	Description
source	String	RUNTIME	The source that triggers the SAE event.
type	String	SAE_K8S_UNHEALTHY_EVENT	The type of the SAE event.
level	String	WARNING	The level of the SAE event. Valid values: WARNING: Warning. INFO: Notification.
namespaceId	String	cn-beijing:****	The ID of the SAE namespace.
resourceId	String	fe4f9fa1-0eef-4957-91a0-****	The ID of the SAE application.
instanceId	String	**-fe4f9fa1-0eef-4957-91a0-081b625efe9b-**	The ID of the SAE application instance.
message	String	Your SAE application: **-MSGGATE(cn-beijing:**) had a health check failure (Readiness) at 2022-04-15 13:23:29!	The content of the SAE event message.
detail	String	Readiness probe failed: check http://127.0.XX.XX:10010/im-msg-gate/actuator/health failed\n	Other details about the SAE event.

Task execution failure

When a task execution fails, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeJobFailEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "RUNTIME",
        "type": "SAE_JOB_FAIL_EVENT",
        "level": "WARNING",
        "namespaceId": "cn-beijing:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "message": "Your SAE task: ****-MSGGATE(cn-beijing:****) failed to execute at 2022-08-10 10:45:50. Creation time: 2022-08-10 10:40:49. Running/Succeeded/Failed instances: 0/0/1. Please check the task.",
        "detail": "job was active longer than specified deadline"
    }
}

For more information about the parameters in the data field, see Parameter details.

Task execution success

When a task execution succeeds, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeJobSuccessEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "RUNTIME",
        "type": "SAE_JOB_SUCCESS_EVENT",
        "level": "INFO",
        "namespaceId": "cn-beijing:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "message": "Your SAE task: ****-MSGGATE(cn-beijing:****) executed successfully at 2022-08-09 17:43:40. Creation time: 2022-08-09 17:43:14. Running/Succeeded/Failed instances: 0/1/0."
    }
}

For more information about the parameters in the data field, see Parameter details.

Instance restart during application runtime

When an application runtime instance restarts, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeInstanceRestartEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": { 
      "source": "RUNTIME",
      "type": "SAE_INSTANCE_RESTART_EVENT",
      "level": "WARNING",
      "namespaceId": "cn-hangzhou:****",
      "resourceId": "fe4f9fa1-0eef-4957-91a0-****", 
      "instanceId": "****-fe4f9fa1-0eef-4957-91a0-081b625efe9b-****",
      "message": "Your SAE instance: demo-*****, which belongs to application: demo (cn-hangzhou:***), restarted at 2022-08-03 21:32:18. Possible reason: Liveness probe failed: check http://127.0.0.1:80/actuator/health failed. Please check the instance.",
      "detail": "Liveness probe failed: check http://127.0.XX.XX:80/actuator/health failed"
    }
}

For more information about the parameters in the data field, see Parameter details.

OOM error during application runtime

When an out-of-memory (OOM) error occurs during application runtime, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeK8sOomKilledEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "RUNTIME",
        "type": "SAE_K8S_OOM_KILLED_EVENT",
        "level": "WARNING",
        "namespaceId": "cn-hangzhou:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****", 
        "instanceId": "****-fe4f9fa1-0eef-4957-91a0-081b625efe9b-****",
        "message": "Your SAE instance: *****, which belongs to application: **** (cn-hangzhou:***), had an OOM error at 2022-08-12 11:40:41. This may cause the instance to restart. Please check the instance.",
        "detail": ""
    }
}

For more information about the parameters in the data field, see Parameter details.

Elastic scaling during application runtime

When elastic scaling occurs during application runtime, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeK8sSuccessfulRescaleEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "RUNTIME",
        "type": "SAE_K8S_SUCCESSFUL_RESCALE_EVENT",
        "level": "Info",
        "namespaceId": "cn-hangzhou:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****", 
        "instanceId": "****-fe4f9fa1-0eef-4957-91a0-081b625efe9b-****",
        "message": "Your application: **** (cn-hangzhou:***) triggered a scale-in at 2022-08-12 11:50:16. Details: New size: 4; reason: All metrics below target.",
        "detail": "New size: 4; reason: All metrics below target"
    }
}

For more information about the parameters in the data field, see Parameter details.

Health check failure during application change

When a health check fails during an application change, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:Runtime:SaeK8sUnhealthyEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42Z",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "RUNTIME",
        "type": "SAE_K8S_UNHEALTHY_EVENT",
        "level": "WARNING",
        "namespaceId": "cn-beijing:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "instanceId": "****-fe4f9fa1-0eef-4957-91a0-081b625efe9b-****",
        "message": "Your SAE application: ****-MSGGATE(cn-beijing:****) had a health check failure (Readiness) at 2022-04-15 13:23:29!",
        "detail": "Readiness probe failed: check http://127.0.XX.XX:10010/im-msg-gate/actuator/health failed\n"
    }
}

For more information about the parameters in the data field, see Parameter details.

Configuration mismatch between the backend service and the CLB console

When the SAE configuration is inconsistent with the Server Load Balancer (SLB) console configuration, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:System:SaeAppSlbConfigResetWarning",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "SYSTEM",
        "type": "SAE_APP_SLB_CONFIG_RESET_WARNING",
        "level": "WARNING",
        "namespaceId": "cn-hangzhou:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "message": "Because you modified %s for the instance [ip: %s] in the SLB console, the configuration conflicts with the information configured for SAE application %s. The configuration was forcibly overwritten by the configuration saved in the SAE system."
    }
}

For more information about the parameters in the data field, see Parameter details.

Gateway routing configuration mismatch with SLB console

When the SAE gateway routing configuration is inconsistent with the SLB console configuration, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:System:SaeSlbConfigResetWarning",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42.179PRC",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "SYSTEM",
        "type": "SAE_SLB_CONFIG_RESET_WARNING",
        "level": "WARNING",
        "namespaceId": "cn-hangzhou:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "message": "Because you modified %s for the instance [ip: %s] in the SLB console, the configuration conflicts with the gateway routing configuration %s saved in the SAE system. The configuration was forcibly overwritten by the configuration saved in the SAE system."
    }
}

For more information about the parameters in the data field, see Parameter details.

Release order execution failure

When an SAE release order fails to execute, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:ChangeOrder:SaeChangeOrderFailEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42Z",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "CHANGE_ORDER",
        "type": "SAE_CHANGE_ORDER_FAIL_EVENT",
        "level": "WARNING",
        "namespaceId": "cn-hangzhou:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "message": "Your SAE release order: failed to execute at 2022-04-15 13:23:29!",
        "detail": "Your change order failed to execute!\n"
    }
}

The following table describes the parameters in the data field.

Parameter	Type	Example	Description
source	String	RUNTIME	The source that triggers the SAE event.
type	String	SAE_CHANGE_ORDER_FAIL_EVENT	The type of the SAE event.
level	String	WARNING	The level of the SAE event. Valid values: WARNING: Warning. INFO: Notification
namespaceId	String	cn-hangzhou:****	The ID of the SAE namespace.
resourceId	String	fe4f9fa1-0eef-4957-91a0-****	The ID of the SAE application.
instanceId	String	**-fe4f9fa1-0eef-4957-91a0-081b625efe9b-**	The ID of the SAE application instance.
message	String	Your SAE release order: failed to execute at 2022-04-15 13:23:29!	The content of the SAE event message.
detail	String	Your change order failed to execute!\n	Other details about the SAE event.

Delayed batch in manual phased release

When the next batch is not executed for a prolonged period during a manual phased release of an SAE application, EventBridge receives a sample event as follows.

{
    "id": "45ef4dewdwe1-7c35-447a-bd93-fab****",
    "source": "acs.sae",
    "specversion": "1.0",
    "subject": "acs.sae:cn-hangzhou:123456789098****:215672",
    "time": "2020-11-19T21:04:41+08:00",
    "type": "sae:ChangeOrder:SaeWaitBatchConfirmEvent",
    "aliyunaccountid": "123456789098****",
    "aliyunpublishtime": "2020-11-19T21:04:42Z",
    "aliyuneventbusname": "default",
    "aliyunregionid": "cn-hangzhou",
    "aliyunpublishaddr": "172.25.XX.XX",
    "data": {
        "source": "CHANGE_ORDER",
        "type": "SAE_WAIT_BATCH_CONFIRM_EVENT",
        "level": "INFO",
        "namespaceId": "cn-hangzhou:****",
        "resourceId": "fe4f9fa1-0eef-4957-91a0-****",
        "message": "Your SAE application: ****-MSGGATE(cn-hangzhou:****) has not executed the next batch for a long time!",
        "detail": "Your change order has not been operated for a long time\n"
    }

For more information about the parameters in the data field, see Parameter details.