Resource query method and device, resource management platform, equipment and program product

Abstract

Embodiments of the present invention provide a resource query method and apparatus, a resource management platform, a device and a program product, the resource query method comprising: receiving a resource query request sent by a front end, the resource query request comprising a resource type of a to-be-queried resource and a user identity identifier; target resource information is queried based on the resource type, target configuration information is queried based on the user identity identifier, the target configuration information is configuration information of a deployed application, and the deployed application is an application using the target resource; the target resource information and the target configuration information are subjected to correlation analysis, a correlation analysis result is obtained, and the correlation analysis result represents the use state of at least one application for the to-be-queried resource; and returning a correlation analysis result to the front end. The resource use condition can be accurately inquired and analyzed, and a user is helped to quickly know and manage the configuration and state of the application program, so that the working efficiency and the user experience are optimized.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of cloud service technology, and in particular to a resource query method, device, resource management platform, equipment and program product. Background Art

[0002] The popularity of cloud computing technology enables enterprises to run their applications and services in a more flexible and scalable manner, thereby improving efficiency and reducing costs.

[0003] However, after migrating their businesses to the cloud, enterprises are faced with problems such as lack of real-time monitoring and analysis capabilities, inefficient resource optimization and scheduling, and lack of intuitive management interfaces. The rapid expansion and diversified use of resources in cloud environments have made it difficult for enterprises to track and optimize resource allocation in real time. In addition, as business grows, demand for resources becomes more dynamic and complex, making management methods that rely solely on manual management and a single perspective inconvenient and unintuitive. Summary of the invention

[0004] In view of this, an embodiment of the present invention provides a resource query method. One or more embodiments of the present invention also relate to a resource management platform, a resource query device, a computing device, a computer-readable storage medium and a computer program product to solve the technical defects existing in the prior art.

[0005] According to a first aspect of an embodiment of the present invention, a resource query method is provided, which is applied to a server and includes:

[0006] Receive a resource query request sent by the front end, wherein the resource query request includes a resource type of a resource to be queried and a user identity;

[0007] Query target resource information based on resource type, and query target configuration information based on user identity, wherein the target configuration information is configuration information of deployed applications, and deployed applications are applications that have used target resources;

[0008] Performing correlation analysis on the target resource information and the target configuration information to obtain a correlation analysis result, wherein the correlation analysis result represents a usage status of at least one application for the resource to be queried;

[0009] Return the association analysis results to the front end.

[0010] According to a second aspect of an embodiment of the present invention, a resource query method is provided, which is applied to a front end and includes:

[0011] In response to the input query instruction, a resource query request is generated, wherein the resource query request includes a resource type of a resource to be queried and a user identity identifier;

[0012] Send a resource query request to the server;

[0013] Receive the association analysis result returned by the server, where the association analysis result represents the usage status of the deployed application for the resource to be queried, and the association analysis result is obtained by the server through association analysis of the target resource information and the target configuration information, the target configuration information is the configuration information of the deployed application, the target resource information is obtained based on the resource type query, and the target configuration information is obtained based on the user identity query.

[0014] According to a third aspect of an embodiment of the present invention, there is provided a resource management platform, including a front end and a server;

[0015] The front end is used to generate a resource query request in response to the input query instruction, wherein the resource query request includes the resource type of the resource to be queried and the user identity identifier; and send the resource query request to the server;

[0016] The server is used to receive the resource query request sent by the front end; query the target resource information based on the resource type, and query the target configuration information based on the user identity, wherein the target configuration information is the configuration information of at least one application deployed by the front end; perform correlation analysis on the target resource information and the target configuration information to obtain the correlation analysis result, wherein the correlation analysis result represents the usage status of at least one application for the resource to be queried; and return the correlation analysis result to the front end;

[0017] The front end is also used to receive the correlation analysis results returned by the server.

[0018] According to a fourth aspect of an embodiment of the present invention, a resource query device is provided, which is applied to a server, and includes:

[0019] Resource management platform, including front-end and server;

[0020] The front end is used to generate a resource query request in response to the input query instruction, wherein the resource query request includes the resource type of the resource to be queried and the user identity identifier; and send the resource query request to the server;

[0021] The server is used to receive the resource query request sent by the front end; query the target resource information based on the resource type, and query the target configuration information based on the user identity, wherein the target configuration information is the configuration information of at least one application deployed by the front end; perform correlation analysis on the target resource information and the target configuration information to obtain the correlation analysis result, wherein the correlation analysis result represents the usage status of at least one application for the resource to be queried; and return the correlation analysis result to the front end;

[0022] The front end is also used to receive the correlation analysis results returned by the server.

[0023] According to a fifth aspect of an embodiment of the present invention, a resource query device is provided, which is applied to a front end and includes:

[0024] A generating module is configured to generate a resource query request in response to an input query instruction, wherein the resource query request includes a resource type of a resource to be queried and a user identity;

[0025] A sending module, configured to send a resource query request to a server;

[0026] The second receiving module is configured to receive the association analysis result returned by the server, wherein the association analysis result represents the usage status of the deployed application for the resource to be queried, and the association analysis result is obtained by the server performing an association analysis on the target resource information and the target configuration information, the target configuration information is the configuration information of the deployed application, the target resource information is obtained based on the resource type query, and the target configuration information is obtained based on the user identity query.

[0027] According to a sixth aspect of an embodiment of the present invention, there is provided a computing device, including:

[0028] Memory and processor;

[0029] The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer programs / instructions are executed by the processor, the steps of the above-mentioned resource query method are implemented.

[0030] According to a seventh aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which stores a computer program / instruction, and the computer program / instruction implements the steps of the above-mentioned resource query method when executed by a processor.

[0031] According to an eighth aspect of an embodiment of the present invention, there is provided a computer program product, comprising a computer program / instruction, which implements the steps of the above-mentioned resource query method when executed by a processor.

[0032] An embodiment of the present invention realizes receiving a resource query request sent by a front end, wherein the resource query request includes a resource type and a user identity of a resource to be queried; querying target resource information based on the resource type, and querying target configuration information based on the user identity, wherein the target configuration information is the configuration information of a deployed application, and the deployed application is an application that has used the target resource; performing correlation analysis on the target resource information and the target configuration information to obtain a correlation analysis result, wherein the correlation analysis result represents the usage status of at least one application for the resource to be queried; and returning the correlation analysis result to the front end. By querying the target resource information and configuration information based on the resource type and the user identity, the resource management platform can accurately match the resource requested by the user and the corresponding configuration, ensuring that the correct information is provided to the user. By performing correlation analysis on the resource information and the configuration information, the resource management platform can understand the usage status of the application for the resource, which helps to provide more comprehensive data and help users better understand the actual usage and configuration details of the resource. By returning the correlation analysis result to the front end, the user can intuitively understand the usage status of the application for the resource, helping it to make decisions and adjustments quickly. This improves the user experience and helps to improve work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 is a flow chart of a resource query method provided by an embodiment of the present invention;

