Index chart generation method and device, electronic equipment and storage medium

Abstract

The invention discloses an index chart generation method and device, electronic equipment and a storage medium, and relates to the technical field of data processing. The method comprises the steps of obtaining a target query statement request matched with a target chart page and a request result of the target query statement request in response to a click instruction of the target chart page in a target system; determining a target attribute field according to the target query statement request and a request result of the target query statement request, and determining whether the target attribute field is an entity field; under the condition of determining that the target attribute field is the target entity field, extracting each piece of index data associated with the target entity field from an index database; generating an index chart matched with the target chart page based on the index data; according to the scheme provided by the embodiment of the invention, the target chart page can be subjected to user-defined chart drilling, the index chart matched with the target chart page is generated, and a basis is provided for better understanding the change trend and relation of data in a system subsequently.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a method, device, electronic device and storage medium for generating an indicator chart. Background Art

[0002] Chart drill-down refers to a visual chart interaction method, which is often used in a visual chart. After the chart component detects the user's selection operation on an element in the visual chart, more specific data under the category corresponding to the selected element is displayed through the next level chart.

[0003] At present, when drilling down on any chart page in the system, it is necessary to predefine the fields and generate the drill-down operation statements, and to bring the values ​​of the specified fields into the drill-down search statement to generate the drill-down chart. User-defined chart drill-down cannot be achieved.

[0004] How to perform user-defined chart drill-down on the target chart page and generate indicator charts that match it is a key issue in industry research. Summary of the invention

[0005] The present invention provides a method, device, electronic device and storage medium for generating an indicator chart, so as to perform a user-defined chart drill-down on a target chart page and generate an indicator chart matching it, thereby providing a basis for a better understanding of the changing trends and relationships of various data in the system in the future.

[0006] According to one aspect of the present invention, a method for generating an indicator chart is provided, the method comprising:

[0007] In response to a click instruction of a target chart page in a target system, obtaining a target query statement request matching the target chart page and a request result of the target query statement request;

[0008] Determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field;

[0009] In the case where it is determined that the target attribute field is a target entity field, extracting each indicator data associated with the target entity field from an indicator database;

[0010] An indicator chart matching the target chart page is generated based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

[0011] According to another aspect of the present invention, a device for generating an indicator chart is provided, the device comprising:

[0012] An acquisition module, configured to respond to a click instruction of a target chart page in a target system, and acquire a target query statement request matching the target chart page and a request result of the target query statement request;

[0013] An entity field determination module, used to determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field;

[0014] An indicator data acquisition module, used for extracting each indicator data associated with the target entity field from the indicator database when determining that the target attribute field is a target entity field;

[0015] An indicator chart generation module is used to generate an indicator chart matching the target chart page based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

[0016] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0017] at least one processor; and

[0018] a memory communicatively connected to the at least one processor; wherein,

[0019] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for generating an indicator chart described in any embodiment of the present invention.

[0020] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for generating an indicator chart described in any embodiment of the present invention when executed.

[0021] According to another aspect of the present invention, a computer program product is provided, comprising a computer program, wherein when the computer program is executed by a processor, the method for generating an indicator chart according to any embodiment of the present invention is implemented.

[0022] The technical solution of the embodiment of the present invention obtains a target query statement request and a request result of the target query statement request that match the target chart page in the target system in response to a click instruction of the target chart page in the target system; determines a target attribute field according to the target query statement request and the request result of the target query statement request, and determines whether the target attribute field is an entity field; when it is determined that the target attribute field is a target entity field, extracts each indicator data associated with the target entity field from an indicator database; generates an indicator chart that matches the target chart page based on each indicator data; the indicator chart is a drill-down chart of the target chart page, which solves the problem that user-defined chart drill-down cannot be realized at this stage, and user-defined chart drill-down can be performed on the target chart page to generate an indicator chart that matches it, providing a basis for better understanding of the changing trends and relationships of various data in the system in the future.

[0023] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 is a flow chart of a method for generating an indicator chart according to the first embodiment of the present invention;

