Advanced search uses SQL statements to query resources within your current account and across members of your resource directory. This feature provides a flexible, practical, and free way to retrieve resources globally. You can use query templates to quickly find resources. Advanced search supports both simple lookups for specific resource types and complex queries.
Features
-
Flexible search conditions
Advanced search frees you from the fixed rules of traditional search. You can customize search conditions to find the exact resources you need. For example, you can set multiple filter conditions to quickly narrow your search and find matching resources. Advanced search supports basic queries and handles complex scenarios. It quickly provides accurate results when you need to find associated instances, run multi-condition queries, or meet other specific needs. This helps you perform in-depth data analytics.
-
Customizable resource scope
You can use advanced search to query resources across different scopes. You can search for resources within your current account or across multiple members in your resource directory.
-
Query templates
Advanced search provides sample query templates to simplify the query process. These templates contain common query statements that help you quickly locate the resources you need. You can also save your queries as custom templates. This lets you reuse them later without rewriting them. This saves time and ensures query accuracy and consistency. Advanced search meets the needs of both beginners and experienced users and helps you find resources quickly and accurately. For more information, see Search for resources using sample query templates, Search for resources using custom query templates, and Query templates.
-
Chart visualization
The visualization feature in advanced search renders query results as charts. When you need to analyze resource data, such as distribution or proportions, you can use this feature to view search results visually. For example, you can use pie charts or column charts to see the proportion of different resource types. This helps you optimize and adjust resources as needed. For more information, see Step 3: View query results.
Query language
When you use advanced search, you can enter SQL statements to query, filter, and sort your data. The operators and functions in advanced search are based on PostgreSQL. For more information about the basic SQL syntax supported by advanced search, see Basic SQL syntax.
Query table
The `resources` table is the core data table in advanced search. It stores information about resource properties. All advanced search queries are performed by querying, filtering, and sorting the fields in the `resources` table. For example, you can specify the `resource_name` field in your query condition to find a resource by name. Alternatively, you can specify the `resource_type` field to find a specific type of resource. In addition to the core fields, the `properties` field in the `resources` table stores other resource information, such as resource status and billing type. The content of the `properties` field varies depending on the resource type.
The `properties` field stores only resource configuration attributes. It does not include runtime monitoring metrics such as TPS, throughput, or connection count. To view performance monitoring data for a service, go to the Cloud Monitor console and check the corresponding metrics.
The following table describes the structure of the `resources` table.
|
Field |
Type |
Description |
|
resource_id |
varchar |
Resource ID |
|
resource_name |
varchar |
Resource name |
|
region_id |
varchar |
Region ID |
|
zone_id |
varchar |
Zone ID |
|
resource_type |
varchar |
Resource type |
|
account_id |
varchar |
Account ID |
|
create_time |
varchar |
Creation time |
|
resource_group_id |
varchar |
Resource group ID |
|
tags |
jsonb |
Tag collection |
|
ip_addresses |
jsonb |
IP address collection |
|
vpc_id |
varchar |
VPC ID |
|
v_switch_id |
varchar |
vSwitch ID |
|
properties |
jsonb |
Resource properties |
Limits
-
Query frequency limit
Each user can make a maximum of three queries every 5 seconds. If you exceed this limit, your requests are throttled. This quota is determined by many factors and may change.
-
Query time limit
A single query is limited to 10 seconds. If the query does not return a result within this time, the system automatically terminates the query and reports an error.
To prevent a timeout, you can reduce query complexity in the following ways:
-
Add conditions. For example, when you query a large volume of data, use `ORDER BY` to sort by
resource_typeandresource_id. -
Limit the returned data. For example, use `LIMIT` to restrict the maximum number of entries in the result.
-
Avoid directly returning the
propertiesattribute unless it is necessary.
-
-
Query function limit
For more information, see Supported functions.