[0034] Figure 2 is a flow chart of another resource query method provided by an embodiment of the present invention;

[0035] Figure 3 is an interactive schematic diagram of a resource management platform provided by an embodiment of the present invention;

[0036] Figure 4 is a process flow chart of a first resource query method provided by an embodiment of the present invention;

[0037] Figure 5 is a process flow chart of a second resource query method provided by an embodiment of the present invention;

[0038] Figure 6 is a process flow chart of a third resource query method provided by an embodiment of the present invention;

[0039] Figure 7 It is a schematic diagram of the operation interface of a first resource management platform provided by an embodiment of the present invention;

[0040] Figure 8 is a schematic diagram of an operation interface of a second resource management platform provided by an embodiment of the present invention;

[0041] Fig. 9 is a schematic diagram of an operation interface of a third resource management platform provided by an embodiment of the present invention;

[0042] Fig.10 is a schematic diagram of an operation interface of a fourth resource management platform provided by an embodiment of the present invention;

[0043] Fig.11 It is a structural diagram of a resource query device provided by an embodiment of the present invention;

[0044] Fig.12 is a schematic diagram of the structure of another resource query device provided by an embodiment of the present invention;

[0045] Fig.13 It is a structural block diagram of a computing device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0046] Many specific details are set forth in the following description to facilitate a full understanding of the present invention. However, the present invention can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present invention, so the present invention is not limited to the specific implementation disclosed below.

[0047] The terms used in one or more embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present invention. The singular forms of "a", "said" and "the" used in one or more embodiments of the present invention and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of the present invention refers to and includes any or all possible combinations of one or more associated listed items.

[0048] It should be understood that, although the terms first, second, etc. may be used to describe various information in one or more embodiments of the present invention, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of the present invention, the first may also be referred to as the second, and similarly, the second may also be referred to as the first. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0049] In addition, it should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in one or more embodiments of the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0050] First, the terms involved in one or more embodiments of the present invention are explained.

[0051] CAM: Cloud Asset Management.

[0052] SN: Serial Number. A string of numbers or letters, usually an identification code for electronic products. Often used for anti-counterfeiting, its biggest feature is its uniqueness.

[0053] Ajax: Asynchronous JavaScript and XML is a technology used to create asynchronous communications on web pages.

[0054] In the present invention, a resource query method is provided. The present invention also relates to a resource management platform, a resource query device, a computing device, a computer-readable storage medium, and a computer program product, which are described in detail one by one in the following embodiments.

[0055] See also Figure 1 , Figure 1 It is a flow chart of a resource query method provided by an embodiment of the present invention, which specifically includes the following steps.

[0056] Step 102: receiving a resource query request sent by the front end, wherein the resource query request includes a resource type of a resource to be queried and a user identity.

[0057] Resource type of the resource to be queried: used to indicate the type of resource the user wants to query, such as database resources, cloud storage space, computing instances, etc.

[0058] User identity: To ensure security and provide personalized query results, the front end will also attach the current user's unique identifier, such as user ID, Token (flag) or session ID, which is used by the back end to verify user permissions and obtain user-related configuration information.

[0059] In actual applications, when triggered by a user's operation (such as clicking a query button or performing a specific query operation), the front-end application will build a query request. After building the query request, the front-end sends the request to the server through the HTTP / HTTPS protocol or other network communication protocols. This step usually involves network IO operations and may also include serialization (converting the request object into a format suitable for network transmission, such as a JSON string). After receiving the request, the server will first perform some basic processing, such as parsing the request header and request body, and verifying the legitimacy of the request (including checking whether the request format is correct and whether the source is credible). Then, the server will extract two key information in the request: the resource type and the user identity. Based on the extracted information, the server begins to prepare to perform the next step, that is, query the corresponding resource information according to the resource type, and query the related configuration information according to the user identity, in preparation for the subsequent association analysis.

[0060] For example, a cloud service management platform is provided, and user Zhang San wants to query the usage of a certain type of cloud server instance he uses through the platform in order to understand resource allocation and optimization suggestions. Specific steps: The front end builds a query request: After Zhang San logs in to the cloud service management platform, he navigates to the resource monitoring or query page. He selects the resource type from the drop-down menu: "Cloud Server ECS" (representing the resource type he wants to query). The platform automatically recognizes and embeds his user identity, which may be his username "zhangsan" or a more secure user token. After clicking the "Query" button, the front-end application builds a query request package containing "Cloud Server ECS" as the resource type and "zhangsan" as the user identity. The front end sends a request to the server: The front end uses Ajax technology or Fetch API to send this request to the specified API endpoint of the cloud service platform through the HTTPS protocol. The server receives and processes the request: After receiving the request, the server first verifies the legitimacy of the request and confirms that the request comes from a legitimate user and is in the correct format. The resource type in the request is parsed as "Cloud Server ECS" and the user identity "zhangsan".

[0061] Step 104: query target resource information based on resource type, and query target configuration information based on user identity, wherein the target configuration information is configuration information of deployed applications, and deployed applications are applications that have used target resources.

[0062] Target resource information may include the following aspects:

[0063] Usage status: Indicates whether the resource is currently being used, as well as how and to what extent. For example, a cloud server may be in different states such as running, stopped, restarted, or under maintenance.

[0064] Capacity information: describes the resource's storage space, computing power (such as the number of CPU cores, memory size), or network bandwidth, and the amount currently used. This helps assess whether the resource is sufficient to support the existing load or future expansion needs.

[0065] Performance indicators: display the operating efficiency of resources, such as CPU utilization, memory usage, I / O read and write speed, etc. These data can help monitor the health of resources and performance bottlenecks.

[0066] Waiting information: In resource queuing or allocation mechanisms, it may also include the queue status of resource requests, that is, whether there are tasks waiting for the resource to become available.

[0067] Geography and access permissions: Where the resource is physically or logically located, and which users or services have access to it.

[0068] Target configuration information can include the following aspects:

[0069] Application or service identification: Identify which applications or services are consuming or are scheduled to consume resources.

[0070] Resource requirements: The resource requirements configured by the user for the application, such as the required number of CPU cores, memory size, storage space, etc. These configurations reflect the minimum or optimal resource standards for the application to run.

