Microservices Engine:Manage applications

Create an application

Create an application before you create jobs. The application groups your jobs and provides the entry point for agent and SDK connectivity.

Before you begin, make sure you have:

• A SchedulerX namespace to host the application

• A unique application ID (this ID also serves as the job group ID and is required for agent initialization)

Step 2: Configure notifications

1. In the Notification configuration step, set the Notification channel and Notify contact parameters.

   • Notification channel: Select one or more channels -- SMS, Mail, webhook, or Telephone.

   • Notify contact: Choose a Contact group (all members receive notifications) or add individual contacts by selecting Contact. For more information about creating contact groups, see the Create a notification contact and a notification contact group section.

2. To add a new contact, click Add contact > Go to create a contact. On the contacts page, click New contact and enter the contact information.

   

   

   

3. Click Complete.

After the application is created, it appears in the application list.

Important

After creation, record the following values from the application list:

• Application ID: Required for agent initialization. Also serves as the unique job group identifier.

• Application key: Required for SDK request authentication. Do not share this key with other users.

curl 'https://oapi.xxxxxxx' \
     -H 'Content-Type: application/json' \
     -d '{
          "msgtype": "text",
          "text": {
              "content": "Details of the alert triggered in SchedulerX"
          },
          "at": {
              "isAtAll": false
          }
     }'

View instances

After an application connects to SchedulerX, verify that workers are online and review their status.

1. On the Application Management page, check the Total number of instances column.

   If the value in the Total number of instances column is 0, you failed to connect the job for the application to SchedulerX.

2. Click View instances in the Operation column to open the Connect to an instance panel.

3. Review the worker list. Each entry shows: To force job scheduling on busy workers, click Edit in the Operation column of the application, then disable the Whether to trigger a busy machine switch in the Machine Instance busy configuration section.

   • IP address and agent count: The number in parentheses after the IP address indicates how many SchedulerX agents run on that worker. In most cases, each worker runs a single agent.

   • Status: Either Health (normal) or Busy (one or more thresholds exceeded). By default, SchedulerX skips busy workers when scheduling jobs. If all workers are busy, no jobs are scheduled.

Grant RAM users access to an application

Grant Resource Access Management (RAM) users access to a specific application. You can grant permissions from either an Alibaba Cloud account or a RAM user with sufficient privileges.

On the Application Management page, click Authorization in the Operation column of the target application.

If the system displays you do not have the required permissions, attach the following custom policy to the RAM user through your Alibaba Cloud account:

{
    "Version": "1",
    "Statement": [
        {
            "Action": "ram:ListUsers",
            "Resource": "*",
            "Effect": "Allow"
        }
    ]
}

Delete an application

Deleting an application stops all associated jobs from being triggered and removes the application from the Application Management page.

1. On the Application Management page, click Delete in the Operation column of the target application.

2. In the Delete application dialog box, confirm the application information, enter the application name, and click OK.