All Products
Search
Document Center

View application details

Last Updated: Sep 23, 2021

Basic Instance Information

  1. Instance ID: uniquely identifies the application.

  2. Instance Creation Time: the time when the application was created, which is in the YYYY-mm-dd HH:MM:SS format.

  3. Billing Method: the billing method of the application, which is subscription or pay-as-you-go.

  4. Region: the region where the application is deployed.

  5. Instance Type: the type of the application. Valid values: Advanced and Standard.

  6. Instance Specifications: the specifications of the application. Example values: Shared General-purpose, Shared Computing, Exclusive General-purpose, and Exclusive Computing.

  7. Storage Resource: the total document size of all tables in the application. This size includes only the size of strings in field values, and does not include the size of field names.

  8. Computing Resource: Logical computing units (LCUs) are used to measure the computing consumption of the search service. An LCU indicates the computing power of 10 millicores in a search cluster. Note that millicore is the unit of CPU resources. One millicore is one thousandth of one core.

  9. Instance Description: the description of the application, which can be customized.

Online or Offline Version

When you configure an application for the first time, the application has only an online version. If you perform operations that trigger reindexing, such as data clearing or offline changes, OpenSearch automatically creates an offline version for the application to ensure the stability of the online version. All the operations are performed on the offline version. When reindexing is complete for the offline version, you can perform a simple test on the offline version. After the test is passed, you can publish the offline version. This way, no matter what operations you perform on the application, your service will not be affected.

Status

The status of the application. If the status is Normal, the online version of the application is in service.

If the application is not in service, it is in one of the following states:

(1) Pending: the status of the application before you configure it

(2) Initializing Application

(3) Initializing Data

(4) Invalid: The application becomes invalid if the full storage size exceeds the quota, or data source tables or fields do not exist. Invalid applications can only be deleted and then reconfigured.

(5) Expired: The service is suspended after the subscription period of a subscription application expires. The application is retained for seven days in the OpenSearch console. During the seven-day period, you can only renew the application. Other features are not supported.

(6) Frozen: The application is frozen due to overdue payments.

Basic Information

The basic information about the current application version includes the billing method, specifications, storage specifications, computing specifications, application ID, region, and description of the current application version.

1

Note: For more information about the billing rules of applications, see the "Billing methods" and "Pricing" sections of the Overview topic.

API Endpoint

For more information, see Endpoint. The API domain name varies by region. When you use the API or SDKs to access OpenSearch, you must use an API endpoint that corresponds to the API domain name for the region. API endpoints for each region are classified into the internal endpoint and the Internet endpoint. The internal endpoint is used for the access from Elastic Compute Service (ECS) instances that are in the same region or virtual private cloud (VPC) as OpenSearch. The Internet endpoint is used for the access from the Internet. Select an API endpoint based on the actual deployment situation. Ping the endpoint before use to ensure that it is accessible.

Data Source

The data source for OpenSearch. Data can be from MaxCompute, ApsaraDB RDS V5.2 to V8.0, or PolarDB, or be imported by using the API or SDKs.

Application Schema

  1. Tables The schemas of tables in the application.

  2. Index Fields Index fields that are configured in the application. For example, you can query the index field whose index name is id:

    query=id: 'Cloud search'. For more information about index analysis methods, see Application schema and index schema.

  3. Attribute Fields Attribute fields that are configured in the application.

    Instructions: Attribute fields are used in the FILTER, AGGREGATE, SORT, and DISTINCT clauses of queries to implement filtering, statistics, and sorting features. Example: filter=id>100000

Default Display Fields

In each search request, you can specify default display fields to limit the exhibition of specific fields in the application schema.

CloudMonitor

You can click CloudMonitor to view common metrics of the current application, such as the storage capacity (bytes), storage capacity usage (%), total number of documents, queries per second (QPS), throttled queries per second, query duration (ms), computing resources (LCU), consumed computing resource per query (LCU), and daily peak computing resource (LCU). For more information about the monitoring metrics and the process of configuring alerts, see Use CloudMonitor to monitor resource usage and configure alert rules.

Reindex

OpenSearch creates an image for uploaded data and data that is synchronized from data sources. If you modify the schema of an application or upload full data to the application, you must perform reindexing. Reindexing can be manually performed or performed as scheduled. If you modify the schema of an application or upload full data to the application, you can manually trigger reindexing. If full data is synchronized from a MaxCompute data source to an application every day, you can configure scheduled reindexing for the application. You do not need to configure scheduled reindexing for an application with an ApsaraDB RDS data source. This is because data synchronization is enabled for ApsaraDB RDS data sources by default. Reindexing is automatically performed when data is synchronized from an ApsaraDB RDS data source.

Change to Subscription

You can change the billing method of an application from pay-as-you-go to subscription. For more information about billing methods, pricing, and procedures, see Overview.

Error Logs

You can click Error Logs to view the error messages for reindexing failures and failures to push data by using the API or SDKs. Note that data pushing by using the API or SDKs is asynchronous. The pushing may fail even if no error message is returned. If data processing fails, the OpenSearch console displays an error message. For more information about error codes, see Error codes.

Unpublished Applications

Online version: the OpenSearch application version that is connected to the search service.

Offline version: the offline version that is created when you modify the application configurations, such as the schema of the application. The initial status of the offline version is the same as the current status of the online version. In addition, the online version supports offline changes. You can change the data source of the application, and modify the application schema and the index schema. The online version also supports query configuration, sort configuration, and extended features. However, you cannot create another version to modify the current offline version. You can only configure the data source, application schema, index schema, sorting, and extended features for the current offline application. The online version and offline version have an inheritance relationship but are independent of each other.

Unpublished version: After you publish the offline version as the new online version, the original online version is unpublished as the new offline version. In this case, you cannot publish the offline version unless you initiate another offline change. This is because the current offline version has been published before.

Delete Application

To prevent accidental deletion, you can delete an application only when you correctly enter Application Name + Online Application.

To prevent an application from being deleted due to misoperations, OpenSearch does not allow you to directly delete the entire application when an online version exists. If you are sure that the application can be unpublished, perform the following steps:

1.Delete the offline version: On the Applications page, find the application whose offline version you want to delete and click Details in the Actions column. On the Application Details page, click the Offline Application tab. On the Offline Application tab, click Delete Application.

2

Note: This step can be ignored if no offline version exists.

2.Delete the online version: On the Applications page, find the application whose online version you want to delete and click Details in the Actions column. On the Online Application tab of the Application Details page, click Delete Application.

3

3.If an application is in the Pending state, you can directly delete the application.

4

Note: You can delete only pay-as-you-go applications, but not subscription applications.

Offline Change

If you want to change the data source of an application or modify the schema of the application, including creating and deleting fields, modifying and creating indexes, and creating and deleting attributes, you can click Offline Change on the details page of the application. For more information, see Perform offline changes.