[0071] In actual applications, after receiving a request, the server first parses out the resource type specified in the request, such as "cloud storage", "computing instance" or "database service". Based on the resource type, the platform performs a query operation in the background resource management database. This usually involves SQL query statements to filter out all resource entities of that type and their related information, such as resource ID, name, status, capacity, location, etc. In some cases, the platform may need to further filter the resource information to ensure that the returned data is directly related to the user, for example, only displaying resources that the user has permission to access. Using the user identity (such as the user ID), the platform verifies the validity and permission level of the user in the user authentication module to ensure that the subsequent operations comply with the security policy. After confirming that the user identity is valid, the platform queries the configuration information database related to the user. This configuration information may include, but is not limited to, configuration files, security policies, access control lists (ACLs), resource quotas, etc. of deployed applications. In particular, the platform identifies the configuration information of "deployed applications" that have used or plan to use the target resources. This means that the platform needs to match the resource type with the resource requirements specified in the application configuration to determine which configurations are directly related to the resources to be queried.

[0072] For example, in an enterprise cloud environment, user Zhang San wants to query the usage of a specific model of cloud servers (resource type) used within the enterprise, as well as the configuration details of applications deployed on these servers (applications that have used the target resources). Zhang San queries the resource information of all cloud servers of model "C1.Standard-4" through the cloud management console. After Zhang San enters "C1.Standard-4", he queries the resource management database to find all cloud servers of this model. The query results may include the ID, IP address, region, number of CPU cores, memory size, disk capacity, current operating status (such as running, stopped, maintenance, etc.) of each server, and recent usage statistics (CPU utilization, memory usage, etc.). After the platform confirms Zhang San's administrator authority, it continues to query the deployed application configuration information associated with the "C1.Standard-4" model cloud server based on his identity. Query the application configuration database involved, which lists all applications deployed on such servers, including but not limited to application name, version, deployment time, running status, server resources occupied (such as allocated CPU cores, memory size), automatic expansion rules, security policies, access control lists, etc. In particular, the platform will also display application configurations that are directly related to "C1.Standard-4" server resources in the configuration information to ensure the pertinence and practicality of the information.

[0073] Furthermore, the target resource information includes detailed information of non-cloud resources and list information of cloud resources; querying the target resource information based on the resource type, and querying the target configuration information based on the user identity, including: querying the resource list information of cloud resources and non-cloud resources based on the resource type; querying the target configuration information based on the user identity; determining the non-cloud resource type in the resource list information based on the target configuration information; querying the detailed information of non-cloud resources based on the non-cloud resource type, and combining the detailed information of non-cloud resources with the resource list information of cloud resources into the target resource information.

[0074] Cloud resources refer to the various services, infrastructure or application components provided in the cloud computing platform. These resources are available to users in an on-demand and scalable manner through the network (usually the Internet). Typical features of cloud resources include elastic scaling, resource pooling, self-service, and flexible billing. Common cloud resources include:

[0075] Computing resources: such as virtual machine instances, container instances, serverless functions, etc.

[0076] Storage resources: such as object storage, block storage, file storage, etc.

[0077] Database services: including relational database services, non-relational databases, data warehouses, etc.

[0078] Network resources: such as virtual private cloud, load balancer, cloud firewall, content distribution network, etc.

[0079] Security management: identity and access management, key management services, etc.

[0080] Analysis and big data services: big data processing, machine learning platform, data stream processing, etc.

[0081] Non-cloud resources, also often referred to as local resources or traditional IT resources, refer to hardware, software, and services deployed and run on local data centers or personal computers. These resources do not rely on cloud service providers, but are owned, managed, and maintained by the organization itself. Examples of non-cloud resources include:

[0082] Physical server: Server hardware installed directly within the enterprise.

[0083] Local network equipment: such as routers, switches, local Domain Name System (DNS) servers, Elastic IP Addresses, mail servers, etc.

[0084] Storage devices: such as direct attached storage (DAS), network attached storage (NAS), storage area network (SAN), etc.

[0085] Software Application: An application program installed on a local server or personal computer, such as a database management system.

[0086] In practical applications, first, the system needs to collect detailed information about resources in non-cloud environments from various sources. At the same time, it obtains list information of all relevant resources. Users can specify resource types (such as servers, database instances, storage devices, etc.) according to their needs. The system filters the collected resource information based on the resource types specified by the user, and performs this operation for cloud resources and non-cloud resources respectively. The system authenticates the user based on the user's unique identity (such as user name, access token, etc.), and further checks whether the user has permission to access the requested target configuration information. This step ensures information security and compliance. After verifying the user's permissions, the system queries specific configuration information related to the user. This configuration information may include resource configuration policies, access control rules, security settings, etc. Based on the non-cloud resource types determined from the target configuration information, the system further queries the detailed information of these non-cloud resources. This step refines the data of non-cloud resources to keep the same level of detail as the cloud resource information. Finally, the system combines the queried non-cloud resource details with the previously obtained cloud resource list information to form a comprehensive "target resource information" set. This collection contains the necessary details of all target resources that the user has access to, whether cloud or non-cloud resources, providing users with a one-stop view and management capability for resources.

[0087] Based on this, ensure that the platform can accurately obtain and present the resource information required by users, thereby helping users understand and manage the configuration and status of applications.

[0088] Furthermore, querying the target configuration information based on the user identity includes: based on the user identity, initiating a query request to the local database and the cloud storage service: when the cloud storage service returns a query result, using the query result of the cloud storage service as the target configuration information; when the cloud storage service does not return a query result, using the query result returned by the local database as the target configuration information, and synchronizing the target configuration information to the cloud storage service.

[0089] As a centralized, highly available storage solution, cloud storage services are usually designed to store the latest, verified configuration information. When multiple users or system components synchronize their configurations to the cloud, the cloud storage service can immediately reflect these changes, ensuring that the queried information is the latest and authoritative. If the cloud storage service does not find the relevant configuration information, it means that this is the first time to perform the relevant configuration operation. You need to query the configuration information recorded locally and synchronize it to the cloud storage service.

[0090] In actual applications, query requests are initiated to both the local database and the cloud storage service at the same time. This means that the platform is designed to query both data sources at the same time to improve efficiency and fault tolerance. Processing the response of the cloud storage service: If the cloud storage service returns a query result: The platform directly uses the query result returned by the cloud storage service as the target configuration information. This is because the data of the cloud storage service is generally considered to be the latest and authoritative, and is suitable for most cases. Processing the response of the local database: If the cloud storage service does not return a query result (possibly due to network problems, service unavailability, or data has not yet been synchronized): The platform uses the query result returned by the local database as the target configuration information. The local database, as a data backup or historical data storage, can provide basic configuration information guarantees at this time. Synchronization mechanism: When using the query results of the local database, the platform will automatically trigger a synchronization process to synchronize the target configuration information in the local database to the cloud storage service. This step ensures data consistency and avoids encountering the same problem again the next time you query.

[0091] Based on this, the latest target configuration information can be obtained and synchronized in a timely manner according to the user's identity, ensuring the consistency and accuracy of configuration management in the cloud environment. This method not only improves the system's management efficiency of configuration information, but also ensures the user's consistent experience and operational stability in different environments.