[0026] Figure 2 is a flow chart of a method for generating an indicator chart according to Embodiment 2 of the present invention;

[0027] Figure 3 is a schematic diagram of the structure of a device for generating an indicator chart according to Embodiment 3 of the present invention;

[0028] Figure 4 It is a structural schematic diagram of an electronic device for implementing the method for generating an indicator chart according to an embodiment of the present invention. DETAILED DESCRIPTION

[0029] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0031] Embodiment 1

[0032] Figure 1 This is a flow chart of a method for generating an indicator chart according to the first embodiment of the present invention. This embodiment is applicable to the case where a user-defined chart is drilled down on a target chart page to generate an indicator chart that matches it. The method can be executed by an indicator chart generation device, which can be implemented in the form of hardware and / or software. The indicator chart generation device can be configured in an electronic device such as a computer, a server, or a tablet computer. Figure 1 As shown, the method includes:

[0033] Step 110: In response to a click instruction of a target chart page in a target system, a target query statement request matching the target chart page and a request result of the target query statement request are obtained.

[0034] The target system may be any business system, such as a data processing business system, a financial business system, or a production business system, etc., which is not limited in this embodiment. The target chart page may be any page in the target system, such as a link log display page, a system log storage page, or an entity relationship storage page, etc., which is not limited in this embodiment.

[0035] In this embodiment, after the target user clicks on the target chart page in the target system, a click instruction for the target chart page can be automatically triggered. After receiving the click instruction for the target chart page, the processor can obtain a target query statement request that matches the target chart page and a request result of the target query statement request.

[0036] The target query statement request may be SPL (Search Processing Language); for example, an SPL request may be: "index=_o11y_metrics metric:service.latency|bucket timestamp span=1h as ts|stats pct(value,90)as latency_service bytags.service ts|join tags.service[[index=_o11y_metrics metric:service.latency|stats pct(value,90)by tags.service|sort by_pct.value.90|limit5]]"; the request result corresponding to the SPL request may be shown in Table 1:

[0037] Table 1

[0038] timestamp tags.service service.latency_pct.value.90 20241105 10:00:00 service1 342 20241105 11:00:00 service1 544 20241105 12:00:00 service1 454

[0039] Among them, the first column is time, the second column is the entity field, and its specific content will not change with time, and the third column is the indicator, and its specific content changes with time.

[0040] Optionally, in this embodiment, obtaining a target query statement request that matches the target chart page and a request result of the target query statement request may include: obtaining the target query statement request from a target page corresponding to the target chart page; and obtaining the request result of the target query statement request in response to an execution completion instruction of the target query statement request.

[0041] In an optional implementation of the present embodiment, after receiving a click instruction from the target user for a target chart page in the target system, a target query statement request can be further obtained from a target page corresponding to the target chart page; wherein the target page can record query statement requests for all chart pages of the target system; the target page can be displayed in the form of a document or a data table, etc., which is not limited in the present embodiment.

[0042] Optionally, after obtaining the target query statement request, it is possible to further confirm whether the target query statement request has been executed. If it is determined that the target query statement request has been executed, the execution result of the target query statement request can be further obtained and determined as the request result of the target query statement request.

[0043] Step 120: determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field.

[0044] In an optional implementation of this embodiment, after obtaining a target query statement request that matches the target chart page and a request result of the target query statement request, the target attribute field can be further determined based on the obtained target query statement request and the request result of the target query statement request.

[0045] Optionally, in this embodiment, the target query statement request and the request result of the target query statement request may be traversed respectively. If the target query statement request and the request result of the target query statement request both contain a first field, the first field may be determined as the target attribute field.

[0046] In an optional implementation of the present embodiment, determining the target attribute field according to the target query statement request and the request result of the target query statement request may include: parsing the target query statement request to obtain each query field of the target query statement request; traversing each query field to obtain each first query field, and obtaining a subsequent field of each first query field; determining whether the subsequent field of the first query field is the target attribute field according to the request result of the target query statement request.

