The event center centralizes, stores, analyzes, and displays event data generated by Alibaba Cloud services. The event center supports the following events: change events of Enterprise Distributed Application Service (EDAS), alert events of Application Real-Time Monitoring Service (ARMS), 0-1 status events such as deadlocks, out of memory (OOM), and application startup failures, microservice governance events of Microservice Engine (MSE), and Kubernetes cluster events. If your application uses one of the related services, the event center automatically analyzes and displays the corresponding events in a unified manner. This provides an easy way for you to view and analyze the events.

Event model

The following table describes the parameters that define an event in the event center.

Parameter Required Description
source Yes The source of the event.
type Yes The type of the event.
level Yes The level of the event.
time Yes The time when the event occurred.
data Yes The content of the event, which is generally in the JSON format.
PID No The ID of the pod.
IP No The IP address.
ClusterId No The ID of the cluster.
PodName No The name of the pod.

Go to the event center

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. Select Container Service or Serverless Kubernetes Cluster from the Cluster Type drop-down list, and click the name of the desired application.
  3. In the left-side navigation pane, click Event Center.

Overview of the event center module

The Event Center page consists of typical events and the Normal View, Topology View, and Subscription rules tabs.
  • Typical events: displays the number of typical events that are preset by the system. For more information, see Typical events.
  • On the Normal View tab, all events associated with the current application are analyzed and displayed in multiple dimensions. For more information, see Normal view.
  • On the Topology View tab, the events associated with the application and the resource topology of the application are displayed together. For more information, see Topology view.
  • On the Subscription rules tab, subscription rules that you create are displayed in a list. For more information, see Subscription rules.

Typical events

Typical events: displays the number of times that each type of typical event preset by the system occurred within the last 30 minutes. You can adjust the time range in the upper-right corner. Click Subscribe below an event to edit subscription rules of the event. For more information about subscription rules, see Subscription rules.

Normal view

On the Normal View tab, you can specify filter conditions to search for events. The search results are displayed in four sections: Last two weeks event re li tu, Proportion of events from different sources, Trend of the number of events from different sources, and Event Details.

Normal view
  • The Last two weeks event re li tu section displays the heat map for hourly occurrences of events that meet the filter conditions in the last two weeks. A darker color indicates more events in the hour.
  • The Proportion of events from different sources section displays the proportions of events from different sources.
  • The Trend of the number of events from different sources section displays the trends of events from different sources within a specified period.
  • The Event Details section displays details about all current events.

Perform the following operations to view information on the Normal View tab:

  • In the Last two weeks event re li tu section, click each heat block to view event details in the hour.
  • In the Trend of the number of events from different sources section, click each column to view all the events that occurred in the specified period in the Event Details section.
  • In the Event Details section, click View in the Operation column to view the details of the event.
  • In the Event Details section, click Subscription in the Operation column of an event to subscribe to the event. For more information, see Subscription rules.

Topology view

On the Topology View tab, the resource topology of the application is displayed. The resources include the Elastic Compute Service (ECS) instances used by the application, pods on which the application is running, the ApsaraDB RDS and ApsaraDB for Redis middleware used by the application, and the Server Load Balancer (SLB) and NAT Gateway resources mounted to the application. After the resource topology is displayed, the obtained correlated events, ActionTrail events, and CloudMonitor events are associated with topology nodes. If you click a node, the events associated with the node are displayed in the Event Details section in the upper-left corner.
  • Application-side events: the events in the event center.
  • Events related to cloud resources: the events that CloudMonitor records.
  • Audit related operations: the audit records from ActionTrail.

The topology view can help you troubleshoot the associated resources when an application error occurs. For example, in a large enterprise, an employee mistakenly restarts an ApsaraDB RDS instance in the production environment, which leads to an online service failure. The topology view helps you find out the restart operation on the ApsaraDB RDS instance that is accessed by the application.

Topology view

Subscription rules

On the Subscription rules tab, all your existing subscription rules are displayed. You can enable, disable, or modify subscription rules on this tab.
Notice You can modify only the rules that you created in the console. You cannot modify rules that are automatically created by the system.
A subscription rule is used as a basis when you subscribe to events that meet specified criteria and send the events to a specified webhook. You can use one of the following methods to create a subscription rule:
  • Method 1: On the Subscription rules tab, click Create a subscription rule in the upper-right corner.
  • Method 2: On the Normal View tab, click Subscription in the Operation column of an event in the Event Details section.

Create a subscription rule

  1. Click the Subscription rules tab. On this tab, click Create a subscription rule in the upper-right corner.
  2. In the Create a subscription rule panel, set the Rule name and Rule description parameters, and then click Next in the Enter basic information step.
  3. In the Select event mode step, set the event rule parameters and click Next.
    Parameter Description
    Event Source Select an event source from the drop-down list.
    Event Type Select an event type from the drop-down list.
    Event Level Select an event level from the drop-down list.
    Event Keywords Enter event keywords in the field.
    Show advanced filtering options By default, this feature is disabled. After you enable this feature, you can configure filtering options, such as Cluster ID, Interface/service name, Host IP, and POD name.
    Custom filter conditions A custom filter condition is used to specify the condition that must be met by a field in the JSON data of the specified event. The root node in the JSON data of an event is data. A specific field is expressed by using the dot (.) notation starting from the root node. Enter custom filter conditions. You can enter up to six filter conditions.
    Select a valid field Enter a valid field in the format of %data.x.y;. Then, enter an alias for the field. The alias can be used as a placeholder when you enter the POST request body of webhook information. You can set up to six valid fields.
    Notification Template

    In the Notification Template field, enter the content that is sent to you when the specified event occurs. If the notification object is the webhook of a DingTalk chatbot, include the keyword used to create the DingTalk chatbot in the notification template.

  4. From the Select Contact drop-down list, select a contact. Then, click Submitted.
    If no contact is available in the Select Contact drop-down list, click Create Contact on the right side to create a contact. After you create a contact, select the contact from the Select Contact drop-down list.

Subscribe to events on the Normal View tab

  1. On the Normal View tab, click Subscription in the Operation column of an event in the Event Details section.
    If you create a subscription rule by using this method, the source, type, and level filter conditions are automatically selected based on the selected event.
  2. Enter a value in the Value field in the JSON file of the event. This way, you can specify custom filter conditions and valid fields. A filter condition and a valid field are automatically generated each time you click a field. You can manually modify or delete the fields to adjust the subscription rule. After you select an event mode, click Next.
  3. From the Select Contact drop-down list, select a contact. Then, click Submitted.
    If no contact is available in the Select Contact drop-down list, click Create Contact on the right side to create a contact. After you create a contact, select the contact from the Select Contact drop-down list.

Troubleshooting

The issues that occur during the running of applications in Container Service for Kubernetes (ACK) clusters or serverless Kubernetes clusters deployed in EDAS are typically pod issues. For more information about the solutions, see Common pod errors.