[0092] Step 106: Perform correlation analysis on the target resource information and the target configuration information to obtain a correlation analysis result, wherein the correlation analysis result represents a usage status of at least one application for the resource to be queried.

[0093] In actual applications, a mapping relationship is created based on the queried target resource information and target configuration information. This step is to match each resource (such as server instance, storage volume, etc.) with the application deployed or planned to be deployed on it, and to clarify which applications directly or indirectly use specific resources.

[0094] For example, in an enterprise cloud environment, the administrator is investigating the resource utilization efficiency of the cloud server cluster, especially focusing on the server instances of model "C2.Large". Multiple business applications are running on these servers, including "online mall application", "data analysis platform" and "internal communication tool". Through the API or console of the cloud management platform, query the detailed information of all "C2.Large" server instances. The information includes the instance ID, CPU usage, memory usage, storage space usage, network traffic, and operating status (such as running, stopped, etc.) of each server. For each "C2.Large" server instance, further query the applications deployed on it and their configuration details. For example, the "online mall application" is configured to use 2vCPU and 8GB of memory; the "data analysis platform" is configured to use 4vCPU, 16GB of memory, and an automatic expansion policy is set; the "internal communication tool" is configured to use 1vCPU and 4GB of memory. The "online mall application" is deployed on instance ID A001, using 2vCPU and 8GB of memory. Instance IDB002 runs the "Data Analysis Platform" and is configured with 4vCPU, 16GB of memory, and has an automatic expansion configuration. Instance IDC003 supports the "Internal Communication Tool" and occupies 1vCPU and 4GB of memory. In addition, pay attention to identifying the usage of shared resources. For example, all applications may share a cloud database instance or file storage service, and record the allocation and usage of these shared resources. By analyzing the above mapping relationships, administrators can clearly see which resources each application uses directly or indirectly. For example, due to its resource-intensive nature, the "Data Analysis Platform" has a high configuration and is set to automatically expand to cope with data processing peaks, indicating that it consumes a large amount of resources on the "C2.Large" server. In addition, by comparing the configuration with the actual usage data, the administrator found that although the "Online Mall Application" was configured with 8GB of memory, the actual average usage was only 4GB, and there may be resource redundancy.

[0095] Furthermore, the target resource information includes the usage identifier of each deployed application for the target resource; the target resource information and the target configuration information are correlated and analyzed to obtain the correlation analysis result, including: obtaining the application identifier of at least one deployed application based on the target configuration information; for any application identifier, based on any application identifier and the usage identifier of each deployed application for the target resource, determining the resource usage information corresponding to any application identifier; and combining the resource usage information corresponding to the application identifier of at least one deployed application to obtain the correlation analysis result.

[0096] The usage identifier of each deployed application for the target resource refers to a special tag or reference assigned to each application in the system or network environment to clearly indicate which specific resources the application is using or has been allocated. This identifier is a logical link that associates the application instance with the resources it depends on or occupies (such as database connections, files, network ports, memory blocks, processor time, etc.). The usage identifier can be in many forms, such as file paths, database connection strings, URLs, content URIs (Un iform Resource Identifiers), port numbers, or any other string or code that can uniquely refer to a resource.

[0097] In actual applications, first, the platform needs to collect detailed usage information of all target resources, including but not limited to the resource type (such as server, database), resource ID, resource allocation, current usage status, and the usage identification of the deployed applications associated with it. The usage identification may be one or a group of specific tags used to distinguish the usage of resources by different applications. Then, the platform queries the target configuration information based on the user identity, which includes but is not limited to the configuration details of the application (such as expected resource requirements, deployment strategy), security settings, and application identification. The application identification is the bridge between the configuration information and the actual resource usage. For each deployed application, based on its application identification, the platform searches for the corresponding resource usage identification in the collected target resource information. This step is to determine which resources are used by a specific application, as well as the way and extent of use. Once the corresponding relationship between the application and the resource usage identification is identified, the platform further analyzes the usage of these resources. For example, check whether the actual CPU, memory, and storage used by the application are consistent with the requirements set in the configuration information, and whether there is resource overload or waste. For each deployed application, the corresponding resource usage information is collected and combined based on its application identification to form a comprehensive view. This includes the total resource consumption of the application, resource utilization efficiency, and whether the resource allocation is reasonable. Finally, the platform aggregates the application identifiers of all deployed applications and their corresponding resource usage information to form a correlation analysis result. This result can intuitively display the specific usage status of each application for the target resources, help understand the effectiveness of resource allocation, identify potential optimization space, and assist in decision-making, such as whether it is necessary to adjust resource configuration, optimize application performance, or redeploy certain applications.

[0098] Based on this, it is possible to provide users with detailed resource usage and configuration management suggestions through in-depth analysis and correlation of target resource information and its application configuration information, which helps to improve the manageability and efficiency of the system.

[0099] Further, the target configuration information includes cloud room configuration information; obtaining the application identifier of at least one deployed application based on the target configuration information includes: determining at least one cloud room identifier based on the cloud room configuration information; querying the application identifier of the deployed application in at least one cloud room based on the at least one cloud room identifier; accordingly, combining the resource usage information corresponding to the application identifier of at least one deployed application to obtain an association analysis result, including: for any cloud room, combining the resource usage information corresponding to the deployed application in any cloud room; combining the resource usage information corresponding to at least one cloud room application to obtain an association analysis result.

[0100] A cloud room is used to describe a logically isolated environment or resource collection. This concept does not refer to a physical room, but to a virtual space created on a cloud platform that contains user-defined computing resources and services for specific purposes. These resources may include but are not limited to virtual machine instances, storage capacity, database services, applications, network configurations (such as VPCs, security groups), load balancers, and application deployment environments.

[0101] In actual applications, first, obtain detailed configuration information of the cloud room from the front-end database or cloud service provider. A cloud room can be understood as a logically divided resource collection. Each cloud room may contain a set of servers, storage resources, network configurations, etc., serving a specific application or project group. In the collected configuration information, identify and list all relevant cloud room identifiers. These identifiers are unique and are used to distinguish different cloud room environments. For each cloud room identifier, query all applications deployed in the cloud room and their application identifiers. The application identifier is the only mark to identify a specific application, which helps to accurately track the subsequent resource usage. For each application identifier, obtain the resource information actually used by the application from the monitoring platform or resource management platform, including but not limited to CPU usage, memory usage, storage space, network traffic, etc. This step is the basis for correlation analysis and provides data support for subsequent resource utilization efficiency evaluation and optimization. For each cloud room, summarize the resource usage information of all deployed applications in the cloud room. This includes calculating indicators such as the total resource consumption and average resource usage of the application, so as to understand the overall resource utilization of a single cloud room. The application resource usage information of all cloud rooms is further aggregated to form the correlation analysis results across cloud rooms. This level of analysis can help identify the differences in resource allocation between different cloud rooms, find global patterns or bottlenecks in resource usage, and evaluate the effectiveness of resource scheduling strategies.