[0047] Optionally, in this embodiment, after obtaining the target query statement request that matches the target chart page and the request result of the target query statement request, the target query statement request can be further parsed to obtain the query fields of the target query statement request; further, each query field can be traversed to obtain the first query field, and further obtain the subsequent fields of the first query field; exemplarily, in the SPL request of the above example, the first query field can be "by", and the subsequent fields of the first query field are the fields after by, for example, tags.service, ts, and _pct.value.90.

[0048] Furthermore, it is possible to determine whether each subsequent field of the first query field is a target attribute field according to the request result of the target query statement request, and to determine which field among tags.service, ts, and _pct.value.90 is the target attribute field.

[0049] Optionally, in this embodiment, determining whether the subsequent field of the first query field is the target attribute field according to the request result of the target query statement request may include: traversing the request result of the target query statement request, and determining whether the request result contains the subsequent field of the first query field; if it is determined that the request result contains the target subsequent field of the first query field, and the content data of the target subsequent field does not change with time, then determining the target subsequent field as the target attribute field.

[0050] In an optional implementation of the present embodiment, after determining to obtain the subsequent fields of the first query field in the target query statement request, the request result of the target query statement request can be further traversed to determine whether the request result contains the subsequent fields of the first query field; if it is determined that the request result contains the target subsequent field of the first query field (exemplarily, in the above example, the target subsequent field can be tags.service and _pct.value.90), and it can be determined that the content data of the target subsequent field does not change with time, then the target subsequent field can be determined as the target attribute field.

[0051] Exemplarily, in the request result of the above target query statement request, the attribute field tags.service appears, and its specific content does not change with time, then tags.service is a target attribute field; ts is the time of the spl syntax, it will not exist as a result, that is, the field does not appear in the request result of the target query statement request, that is, ts is not a target attribute field; _pct.value.90 is an indicator, and "sort" appears before the "by" field corresponding to the indicator, indicating that this is a sorting indicator, not a target attribute field to be determined; in summary, the target attribute field determined in the above example is "tags.service".

[0052] Further, it can be determined whether the target attribute field is an entity field; optionally, in this embodiment, determining whether the target attribute field is an entity field may include: matching the target attribute field with each entity field in a predefined entity library; if the target attribute field matches the target entity field in the entity library, determining that the target attribute field is an entity field; otherwise, it is a non-entity field.

[0053] Among them, the entity library records all entities related to the target system.

[0054] In an optional implementation of this embodiment, after determining the target attribute field, the target attribute field can be matched with each entity field recorded in the entity library; if it is determined that the target attribute field matches the target entity field in the entity library, it can be determined that the target attribute field is an entity field; otherwise, the target attribute field is a non-entity field.

[0055] For example, after determining that the target attribute field is "tags.service", you can connect to the entity library. If there is an entity field "entity.service" in the entity library, which is also tags.service, both involve service, but the specific names are different, then you can determine that the target attribute field "tags.service" is the entity field.

[0056] In an optional implementation of the present embodiment, after determining to obtain the subsequent fields of the first query field in the target query statement request, the request result of the target query statement request can be further traversed to determine whether the request result contains the subsequent fields of the first query field; if it is determined that the request result contains the target subsequent field of the first query field, and it is determined that the target subsequent field has the highest frequency of occurrence, then the target subsequent field can be determined as the target attribute field.

[0057] Step 130: When it is determined that the target attribute field is a target entity field, extract each indicator data associated with the target entity field from an indicator database.

[0058] In an optional implementation of this embodiment, when it is determined that the target attribute field is a target entity field, each indicator data associated with the target entity field may be further extracted from the indicator database.

[0059] The indicator database stores each entity field and each indicator data corresponding to each entity field.

[0060] Optionally, in this embodiment, when it is determined that the target attribute field is a target entity field, extracting each indicator data associated with the target entity field in the indicator database may include: determining the target entity field and the reference entity field associated with the target entity field in the indicator database; and respectively obtaining the indicator data corresponding to the target entity field and each reference entity field.

[0061] In an optional implementation of the present embodiment, when the target attribute field is determined to be a target entity field, the target entity field and the reference entity field associated with the target entity field can be further determined in the indicator database; and the indicator data corresponding to the target entity field and each reference entity field are respectively obtained, and these indicator data are determined as the indicator data associated with the target entity field.