[0102] Based on this, it is possible to effectively obtain the application identification of deployed applications in each cloud room based on the cloud room configuration information, and further analyze its resource usage, helping users to better manage and optimize application deployment and resource utilization in the entire cloud environment.

[0103] Step 108: Return the association analysis result to the front end.

[0104] In practical applications, the results of correlation analysis are organized into a format that is easy to understand and display. This usually includes converting complex analysis data into tables, charts, or specific JSON objects to facilitate front-end parsing and display. For example, bar charts and pie charts can be drawn based on the resource usage of each application.

[0105] Furthermore, after returning the association analysis results to the front end, it also includes: saving the association analysis results as an association analysis file and recording the saving time; determining the saving time of the association analysis file based on the saving time and the current time at every preset time period; and deleting the association analysis file when the saving time is greater than a preset time threshold.

[0106] In actual applications, first, when the correlation analysis is completed, the platform will organize and serialize the analysis results (including application resource usage, configuration information correlation matching and other data) (usually converted to JSON, CSV or a specific format), and then save them as one or more files. These files are usually given meaningful names to facilitate identification of the time, scope or specific application scenario of the analysis. When the file is saved, the platform will record the timestamp of this moment. This timestamp is used to track the creation time of the file and is the key basis for subsequent judgment of whether the file is expired. Set a scheduled task or use a scheduled task service (such as cronjob) to automatically wake up and execute the inspection program every preset period (such as once a day, week or month). This preset period is determined according to the data retention policy and resource management requirements. During each scheduled inspection, the program will obtain the current time and compare it with the save time (recorded timestamp) of the correlation analysis file to calculate the length of time each file is saved. According to the calculated save time, it is compared with the preset time threshold. If the save time of a correlation analysis file exceeds the preset time threshold, the file will be considered expired. For those related analysis files that have been saved for more than the preset time threshold, the platform will automatically perform deletion operations to free up storage space and reduce the complexity of data management. Deletion operations should be performed with caution, and it is best to have a backup or archiving mechanism to prevent accidental loss of important data.

[0107] Based on this, the association analysis results can be saved regularly and the saving time can be recorded. The retention period of the file can be controlled according to the preset time threshold to ensure that expired or useless association analysis files are not accumulated in the system, and the system's data is kept neat and resource management efficient.

[0108] See also Figure 2 , Figure 2It is a flowchart of another resource query method provided by an embodiment of the present invention, which specifically includes the following steps.

[0109] Step 202: In response to the input query instruction, a resource query request is generated, wherein the resource query request includes a resource type of a resource to be queried and a user identity.

[0110] Step 204: Send a resource query request to the server.

[0111] Step 206: Receive the association analysis result returned by the server, wherein the association analysis result represents the usage status of the deployed application for the resource to be queried, and the association analysis result is obtained by the server performing an association analysis on the target resource information and the target configuration information, the target configuration information is the configuration information of the deployed application, the target resource information is obtained based on a resource type query, and the target configuration information is obtained based on a user identity query.

[0112] It can be understood that the logic of step 202 to step 206 is the same as the logic of the aforementioned step 102 to step 108, and only the execution subject is different, which will not be repeated here.

[0113] Furthermore, in response to the input query instruction, a resource query request is generated, including: corresponding to the query instruction, verifying the signature information of the query instruction; if the verification is passed, assembling the resource type and user identity of the resource to be queried to generate a resource query request; saving the resource query request; accordingly, after receiving the association analysis result returned by the server, it also includes: associating and storing the resource query request with the association analysis result.

[0114] In actual applications, the platform first receives a query instruction sent by a user or client, which may be an API request, a message in a message queue, or other forms of instructions. The platform needs to parse the instruction to understand the query requirements. In order to ensure the security of the query instruction and the legitimacy of the source, the platform needs to verify the signature information contained in the instruction. This usually involves decrypting the signature using a public key and comparing the decrypted information with the instruction content, or using a pre-shared secret key for verification. If the signature verification fails, subsequent operations are rejected. After the signature verification passes, the platform assembles a resource query request based on the content of the query instruction. This step includes specifying the resource type to be queried (such as database records, files, network resources, etc.) and attaching the user identity of the query initiator. The purpose of this is to enable the server to accurately execute queries based on user permissions and resource types. For auditing, monitoring, or subsequent processing needs, the platform will record the complete resource query request. This may be saved in a log file, database, or other persistent storage medium. The assembled query request is sent to the server, which is responsible for performing the actual resource query operation. After the server processes the query request, it returns the results of the association analysis. These results may include information such as relationships between resources, access statistics, dependency analysis, etc. Finally, the platform associates the original resource query request with the associated analysis results received from the server and stores them. This association helps track the history of queries, evaluate query effects, and perform more in-depth data analysis in the future. This can be achieved by updating database records, creating indexes, or using other data structures.

[0115] Based on this, it can effectively respond to user query instructions, generate and send correct resource query requests, ensure data integrity and security, and flexibly process and store the associated analysis results returned by the service client to provide users with accurate resource usage and configuration information.

[0116] Applied to the resource query method, a resource query request sent by a front end is received, wherein the resource query request includes a resource type and a user identity of the resource to be queried; the target resource information is queried based on the resource type, and the target configuration information is queried based on the user identity, wherein the target configuration information is the configuration information of the deployed application, and the deployed application is the application that has used the target resource; the target resource information and the target configuration information are correlated and analyzed to obtain a correlation analysis result, wherein the correlation analysis result represents the usage status of at least one application for the resource to be queried; and the correlation analysis result is returned to the front end. By querying the target resource information and configuration information based on the resource type and the user identity, the resource management platform can accurately match the resources requested by the user and the corresponding configuration, ensuring that the correct information is provided to the user. By correlating and analyzing the resource information and the configuration information, the resource management platform can understand the usage status of the application for the resource, which helps to provide more comprehensive data and help users better understand the actual usage and configuration details of the resource. By returning the correlation analysis result to the front end, the user can intuitively understand the usage status of the application for the resource, helping it to make decisions and adjustments quickly. This improves the user experience and helps to improve work efficiency.

[0117] See also Figure 3 , Figure 3 It is an interactive schematic diagram of a resource management platform provided by an embodiment of the present invention. Specifically, the resource management platform includes a front end and a server; the front end is used to generate a resource query request in response to an input query instruction, wherein the resource query request includes the resource type and user identity of the resource to be queried; send the resource query request to the server; the server is used to receive the resource query request sent by the front end; query target resource information based on the resource type, and query target configuration information based on the user identity, wherein the target configuration information is the configuration information of at least one application deployed by the front end; perform correlation analysis on the target resource information and the target configuration information to obtain a correlation analysis result, wherein the correlation analysis result represents the usage status of at least one application for the resource to be queried; return the correlation analysis result to the front end; the front end is also used to receive the correlation analysis result returned by the server.

[0118] The resource management platform can use Golang for data visualization development, and combined with related tools and libraries (such as gommicro, Go Elasticsearch and Consul), it can build high-performance, scalable data visualization applications. It is understandable that the above development tools are only used for example, and the present invention does not specifically limit the development tools.

[0119] The resource management platform can also add automated testing capabilities. The automated testing process focuses on functional testing of data visualization applications to ensure their accuracy, stability, reliability and user experience. The following is a summary and analysis of the testing process:

[0120] Test objectives:

[0121] Ensure quality: Improve the accuracy and reliability of your applications by verifying that data visualization functions work as expected and detecting errors and anomalous behavior.

[0122] User experience: Confirm that data visualization meets user needs and provides a good interactive experience.

[0123] Test scope:

[0124] The test covers multiple modules, each module contains multiple test items, mainly focusing on the following aspects:

[0125] Verification of page elements and functions: Check the correctness of resource information cards, filters, sorting, exporting and other functions.

[0126] Data verification: Ensure the accuracy of cloud provider resource data, total resource information, resource ratios, and other data.

[0127] Interaction logic: Test whether the interaction logic such as switch status, filter condition setting, positive and negative selection meets the design requirements.

[0128] Performance and Updates: Verify the efficiency of updating resource operations and the performance of page elements after data is updated.

[0129] Analysis function: whether the resource analysis page elements, data overview, trend charts, etc. are displayed correctly and respond to the filtering conditions.

[0130] Permission management: Check data permission display and filtering functions for different user roles.

[0131] Test environment:

[0132] Number of cases: For example, a total of 204 use cases, all executed, no unexecuted items, and a pass rate of 100%, indicating that the test coverage is comprehensive and the execution is thorough.

[0133] Defect statistics:

[0134] Resolution: For example, all 28 defects found have been closed, with no items to be resolved, not processed, delayed, or optimized, indicating an efficient defect management process.

[0135] Test conclusion:

[0136] Positive results: The test results are consistent with expectations, proving that the data visualization function is effective and can ensure that users enjoy a high-quality data visualization experience.

[0137] Based on this, the automated testing process reflects the comprehensiveness and rigor of the system, verifies all aspects of data visualization applications from multiple dimensions, and focuses not only on functional implementation, but also on user experience and performance. Through detailed test case execution and efficient defect handling mechanism, the quality and stability of the product are effectively improved, ensuring the satisfaction of end users.

[0138] Applied to the resource management platform, by querying the target resource information and configuration information based on resource type and user identity, the resource management platform can accurately match the resources requested by the user and the corresponding configuration, ensuring that the correct information is provided to the user. By performing correlation analysis on resource information and configuration information, the resource management platform can understand the application's use of resources, which helps to provide more comprehensive data and help users better understand the actual use of resources and configuration details. By returning the correlation analysis results to the front end, users can intuitively understand the application's use of resources, helping them make decisions and adjustments quickly. This improves the user experience and helps improve work efficiency.

[0139] See also Figure 4 , Figure 4 This is a flowchart of the processing process of the first resource query method provided by an embodiment of the present invention. Specifically, it is applied to the front end, after receiving the user's query instruction, generating signature information, verifying whether the query instruction complies with the authority; configuring parameters, assembling relevant query parameters according to the content of the query instruction after verification; generating and saving resource query requests, sending them to the server for resource query, receiving and associating the storage and returning the associated analysis results.

[0140] See also Figure 5 , Figure 5 It is a process flow chart of the second resource query method provided by an embodiment of the present invention. It is a specific step of obtaining target configuration information, specifically: after starting, enter the "user identity identification" step. Perform local database query and cloud storage service query (in parallel) according to user identity. Determine whether the cloud storage service returns a result: if yes, use the return result of the cloud storage service; if not, use the return result of the local database.

[0141] See also Figure 6 , Figure 6This is a flowchart of the processing process of the third resource query method provided by an embodiment of the present invention. It is a specific step of clearing files. Specifically: after starting, enter the judgment condition: "Is the file survival time greater than 2 days?" If the condition is met (that is, the file survival time is greater than 2 days), a request to delete the file is initiated to the object storage service. If the condition is not met (the file survival time is less than or equal to 2 days), the process ends directly.

[0142] See also Figure 7 , Figure 7 It is a schematic diagram of the operation interface of a first resource management platform provided by an embodiment of the present invention. Figure 7 The following is the user interface of the resource list of the resource management platform, which specifically includes: the management selection area of ​​the management platform, Figure 7 The resource list control under the cloud resource visualization selected in the management platform; the cloud product display area, the selection controls for the first cloud vendor, the second cloud vendor, and the third cloud vendor, Figure 7 The middle indicates that the first cloud vendor is selected; the total number of cloud products provided by the first cloud vendor is 5, the total number of resources is 572, the first cloud product involves 320 resources, accounting for 55.94%, the second cloud product involves 120 resources, accounting for 20.98%, the third cloud product involves 98 resources, accounting for 17.13%, the fourth cloud product involves 32 resources, accounting for 5.59%, and the fifth cloud product involves 2 resources, accounting for 0.35%. Users can select specific cloud products through the cloud product filter bar.

[0143] See also Figure 8 , Figure 8 It is a schematic diagram of the operation interface of a second resource management platform provided by an embodiment of the present invention. Figure 8 Shown Figure 7 The specific resource list interface displayed after the user clicks the first cloud product has some elements similar to Figure 7 The same is not repeated here. Figure 7 The different elements specifically include: a resource list display interface including a serial number, a cloud product name, a resource name, a source, a cloud room name, an application name, and a description detail control related to the first cloud product. A user can obtain specific usage details of the row of resources by clicking the detail control.

[0144] See also Fig. 9 , Fig. 9 It is a schematic diagram of the operation interface of a third resource management platform provided by an embodiment of the present invention. Fig. 9 The following is the user interface of resource analysis of the resource management platform, which specifically includes: the management selection area of ​​the management platform, Fig. 9The resource analysis control under cloud resource visualization is selected in the middle management platform; the resource analysis display area includes the resource overview sub-area, which displays the total resources as 32013, the first cloud vendor 2013, the second cloud vendor 15000, and the third cloud vendor 15000. The filter sub-area includes the date filter bar, cloud service provider filter bar, cloud product filter bar, region filter bar, cloud room filter bar, and application filter bar. The visualization display sub-area includes the pie chart display area and the bar chart display area.