[0062] Step 140: Generate an indicator chart matching the target chart page based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

[0063] In an optional implementation of this embodiment, after obtaining the indicator data associated with the target entity field, an indicator chart matching the target chart page can be further generated based on the indicator data, wherein the indicator chart matching the target chart page is the drill-down chart of the target chart page.

[0064] Optionally, in this embodiment, after obtaining each indicator data associated with the target entity field, the data type of each indicator data can be further determined, and the type of indicator chart can be determined according to the data type of each indicator data, wherein the type of indicator chart can be a bar chart, a line chart, a pie chart, or a radar chart, etc., which is not limited in this embodiment.

[0065] In another optional implementation of this embodiment, after obtaining the indicator data associated with the target entity field, the indicator data can be further filtered to determine the indicator data that matches the target user's click intention, and an indicator chart that matches the target chart page can be generated based on the filtered indicator data. This ensures that the generated indicator chart meets the user's customized needs.

[0066] The technical solution of this embodiment obtains a target query statement request and a request result of the target query statement request that match the target chart page in the target system in response to a click instruction of the target chart page in the target system; determines a target attribute field according to the target query statement request and the request result of the target query statement request, and determines whether the target attribute field is an entity field; when it is determined that the target attribute field is a target entity field, extracts each indicator data associated with the target entity field from an indicator database; generates an indicator chart that matches the target chart page based on each indicator data; the indicator chart is a drill-down chart of the target chart page, which solves the problem that user-defined chart drill-down cannot be realized at this stage, and user-defined chart drill-down can be performed on the target chart page to generate an indicator chart that matches it, providing a basis for better understanding of the changing trends and relationships of various data in the system in the future.

[0067] Embodiment 2

[0068] Figure 2 1 is a flow chart of a method for generating an indicator chart according to the second embodiment of the present invention. This embodiment is a further refinement of the above technical solution. The technical solution in this embodiment can be combined with each optional solution in one or more of the above embodiments. Figure 2 As shown, the method includes:

[0069] Step 210: In response to a click instruction of a target chart page in a target system, a target query statement request matching the target chart page and a request result of the target query statement request are obtained.

[0070] Step 220: determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field.

[0071] Step 230: When it is determined that the target attribute field is a target entity field, extract each indicator data associated with the target entity field from an indicator database.

[0072] Step 240: Generate an indicator chart matching the target chart page based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

[0073] Step 250: In response to a rendering instruction of the indicator chart, display the indicator chart on a target display page of the target system.

[0074] In an optional implementation of this embodiment, after an indicator chart matching a target chart page is generated, if a rendering instruction for the indicator chart is received, the indicator chart may be displayed on a target online page of the target system.

[0075] In a specific example of the present embodiment, each chart page in the target system is connected to a drill-down processor (a processor in an electronic device, which is named as a drill-down processor in the present embodiment), supporting the automatic acquisition of relevant requests and results after a user clicks; the click event triggers the drill-down processor, and pulls the SPL request related to the current chart page and the request result matching it; further, the field after "by" is parsed from the SPL; it is checked whether the field obtained by the parsing exists as a tag in the request result; further, according to the number of occurrences of the tag, the field with the largest number of occurrences is selected as the target field; further, the entity library can be connected to confirm whether the selected field exists in the entity definition; further, if it is confirmed to exist, the indicator data related to the entity is pulled from the indicator database and transmitted to the view configurator; further, the view configurator generates a new indicator chart based on the received indicator data, and returns it to the drill-down processor; further, the drill-down processor displays the newly generated chart in the user interface.

[0076] The solution of this embodiment, after generating an indicator chart that matches the target chart page, if a rendering instruction of the indicator chart is received, the indicator chart can be displayed on the target online page of the target system, which can meet the user's customized icon drill-down requirements.