[0145] See also Fig.10 , Fig.10 It is a schematic diagram of the operation interface of a fourth resource management platform provided by an embodiment of the present invention. Fig.10 Shown Fig. 9 The specific resource list interface displayed after the user selects the first cloud service provider, first cloud product, first region, first cloud room, and first application. Some of its elements are similar to Fig. 9 The same is not repeated here. Fig. 9 The different elements specifically include: a resource list display interface, including the first application-related serial number, cloud product name, resource name, source, cloud room name, application name, and description detail control. The user can obtain specific usage details of the row of resources by clicking the detail control.

[0146] Corresponding to the above method embodiment, the present invention also provides a resource query device embodiment, Fig.11 FIG. 1 is a schematic diagram of a resource query device provided by an embodiment of the present invention. Fig.11 As shown, the device comprises:

[0147] The first receiving module 1120 is configured to receive a resource query request sent by the front end, wherein the resource query request includes a resource type of a resource to be queried and a user identity;

[0148] The query module 1140 is configured to query target resource information based on resource type and query target configuration information based on user identity, wherein the target configuration information is configuration information of deployed applications, and the deployed applications are applications that have used target resources;

[0149] The association analysis module 1160 is configured to perform an association analysis on the target resource information and the target configuration information to obtain an association analysis result, wherein the association analysis result represents a usage status of at least one application for the resource to be queried;

[0150] The return module 1180 is configured to return the association analysis result to the front end.

[0151] Optionally, the target resource information includes detailed information of non-cloud resources and list information of cloud resources; accordingly, the query module 1140 is further configured to query resource list information of cloud resources and non-cloud resources based on resource type; query target configuration information based on user identity; determine the non-cloud resource type in the resource list information based on the target configuration information; query detailed information of non-cloud resources based on the non-cloud resource type, and combine the detailed information of non-cloud resources with the resource list information of cloud resources into target resource information.

[0152] Optionally, the query module 1140 is further configured to initiate a query request to the local database and the cloud storage service based on the user identity: if the cloud storage service returns a query result, the query result of the cloud storage service is used as the target configuration information; if the cloud storage service does not return a query result, the query result returned by the local database is used as the target configuration information, and the target configuration information is synchronized to the cloud storage service.

[0153] Optionally, the target resource information includes the usage identifier of each deployed application for the target resource; accordingly, the association analysis module 1160 is further configured to obtain the application identifier of at least one deployed application based on the target configuration information; for any application identifier, based on any application identifier and the usage identifier of each deployed application for the target resource, determine the resource usage information corresponding to any application identifier: combine the resource usage information corresponding to the application identifier of at least one deployed application to obtain the association analysis result.

[0154] Optionally, the target configuration information includes cloud room configuration information; accordingly, the association analysis module 1160 is further configured to determine at least one cloud room identifier based on the cloud room configuration information; based on the at least one cloud room identifier, query the application identifier of the deployed application in at least one cloud room; accordingly, combine the resource usage information corresponding to the application identifier of at least one deployed application to obtain the association analysis result, including: for any cloud room, combine the resource usage information corresponding to the deployed application in any cloud room; combine the resource usage information corresponding to at least one cloud room application to obtain the association analysis result.

[0155] Fig.12 FIG. 1 is a schematic diagram of the structure of another resource query device provided by an embodiment of the present invention. Fig.12 As shown, the device comprises:

[0156] The generating module 1220 is configured to generate a resource query request in response to the input query instruction, wherein the resource query request includes a resource type of the resource to be queried and a user identity;

[0157] The sending module 1240 is configured to send a resource query request to the server;

[0158] The second receiving module 1260 is configured to receive the association analysis result returned by the server, wherein the association analysis result represents the usage status of the deployed application for the resource to be queried, and the association analysis result is obtained by the server performing an association analysis on the target resource information and the target configuration information, the target configuration information is the configuration information of the deployed application, the target resource information is obtained based on a resource type query, and the target configuration information is obtained based on a user identity query.

[0159] Optionally, the generation module 1220 is further configured to verify the signature information of the query instruction in response to the query instruction; if the verification is successful, assemble the resource type and user identity of the resource to be queried to generate a resource query request; save the resource query request; accordingly, the resource query device also includes an associated storage module, which is configured to associate and store the resource query request with the associated analysis result.

[0160] Applied to the resource query device, by querying the target resource information and configuration information based on the resource type and user identity, the resources requested by the user and the corresponding configuration can be accurately matched to ensure that the correct information is provided to the user. By performing correlation analysis on the resource information and configuration information, the resource usage status of the application can be understood, which helps to provide more comprehensive data and help users better understand the actual usage and configuration details of the resources. By returning the correlation analysis results to the front end, the user can intuitively understand the resource usage status of the application, helping it to make decisions and adjustments quickly. This improves the user experience and helps to improve work efficiency.

[0161] The above is a schematic scheme of a resource query device of this embodiment. It should be noted that the technical scheme of the resource query device and the technical scheme of the resource query method described above are of the same concept, and the details not described in detail in the technical scheme of the resource query device can be found in the description of the technical scheme of the resource query method described above.

[0162] Fig.13 13 is a block diagram of a computing device provided by an embodiment of the present invention. The components of the computing device 1300 include but are not limited to a memory 1310 and a processor 1320. The processor 1320 is connected to the memory 1310 via a bus 1330, and the database 1350 is used to store data.

[0163] The computing device 1300 also includes an access device 1340 that enables the computing device 1300 to communicate via one or more networks 1360. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 1340 may include one or more of any type of network interface, wired or wireless (e.g., a network interface card (NIC)), such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, and a Near Field Communication (NFC).

[0164] In one embodiment of the present invention, the above components of the computing device 1300 and Fig.13 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Fig.13 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of the present invention. Those skilled in the art may add or replace other components as needed.

[0165] The computing device 1300 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a personal computer (PC). The computing device 1300 may also be a mobile or stationary server.

[0166] The processor 1320 is used to execute the following computer program / instruction, which implements the steps of the above-mentioned resource query method when executed by the processor.

[0167] Each embodiment of the present invention is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the computing device embodiment, since it is basically similar to the resource query method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the resource query method embodiment.

[0168] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program / instruction, which implements the steps of the above-mentioned resource query method when executed by a processor.

[0169] Each embodiment of the present invention is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the computer-readable storage medium embodiment, since it is basically similar to the resource query method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the resource query method embodiment.

[0170] An embodiment of the present invention further provides a computer program product, including a computer program / instruction, which implements the steps of the above-mentioned resource query method when executed by a processor.

[0171] The above is a schematic scheme of a computer program product of this embodiment. It should be noted that the technical scheme of the computer program product and the technical scheme of the resource query method described above are of the same concept, and the details not described in detail in the technical scheme of the computer program product can be found in the description of the technical scheme of the resource query method described above.

[0172] The above describes specific embodiments of the present invention. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0173] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of patent practice. For example, in some regions, according to patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.

[0174] It should be noted that, for the convenience of description, the aforementioned method embodiments are all described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the described action sequence, because according to the embodiments of the present invention, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the embodiments of the present invention.

[0175] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0176] The preferred embodiments of the present invention disclosed above are only used to help explain the present invention. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the embodiments of the present invention. The present invention selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of the present invention, so that those skilled in the art can understand and use the present invention well. The present invention is limited only by the claims and their full scope and equivalents.

Claims

1. A resource query method, characterized in that: Applied to the server, including: Receiving a resource query request sent by the front end, wherein the resource query request includes a resource type of a resource to be queried and a user identity; querying target resource information based on the resource type, and querying target configuration information based on the user identity, wherein the target configuration information is configuration information of a deployed application, and the deployed application is an application that has used the target resource; Performing correlation analysis on the target resource information and the target configuration information to obtain a correlation analysis result, wherein the correlation analysis result represents a usage status of the at least one application for the resource to be queried; The association analysis result is returned to the front end.

2. The method according to claim 1, characterized in that The target resource information includes detailed information of non-cloud resources and list information of cloud resources; the querying of the target resource information based on the resource type and the querying of the target configuration information based on the user identity include: Querying resource list information of the cloud resources and the non-cloud resources based on the resource type; Querying target configuration information based on the user identity identifier; Based on the target configuration information, determining a non-cloud resource type in the resource list information; Detailed information of non-cloud resources is queried based on the non-cloud resource type, and the detailed information of the non-cloud resources is combined with the resource list information of the cloud resources into target resource information.

3. The method according to claim 2, characterized in that The querying of target configuration information based on the user identity identifier includes: Based on the user identity, a query request is initiated to the local database and the cloud storage service: In the case where the cloud storage service returns a query result, using the query result of the cloud storage service as the target configuration information; In the case that the cloud storage service does not return a query result, the query result returned by the local database is used as target configuration information, and the target configuration information is synchronized to the cloud storage service.

4. The method according to claim 1, characterized in that: The target resource information includes a usage identifier of each deployed application for the target resource; the correlation analysis of the target resource information and the target configuration information to obtain the correlation analysis result includes: Acquire an application identifier of at least one deployed application based on the target configuration information; For any of the application identifiers, based on any of the application identifiers and identifiers of each of the deployed applications using the target resource, determine resource usage information corresponding to any of the application identifiers: The resource usage information corresponding to the application identifier of the at least one deployed application is combined to obtain a correlation analysis result.

5. The method according to claim 4, characterized in that The target configuration information includes cloud room configuration information; and obtaining the application identifier of at least one deployed application based on the target configuration information includes: Based on the cloud room configuration information, determining at least one cloud room identifier; Based on the at least one cloud room identifier, querying the application identifier of the deployed application in at least one cloud room; Accordingly, the combining the resource usage information corresponding to the application identifier of the at least one deployed application to obtain the correlation analysis result includes: For any cloud room, combining resource usage information corresponding to the deployed applications in the any cloud room; The resource usage information corresponding to at least one cloud room application is combined to obtain a correlation analysis result.

6. The method according to claim 1, characterized in that After returning the association analysis result to the front end, the method further includes: Saving the association analysis result as an association analysis file and recording the saving time; Determining the saving time of the association analysis file based on the saving time and the current time at every preset time period; When the storage time is greater than a preset time threshold, the association analysis file is deleted.

7. A resource query method, characterized in that: Applied to the front end, including: In response to the input query instruction, a resource query request is generated, wherein the resource query request includes a resource type of a resource to be queried and a user identity identifier; Sending the resource query request to the server; Receive the association analysis result returned by the server, wherein the association analysis result represents the usage status of the deployed application for the resource to be queried, and the association analysis result is obtained by the server performing an association analysis on the target resource information and the target configuration information, the target configuration information is the configuration information of the deployed application, the target resource information is obtained based on the resource type query, and the target configuration information is obtained based on the user identity query.

8. The method according to claim 1, characterized in that The step of generating a resource query request in response to an input query instruction includes: Corresponding to the query instruction, verifying the signature information of the query instruction; If the verification is successful, assemble the resource type and user identity of the resource to be queried and generate a resource query request; Saving the resource query request; Accordingly, after receiving the association analysis result returned by the server, the method further includes: The resource query request and the association analysis result are stored in association.

9. A resource management platform, characterized in that: Including front-end and server; The front end is used to generate a resource query request in response to an input query instruction, wherein the resource query request includes a resource type of a resource to be queried and a user identity; and send the resource query request to the server; The server is used to receive the resource query request sent by the front end; query the target resource information based on the resource type, and query the target configuration information based on the user identity, wherein the target configuration information is the configuration information of at least one application deployed by the front end; perform correlation analysis on the target resource information and the target configuration information to obtain a correlation analysis result, wherein the correlation analysis result represents the usage status of the at least one application for the resource to be queried; and return the correlation analysis result to the front end; The front end is also used to receive the correlation analysis result returned by the server.

10. A resource query device, characterized in that: Applied to the server, including: A first receiving module is configured to receive a resource query request sent by a front end, wherein the resource query request includes a resource type of a resource to be queried and a user identity; A query module, configured to query target resource information based on the resource type, and query target configuration information based on the user identity, wherein the target configuration information is configuration information of a deployed application, and the deployed application is an application that has used the target resource; an association analysis module, configured to perform an association analysis on the target resource information and the target configuration information to obtain an association analysis result, wherein the association analysis result represents a usage status of the at least one application for the resource to be queried; The returning module is configured to return the association analysis result to the front end.

11. A resource query device, characterized in that: Applied to the front end, including: A generating module is configured to generate a resource query request in response to an input query instruction, wherein the resource query request includes a resource type of a resource to be queried and a user identity; A sending module, configured to send the resource query request to the server; The second receiving module is configured to receive the association analysis result returned by the server, wherein the association analysis result represents the usage status of the deployed application for the resource to be queried, and the association analysis result is obtained by the server performing an association analysis on the target resource information and the target configuration information, the target configuration information is the configuration information of the deployed application, the target resource information is obtained based on the resource type query, and the target configuration information is obtained based on the user identity query.

12. A computing device, characterized in that: include: Memory and processor; The memory is used to store computer programs / instructions, and the processor is used to execute the computer programs / instructions. When the computer program / instructions are executed by the processor, the steps of the resource query method described in any one of claims 1-6 or claims 7-8 are implemented.

13. A computer-readable storage medium, characterized in that: It stores a computer program / instruction, which, when executed by a processor, implements the steps of the resource query method described in any one of claims 1-6 or claims 7-8.

14. A computer program product, characterized in that The method comprises a computer program / instruction, which, when executed by a processor, implements the steps of the resource query method described in any one of claims 1 to 6 or claims 7 to 8.

Images