[0077] The solution of this embodiment is as follows: users can quickly obtain relevant data by clicking on the chart, which enhances the interactivity and real-time nature of data analysis; at the same time, the entire drill-down process is automated, reducing manual operations and improving user experience and work efficiency; by processing the "by" field, the most meaningful data aggregation can be accurately obtained to ensure that users see representative information; by connecting the entity library and the indicator database, it is ensured that the obtained indicator data matches the actual business object (entity), thereby increasing the accuracy of data analysis; at the same time, the generated chart can change dynamically according to the different needs and clicks of the user, which helps to better understand the trends and relationships behind the data; finally, the relevant indicators are intuitively presented to the user, which improves the efficiency of information communication,

[0078] Embodiment 3

[0079] Figure 3 Schematic diagram of the structure of a device for generating an indicator chart according to Embodiment 3 of the present invention. Figure 3 As shown, the device includes: an acquisition module 310, an entity field determination module 320, an indicator data acquisition module 330 and an indicator chart generation module 340.

[0080] The acquisition module 310 is used to respond to a click instruction of a target chart page in the target system, and acquire a target query statement request matching the target chart page and a request result of the target query statement request;

[0081] An entity field determination module 320, configured to determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field;

[0082] The indicator data acquisition module 330 is used to extract each indicator data associated with the target entity field from the indicator database when it is determined that the target attribute field is a target entity field;

[0083] The indicator chart generating module 340 is used to generate an indicator chart matching the target chart page based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

[0084] The solution of this embodiment is to obtain a target query statement request and a request result of the target query statement request matching the target chart page in the target system in response to a click instruction of the target chart page in the target system through an acquisition module; determine a target attribute field according to the target query statement request and the request result of the target query statement request through an entity field determination module, and determine whether the target attribute field is an entity field; extract each indicator data associated with the target entity field from an indicator database through an indicator data acquisition module when determining that the target attribute field is a target entity field; generate an indicator chart matching the target chart page based on each indicator data through an indicator chart generation module; the indicator chart is a drill-down chart of the target chart page, which solves the problem that user-defined chart drill-down cannot be realized at this stage, and user-defined chart drill-down can be performed on the target chart page to generate an indicator chart matching it, providing a basis for better understanding of the changing trends and relationships of each data in the system in the future.

[0085] In an optional implementation of this embodiment, the acquisition module 310 is specifically configured to acquire the target query statement request from a target page corresponding to the target chart page;

[0086] In response to an execution completion instruction of the target query statement request, a request result of the target query statement request is obtained.

[0087] In an optional implementation of this embodiment, the entity field determination module 320 is specifically configured to parse the target query statement request to obtain each query field of the target query statement request;

[0088] Traversing each of the query fields, obtaining each first query field, and acquiring subsequent fields of each of the first query fields;

[0089] Determine whether a subsequent field of the first query field is the target attribute field according to a request result of the target query statement request.

[0090] In an optional implementation of this embodiment, the entity field determination module 320 is further specifically configured to traverse the request result of the target query statement request and determine whether the request result contains a subsequent field of the first query field;

[0091] If it is determined that the request result contains a target subsequent field of the first query field, and the content data of the target subsequent field does not change over time, the target subsequent field is determined as the target attribute field.

[0092] In an optional implementation of this embodiment, the entity field determination module 320 is further specifically configured to match the target attribute field with each entity field in a predefined entity library;

[0093] If the target attribute field matches the target entity field in the entity library, determining that the target attribute field is an entity field;

[0094] Otherwise, it is a non-entity field.

[0095] In an optional implementation of this embodiment, the indicator database stores each entity field and each indicator data corresponding to each entity field;

[0096] Accordingly, the indicator data acquisition module 330 is specifically used to determine the target entity field and the reference entity field associated with the target entity field in the indicator database;

[0097] The indicator data corresponding to the target entity field and each reference entity field are obtained respectively.

[0098] In an optional implementation of this embodiment, the device for generating an indicator chart further includes: a rendering module, which is used to display the indicator chart on a target display page of the target system in response to a rendering instruction of the indicator chart.

[0099] The device for generating an indicator chart provided in the embodiment of the present invention can execute the method for generating an indicator chart provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0100] In the technical solutions of the embodiments of the present invention, the collection, storage, use, processing, transmission, provision and disclosure of user personal information (such as facial information, voice information, etc.) are in compliance with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0101] Embodiment 4

[0102] Figure 4 A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0103] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0104] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0105] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a method for generating an indicator chart, the method comprising: in response to a click instruction of a target chart page in a target system, obtaining a target query statement request matching the target chart page and a request result of the target query statement request; determining a target attribute field according to the target query statement request and the request result of the target query statement request, and determining whether the target attribute field is an entity field; in the case of determining that the target attribute field is a target entity field, extracting each indicator data associated with the target entity field in the indicator database; generating an indicator chart matching the target chart page based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

[0106] In some embodiments, the method for generating an indicator chart may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the method for generating an indicator chart described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the method for generating an indicator chart in any other appropriate manner (e.g., by means of firmware).

[0107] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0108] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0109] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0110] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0111] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0112] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0113] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0114] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for generating an indicator chart, characterized in that: include: In response to a click instruction of a target chart page in a target system, obtaining a target query statement request matching the target chart page and a request result of the target query statement request; Determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field; In the case where it is determined that the target attribute field is a target entity field, extracting each indicator data associated with the target entity field from an indicator database; An indicator chart matching the target chart page is generated based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

2. The method for generating an indicator chart according to claim 1, characterized in that: The step of obtaining a target query statement request matching the target chart page and a request result of the target query statement request includes: Acquire the target query statement request from a target page corresponding to the target chart page; In response to an execution completion instruction of the target query statement request, a request result of the target query statement request is obtained.

3. The method for generating an indicator chart according to claim 1, characterized in that: The determining the target attribute field according to the target query statement request and the request result of the target query statement request includes: Parsing the target query statement request to obtain each query field of the target query statement request; Traversing each of the query fields, obtaining each first query field, and acquiring subsequent fields of each of the first query fields; Determine whether a subsequent field of the first query field is the target attribute field according to a request result of the target query statement request.

4. The method for generating an indicator chart according to claim 3, characterized in that: The determining, according to the request result of the target query statement request, whether the subsequent field of the first query field is the target attribute field includes: Traversing the request results of the target query statement request, and determining whether the request results contain a subsequent field of the first query field; If it is determined that the request result contains a target subsequent field of the first query field, and the content data of the target subsequent field does not change over time, the target subsequent field is determined as the target attribute field.

5. The method for generating an indicator chart according to claim 1, characterized in that: The determining whether the target attribute field is an entity field includes: Matching the target attribute field with each entity field in a predefined entity library; If the target attribute field matches the target entity field in the entity library, determining that the target attribute field is an entity field; Otherwise, it is a non-entity field.

6. The method for generating an indicator chart according to claim 1, characterized in that: The indicator database stores each entity field and each indicator data corresponding to each entity field; Correspondingly, when it is determined that the target attribute field is a target entity field, extracting each indicator data associated with the target entity field from the indicator database includes: Determining a target entity field and a reference entity field associated with the target entity field in the indicator database; The indicator data corresponding to the target entity field and each reference entity field are obtained respectively.

7. The method for generating an indicator chart according to claim 1, characterized in that: After generating an indicator chart matching the target chart page based on each of the indicator data, the method further includes: In response to the rendering instruction of the indicator chart, the indicator chart is displayed on the target display page of the target system.

8. A device for generating an indicator chart, characterized in that: include: An acquisition module, configured to respond to a click instruction of a target chart page in a target system, and acquire a target query statement request matching the target chart page and a request result of the target query statement request; An entity field determination module, used to determine a target attribute field according to the target query statement request and a request result of the target query statement request, and determine whether the target attribute field is an entity field; An indicator data acquisition module, used for extracting each indicator data associated with the target entity field from the indicator database when determining that the target attribute field is a target entity field; An indicator chart generation module is used to generate an indicator chart matching the target chart page based on each of the indicator data; the indicator chart is a drill-down chart of the target chart page.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method for generating an indicator chart according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method for generating an indicator chart according to any one of claims 1 to 7 when executed.

Images