CN116795636B - Service system data monitoring method and device, electronic equipment and storage medium - Google Patents
Service system data monitoring method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN116795636B CN116795636B CN202310747957.1A CN202310747957A CN116795636B CN 116795636 B CN116795636 B CN 116795636B CN 202310747957 A CN202310747957 A CN 202310747957A CN 116795636 B CN116795636 B CN 116795636B
- Authority
- CN
- China
- Prior art keywords
- node
- monitoring
- configuration file
- identifier
- application module
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 200
- 238000000034 method Methods 0.000 title claims abstract description 50
- 238000001514 detection method Methods 0.000 claims abstract description 15
- 230000004044 response Effects 0.000 claims description 4
- 230000009191 jumping Effects 0.000 claims description 3
- 238000012806 monitoring device Methods 0.000 claims description 2
- 230000006870 function Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 5
- 230000000007 visual effect Effects 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000018109 developmental process Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000006467 substitution reaction Methods 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 238000013480 data collection Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008929 regeneration Effects 0.000 description 1
- 238000011069 regeneration method Methods 0.000 description 1
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a business system data monitoring method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module as node metadata; the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier; detecting the node identification, and registering the monitoring node according to the node metadata based on the target detection result to obtain a registration identification; rewriting a node identifier of the configuration file through the registration identifier; continuously collecting and storing configuration files of the target application module according to the rewritten node identification; and obtaining monitoring data according to the index information and the graphic information in the configuration file. The invention can realize automatic node registration, conveniently realize data monitoring of the service system, and can be widely applied to the technical field of computers.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and apparatus for monitoring service system data, an electronic device, and a storage medium.
Background
With the increase of the informatization degree of enterprises, the business system has become a core and a foundation of enterprise operation, so that monitoring the business system is very important. The monitoring of the service system in the prior art generally requires the following 3 steps: 1. the service system integrates the monitoring sdk or realizes a monitoring data acquisition interface according to a monitoring protocol; 2. the monitoring server side configures a monitoring data acquisition task to acquire data from the service platform at regular time; 3. and the operation and maintenance personnel configure the monitoring chart on the monitoring platform and view and analyze the monitoring data. However, the existing monitoring procedure has the following disadvantages: after each application node integrates monitoring, the configuration is added on a monitoring platform, and the monitoring data of the new node is acquired; each new node needs to configure the chart on the monitoring platform to display the monitoring data.
Disclosure of Invention
In view of the above, the embodiments of the present invention provide a method, an apparatus, an electronic device, and a storage medium for monitoring service system data, which can conveniently monitor service system data.
In one aspect, an embodiment of the present invention provides a method for monitoring service system data, including:
responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module as node metadata;
the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier;
detecting the node identification, and registering the monitoring node according to the node metadata based on the target detection result to obtain a registration identification;
rewriting a node identifier of the configuration file through the registration identifier;
continuously collecting and storing configuration files of the target application module according to the rewritten node identification;
and obtaining monitoring data according to the index information and the graphic information in the configuration file.
Optionally, in response to a start signal of a target application module in the service system, acquiring a configuration file of the target application module as node metadata includes:
responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module from a monitoring SDK as node metadata;
wherein, the monitoring SDK is integrated in each application module of the business system in advance.
Optionally, the initial value of the node identifier is 0, and monitoring node registration is performed according to the node metadata based on the detection result, so as to obtain a registration identifier, including:
when the node identifier is 0, the node metadata is stored in the target database, and a globally unique registration identifier is generated through the self-increasing primary key, so that the node identifier of the node metadata in the target database is updated.
Optionally, the method further comprises:
when the node identification is not 0, traversing and searching in the target database based on the node identification;
when the node identifier does not exist in the target database, the node metadata is stored in the target database, and the globally unique registration identifier is generated through the self-increasing primary key, so that the node identifier of the node metadata in the target database is updated.
Optionally, the method further comprises:
when the node identification exists in the target database, saving the node metadata to the target database, and jumping to the step of continuously collecting and saving the configuration file of the target application module;
the collected configuration files are stored in a target database.
Optionally, continuously collecting and storing the configuration file of the target application module according to the rewritten node identifier, including:
and periodically acquiring a configuration file from the target application module based on a preset period according to the rewritten node identification as an index, and storing the configuration file into a target database.
Optionally, the monitoring data includes monitoring index data and a monitoring chart, and the obtaining the monitoring data according to the index information and the graphic information in the configuration file includes:
responding to the inquiry instruction, and acquiring the stored configuration file of the target application module from the target database; the query instruction takes the rewritten node identifier as a query index;
obtaining monitoring index data according to the index information in the configuration file;
and extracting target index data from the monitoring index data based on the display configuration of the preset index in the graphic information, and combining the image data in the graphic information to obtain the monitoring chart.
In another aspect, an embodiment of the present invention provides a service system data monitoring apparatus, including:
the first module is used for responding to a starting signal of a target application module in the service system and acquiring a configuration file of the target application module as node metadata;
the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier;
the second module is used for detecting the node identification, and carrying out monitoring node registration according to the node metadata based on the target detection result to obtain a registration identification;
a third module, configured to rewrite the node identifier of the configuration file through the registration identifier;
a fourth module, configured to continuously collect and store a configuration file of the target application module according to the rewritten node identifier;
and a fifth module for obtaining the monitoring data according to the index information and the graphic information in the configuration file.
In another aspect, an embodiment of the present invention provides an electronic device, including a processor and a memory;
the memory is used for storing programs;
the processor executes a program to implement the method as before.
In another aspect, embodiments of the present invention provide a computer-readable storage medium storing a program for execution by a processor to perform a method as previously described.
Embodiments of the present invention also disclose a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions may be read from a computer-readable storage medium by a processor of a computer device, and executed by the processor, to cause the computer device to perform the foregoing method.
Firstly, responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module as node metadata; the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier; detecting the node identification, and registering the monitoring node according to the node metadata based on the target detection result to obtain a registration identification; rewriting a node identifier of the configuration file through the registration identifier; continuously collecting and storing configuration files of the target application module according to the rewritten node identification; and obtaining monitoring data according to the index information and the graphic information in the configuration file. The embodiment of the invention can register the node by taking the configuration file as the node metadata based on the starting information of the application module. After the node registration is successful, node information in the node metadata and graph and index information of the node are stored, and further automatic display of the graph and index data of the node is realized according to the graph and index configuration information of the node. According to the embodiment of the invention, through the detection of the node identification and the unified configuration of the node metadata, the automatic node registration is realized in response to the starting information, and further, the data monitoring of the service system is conveniently realized.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flow chart of a method for monitoring service system data according to an embodiment of the present invention;
FIG. 2 is a system architecture diagram of a monitoring SDK and a monitoring platform according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of an overall flow of registration, graph, index, and monitoring data collection reporting of a monitoring node according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a service system data monitoring device according to an embodiment of the present invention;
fig. 5 is a schematic diagram of a frame of an electronic device according to an embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Firstly, it should be noted that, in order to facilitate understanding of the technical solution of the present invention, the embodiments of the present invention may relate to terms for explanation:
SDK: the SDK, collectively referred to as Software Development Kit (software development kit), is an integrated kit that integrates multiple tools and components to facilitate application development by software developers.
metric: monitoring an index, defining an index display name and an index type
graph: and the monitoring chart consists of chart names and monitoring middle indexes, and a plurality of index data are displayed in one monitoring chart.
And (3) node: and the application module or the monitored component of the monitoring SDK is integrated, and after the application or the monitored component is monitored, the monitoring platform generates node information, so that the monitoring platform can check the monitoring data of the application or the monitored component through the node.
Node metadata: all configuration information of one monitoring node is included, and the configuration information mainly comprises basic information of the node, graph and index configuration information of the node.
In one aspect, as shown in fig. 1, an embodiment of the present invention provides a method for monitoring service system data, including:
s100, responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module as node metadata;
the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier;
it should be noted that, in some embodiments, step S100 may include: responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module from a monitoring SDK as node metadata; wherein, the monitoring SDK is integrated in each application module of the business system in advance.
In some embodiments, the application/component to be monitored of the service system needs to integrate the monitoring SDK first and configure configuration files required for monitoring the SDK according to the specification configuration. The monitoring SDK profile specification is described as follows:
the monitoring SDK configuration file adopts JSON format configuration and comprises three parts: info: node basic information (Info composition as in table 1); metrics: index list collected by node (Metrics composition is shown in table 2); graph: graph list of nodes (graph composition is shown in table 3).
TABLE 1
| name | Node name |
| desc | Node description |
| nodeId | Node ID, default to 0 |
TABLE 2
| name | Index name |
| showName | Displaying names, and displaying the names by taking the monitoring visual page as an index legend |
| vLabel | Index unit |
| desc | Index description, describing data collected by index |
TABLE 3 Table 3
| name | Graphic name |
| showName | Display name, graphic name displayed on monitored visual page |
| vLabel | Graphic unit |
| refMetrics | A graphically displayed index list configured as index name needed to be displayed on the graph |
The monitoring flow can be realized based on the monitoring SDK configuration file as follows:
a) Acquiring the inside of an integrated application/component to be monitored of a monitoring SDK;
b) Compiling a monitoring SDK configuration file under a configuration file directory of an application module, wherein the configuration file directory is referred to the configuration file specification;
c) And the application/component to be monitored calls the monitoring SDK to realize index data acquisition at the embedded point in the service.
S200, detecting the node identification, and carrying out monitoring node registration according to the node metadata based on a target detection result to obtain a registration identification;
it should be noted that, in some embodiments, the initial value of the node identifier is 0, and step S200 may include: when the node identifier is 0, the node metadata is stored in the target database, and a globally unique registration identifier is generated through the self-increasing primary key, so that the node identifier of the node metadata in the target database is updated.
In some embodiments, the method may further include: the method may further comprise: when the node identification is not 0, traversing and searching in the target database based on the node identification; when the node identifier does not exist in the target database, the node metadata is stored in the target database, and the globally unique registration identifier is generated through the self-increasing primary key, so that the node identifier of the node metadata in the target database is updated.
In some embodiments, the method may further comprise: when the node identification exists in the target database, saving the node metadata to the target database, and jumping to the step of continuously collecting and saving the configuration file of the target application module; the collected configuration files are stored in a target database.
In some embodiments, the method may be implemented based on a system architecture as shown in fig. 2, where the system architecture includes two important components: 1) And (3) a monitoring platform: the system is used for storing monitoring node information, index data, monitoring early warning, monitoring data display and the like; 2) Monitoring the SDK: the method is used for reading the monitoring configuration file, registering the monitoring node, collecting the service data and reporting the monitoring data at regular time.
Wherein, the registration of the monitoring node can be realized by the following steps:
when the application module is started, the node, the graph and the index configuration information are read first, then the monitoring node registration is carried out, if the nodeId is 0, the monitoring service generates a globally unique nodeId and returns the globally unique nodeId to the monitoring SDK, and the implementation flow comprises the following steps: when the application module is started, firstly reading configuration file data of the monitoring SDK as node metadata, then using the node metadata as request parameters to request a node registration interface of the monitoring platform by the monitoring SDK, receiving a node registration request of the SDK by the monitoring platform, detecting whether the nodeId of node information in the node metadata is 0, if the nodeId is 0, indicating that the node is a new registration node, storing the node metadata into a MySQL database by the monitoring platform, generating a globally unique nodeId through an auto-increment primary key of the MySQL, and returning the globally unique nodeId to the monitoring SDK.
And the monitoring SDK writes the returned nodeId into the local configuration file, if the nodeId is more than 0 after the next restarting and the monitoring server exists, the regeneration is not needed, and the implementation flow comprises: after the monitoring SDK receives the nodeId returned by the monitoring platform, the nodeId is updated to a nodeId field of node information in the monitoring SDK configuration file. When the application is restarted, the monitoring SDK requests a node registration interface of the monitoring platform, the nodeId of the node information in the parameter node metadata is greater than 0, and the node ID can be queried in a MySQL database of the monitoring platform, so that the node is registered, and repeated registration is not needed. And updating the metadata of the node in the MySQL database of the monitoring platform according to the metadata of the node in the request parameters.
S300, rewriting a node identifier of the configuration file through the registration identifier;
in some embodiments, the monitoring SDK receives the nodeId field of the node information in the monitoring SDK configuration file, and the monitoring SDK generates a globally unique nodeId by using the self-increasing primary key of MySQL.
S400, continuously collecting and storing configuration files of the target application module according to the rewritten node identification;
it should be noted that, in some embodiments, step S400 may include: and periodically acquiring a configuration file from the target application module based on a preset period according to the rewritten node identification as an index, and storing the configuration file into a target database.
S500, obtaining monitoring data according to index information and graphic information in the configuration file;
it should be noted that, the monitoring data includes monitoring index data and a monitoring chart, and in some embodiments, step S500 may include: responding to the inquiry instruction, and acquiring the stored configuration file of the target application module from the target database; the query instruction takes the rewritten node identifier as a query index; obtaining monitoring index data according to the index information in the configuration file; and extracting target index data from the monitoring index data based on the display configuration of the preset index in the graphic information, and combining the image data in the graphic information to obtain the monitoring chart.
Wherein the index information comprises an index name, an index display name, an index unit and an index description; the graphic information includes a graphic name, a graphic display name, a graphic unit, and a graphic display index list (as a presentation configuration for a preset index).
In some embodiments, steps S400 and S500 may be implemented by: after generating node information, the monitoring platform stores merics (index) and graphics (graphic) information of the node, and the graphic and index information under the node can be checked on a visualized page of the monitoring platform. The method comprises the following steps:
after the SDK registration node is successfully monitored, the monitoring platform stores node metadata into a MySQL database, wherein the node metadata comprises basic information of the node, index information of the node and graphic information of the node. And checking the new registered node in the monitored visual platform, namely, searching the graph and index configuration information of the node according to the node, and automatically displaying the node monitoring chart data according to the graph and index configuration information of the node by the visual page of the monitoring platform.
And then, after the monitoring SDK registration node succeeds, a monitoring index object is created according to the configured index.
The process of monitoring data collection may include:
a) After the application is started, calling a monitoring SDK in the service running process to collect the monitoring into the index object, traversing all indexes every 1 minute by the monitoring SDK, and reporting index data to a monitoring server;
b) After receiving the monitoring data reported by the monitoring SDK, the monitoring service stores the monitoring data into a database;
c) The monitoring service visualization end can check the registered monitoring node, and the monitoring graph (graph) and index (metric) data under the node.
For a complete description of the technical principles of embodiments of the present invention, the following more detailed description of the overall process steps is provided in connection with certain embodiments, it being understood that the following is an explanation of the invention and should not be construed as limiting the invention
Taking the system architecture of fig. 2 as an implementation scenario, as shown in fig. 3, the overall implementation process of the service system data monitoring method of the present invention mainly includes:
the service system needs to integrate the SDK of the monitoring platform and provide configuration files according to the monitoring SDK configuration file specification to register the monitoring nodes and collect the monitoring data. After the service system integrates and monitors the SDK, configuration files required by monitoring are required to be provided according to specifications, and the monitoring files must contain the following 3 configuration items:
nodeId: node ID, default to 0;
metrics: the index, the business monitoring index that needs to be gathered;
graphs: a graph, wherein indexes to be displayed are configured in the graph;
firstly, after the application of a service system is started, the monitoring SDK reports the information to a monitoring platform (registering the monitoring node), the monitoring node generates the monitoring node based on the node identification, if the nodeId in the configuration file is 0, the monitoring platform generates a globally unique nodeId (the monitoring node ID is globally unique and gradually increased) and returns the globally unique nodeId to the SDK side, and the SDK side stores the nodeId generated by the monitoring platform to a local file. And meanwhile, calling a monitoring SDK to collect data, and reporting the configured graph and index information to a monitoring platform at regular time by the monitoring SDK.
The monitoring platform stores the graph and index information of the node, and the node and the monitoring chart and the monitoring index data under the node can be directly checked on the visual page of the monitoring platform.
In summary, in the embodiment of the invention, after the service platform integrates the monitoring SDK, the monitoring configuration file is written according to the specification, and after the monitoring SDK is started, the configuration file is used as node metadata to request the monitoring platform to register the nodes. After the nodes are successfully registered, the monitoring platform stores node information in the node metadata and graph and index information of the nodes, and the visualization platform realizes automatic display of the graph and index data of the nodes according to the graph and index configuration information of the nodes. The invention solves the problems of manually configuring the monitoring acquisition task and manually configuring the monitoring chart by realizing the automatic registration of the monitoring nodes, monitoring indexes, charts and reporting of monitoring data. Other monitoring platforms need to apply an interface for integrating a monitoring SDK or realizing a monitoring data acquisition protocol, a monitoring service configures an acquisition task, periodically acquires monitoring data from an application side and stores the data, when a monitoring chart is checked, the chart needs to be manually created, the monitoring data needing to be displayed by the chart is configured, and each time a new application is accessed to the monitoring platform, the two steps are repeated. And the invention automatically registers and monitors the graph and index information reporting function by the monitoring node, and after all application nodes are accessed to monitor, the graph and index data of the node can be checked on the monitoring platform only by configuring the monitoring node, the graph and the index according to the requirement, and repeated manual configuration is not needed.
In another aspect, as shown in fig. 4, an embodiment of the present invention provides a service system data monitoring apparatus 400, including: a first module 410, configured to obtain, as node metadata, a configuration file of a target application module in a service system in response to a start signal of the target application module; the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier; a second module 420, configured to detect a node identifier, and perform monitoring node registration according to node metadata based on a target detection result, so as to obtain a registration identifier; a third module 430, configured to rewrite the node identifier of the configuration file by the registration identifier; a fourth module 440, configured to continuously collect and store the configuration file of the target application module according to the rewritten node identifier; and a fifth module 450, configured to obtain the monitoring data according to the index information and the graphic information in the configuration file.
It should be noted that, in some embodiments, the apparatus further includes:
a sixth module, configured to perform traversal search on the target database based on the node identifier when the node identifier is not 0; when the node identifier does not exist in the target database, the node metadata is stored in the target database, and the globally unique registration identifier is generated through the self-increasing primary key, so that the node identifier of the node metadata in the target database is updated.
A seventh module, configured to store node metadata in the target database when a node identifier exists in the target database, and skip to the step of continuously collecting and storing the configuration file of the target application module; the collected configuration files are stored in a target database.
The content of the method embodiment of the invention is suitable for the device embodiment, the specific function of the device embodiment is the same as that of the method embodiment, and the achieved beneficial effects are the same as those of the method.
As shown in fig. 5, another aspect of an embodiment of the present invention further provides an electronic device 500, including a processor 510 and a memory 520;
the memory 520 is used for storing programs;
processor 510 executes a program to implement the method as before.
The content of the method embodiment of the invention is suitable for the electronic equipment embodiment, the functions of the electronic equipment embodiment are the same as those of the method embodiment, and the achieved beneficial effects are the same as those of the method.
Another aspect of the embodiments of the present invention also provides a computer-readable storage medium storing a program that is executed by a processor to implement a method as before.
The content of the method embodiment of the invention is applicable to the computer readable storage medium embodiment, the functions of the computer readable storage medium embodiment are the same as those of the method embodiment, and the achieved beneficial effects are the same as those of the method.
Embodiments of the present invention also disclose a computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The computer instructions may be read from a computer-readable storage medium by a processor of a computer device, and executed by the processor, to cause the computer device to perform the foregoing method.
In some alternative embodiments, the functions/acts noted in the block diagrams may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Furthermore, the embodiments presented and described in the flowcharts of the present invention are provided by way of example in order to provide a more thorough understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is changed, and in which sub-operations described as part of a larger operation are performed independently.
Furthermore, while the invention is described in the context of functional modules, it should be appreciated that, unless otherwise indicated, one or more of the functions and/or features may be integrated in a single physical device and/or software module or may be implemented in separate physical devices or software modules. It will also be appreciated that a detailed discussion of the actual implementation of each module is not necessary to an understanding of the present invention. Rather, the actual implementation of the various functional modules in the apparatus disclosed herein will be apparent to those skilled in the art from consideration of their attributes, functions and internal relationships. Accordingly, one of ordinary skill in the art can implement the invention as set forth in the claims without undue experimentation. It is also to be understood that the specific concepts disclosed are merely illustrative and are not intended to be limiting upon the scope of the invention, which is to be defined in the appended claims and their full scope of equivalents.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution apparatus, device, or apparatus, such as a computer-based apparatus, processor-containing apparatus, or other apparatus that can fetch the instructions from the instruction execution apparatus, device, or apparatus and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution apparatus, device, or apparatus.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium may even be paper or other suitable medium upon which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.
It is to be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution device. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present invention have been shown and described, it will be understood by those of ordinary skill in the art that: many changes, modifications, substitutions and variations may be made to the embodiments without departing from the spirit and principles of the invention, the scope of which is defined by the claims and their equivalents.
While the preferred embodiment of the present invention has been described in detail, the present invention is not limited to the embodiments, and those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention, and the equivalent modifications or substitutions are intended to be included in the scope of the present invention as defined in the appended claims.
Claims (8)
1. A method for monitoring data of a service system, comprising:
responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module as node metadata;
the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier;
detecting the node identifier, and performing monitoring node registration according to the node metadata based on a target detection result to obtain a registration identifier; the detecting the node identifier includes: detecting whether the node identification of the node information in the node metadata is 0; the target detection result indicates that the detection result of the node identifier is 0;
rewriting the node identification of the configuration file through the registration identification; the rewriting the node identifier of the configuration file through the registration identifier includes: updating the registration identification to the node identification of the node information in the configuration file;
continuously collecting and storing the configuration file of the target application module according to the rewritten node identification;
the step of continuously collecting and storing the configuration file of the target application module according to the rewritten node identifier comprises the following steps:
periodically acquiring the configuration file from the target application module based on a preset period according to the rewritten node identification as an index, and storing the configuration file into a target database;
obtaining monitoring data according to the index information and the graphic information in the configuration file;
the monitoring data comprises monitoring index data and a monitoring chart, and the monitoring data is obtained according to the index information and the graphic information in the configuration file, and comprises the following steps:
responding to a query instruction, and acquiring the saved configuration file of the target application module from a target database; the query instruction takes the rewritten node identifier as a query index;
obtaining monitoring index data according to the index information in the configuration file;
and extracting target index data from the monitoring index data based on the display configuration of the preset index in the graphic information, and combining the image data in the graphic information to obtain a monitoring chart.
2. The method for monitoring service system data according to claim 1, wherein the obtaining, in response to a start signal of a target application module in a service system, a configuration file of the target application module as node metadata includes:
responding to a starting signal of a target application module in a service system, and acquiring a configuration file of the target application module from a monitoring SDK as node metadata;
wherein, the monitoring SDK is integrated in each application module of the service system in advance.
3. The method for monitoring service system data according to claim 1, wherein the initial value of the node identifier is 0, the monitoring node registration is performed according to the node metadata based on the target detection result, and a registration identifier is obtained, which includes:
and when the node identifier is 0, storing the node metadata into a target database, generating a globally unique registration identifier through an auto-increment primary key, and further updating the node identifier of the node metadata in the target database.
4. A business system data monitoring method according to claim 3, characterized in that the method further comprises:
when the node identifier is not 0, performing traversal searching on the target database based on the node identifier;
and when the node identifier does not exist in the target database, storing the node metadata into the target database, generating a globally unique registration identifier through an auto-increment primary key, and further updating the node identifier of the node metadata in the target database.
5. The method for monitoring data of a business system according to claim 4, further comprising:
when the node identifier exists in the target database, storing the node metadata into the target database, and jumping to the step of continuously collecting and storing the configuration file of the target application module;
and the collected configuration files are stored in the target database.
6. A business system data monitoring device, comprising:
the first module is used for responding to a starting signal of a target application module in the service system and acquiring a configuration file of the target application module as node metadata;
the configuration file and the node metadata comprise node information, index information and graphic information of the node where the target application module is located; the node information comprises a node identifier;
the second module is used for detecting the node identifier, and carrying out monitoring node registration according to the node metadata based on a target detection result to obtain a registration identifier; the detecting the node identifier includes: detecting whether the node identification of the node information in the node metadata is 0; the target detection result indicates that the detection result of the node identifier is 0;
a third module, configured to rewrite the node identifier of the configuration file through the registration identifier; the rewriting the node identifier of the configuration file through the registration identifier includes: updating the registration identification to the node identification of the node information in the configuration file;
a fourth module, configured to continuously collect and store the configuration file of the target application module according to the rewritten node identifier;
the step of continuously collecting and storing the configuration file of the target application module according to the rewritten node identifier comprises the following steps:
periodically acquiring the configuration file from the target application module based on a preset period according to the rewritten node identification as an index, and storing the configuration file into a target database;
a fifth module, configured to obtain monitoring data according to the index information and the graphic information in the configuration file;
the monitoring data comprises monitoring index data and a monitoring chart, and the monitoring data is obtained according to the index information and the graphic information in the configuration file, and comprises the following steps:
responding to a query instruction, and acquiring the saved configuration file of the target application module from a target database; the query instruction takes the rewritten node identifier as a query index;
obtaining monitoring index data according to the index information in the configuration file;
and extracting target index data from the monitoring index data based on the display configuration of the preset index in the graphic information, and combining the image data in the graphic information to obtain a monitoring chart.
7. An electronic device comprising a processor and a memory;
the memory is used for storing programs;
the processor executing the program implements the method of any one of claims 1 to 5.
8. A computer-readable storage medium, characterized in that the storage medium stores a program that is executed by a processor to implement the method of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310747957.1A CN116795636B (en) | 2023-06-21 | 2023-06-21 | Service system data monitoring method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310747957.1A CN116795636B (en) | 2023-06-21 | 2023-06-21 | Service system data monitoring method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116795636A CN116795636A (en) | 2023-09-22 |
| CN116795636B true CN116795636B (en) | 2024-02-13 |
Family
ID=88035789
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310747957.1A Active CN116795636B (en) | 2023-06-21 | 2023-06-21 | Service system data monitoring method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116795636B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5941955A (en) * | 1994-08-12 | 1999-08-24 | British Telecommunications Public Limited Company | Recovery of distributed hierarchical data access routing system upon detected failure of communication between nodes |
| US6065065A (en) * | 1997-01-30 | 2000-05-16 | Fujitsu Limited | Parallel computer system and file processing method using multiple I/O nodes |
| EP2214099A1 (en) * | 2009-01-30 | 2010-08-04 | Tieto Oyj | Method for software package deployment in a network node |
| CN111427841A (en) * | 2020-02-26 | 2020-07-17 | 平安科技（深圳）有限公司 | Data management method and device, computer equipment and storage medium |
| WO2021135279A1 (en) * | 2019-12-30 | 2021-07-08 | 浪潮电子信息产业股份有限公司 | Asymmetric configuration management method, apparatus and device, and readable storage medium |
| WO2022105138A1 (en) * | 2020-11-17 | 2022-05-27 | 平安科技（深圳）有限公司 | Decentralized task scheduling method, apparatus, device, and medium |
| CN115185723A (en) * | 2022-06-02 | 2022-10-14 | 广州市玄武无线科技股份有限公司 | Method, system, device and storage medium for repairing Region meta-information |
| WO2023082800A1 (en) * | 2021-11-11 | 2023-05-19 | 中兴通讯股份有限公司 | Main node selection method, distributed database and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8751777B2 (en) * | 2011-01-28 | 2014-06-10 | Honeywell International Inc. | Methods and reconfigurable systems to optimize the performance of a condition based health maintenance system |
| US10178152B2 (en) * | 2016-04-29 | 2019-01-08 | Splunk Inc. | Central repository for storing configuration files of a distributed computer system |
-
2023
- 2023-06-21 CN CN202310747957.1A patent/CN116795636B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5941955A (en) * | 1994-08-12 | 1999-08-24 | British Telecommunications Public Limited Company | Recovery of distributed hierarchical data access routing system upon detected failure of communication between nodes |
| US6065065A (en) * | 1997-01-30 | 2000-05-16 | Fujitsu Limited | Parallel computer system and file processing method using multiple I/O nodes |
| EP2214099A1 (en) * | 2009-01-30 | 2010-08-04 | Tieto Oyj | Method for software package deployment in a network node |
| WO2021135279A1 (en) * | 2019-12-30 | 2021-07-08 | 浪潮电子信息产业股份有限公司 | Asymmetric configuration management method, apparatus and device, and readable storage medium |
| CN111427841A (en) * | 2020-02-26 | 2020-07-17 | 平安科技（深圳）有限公司 | Data management method and device, computer equipment and storage medium |
| WO2022105138A1 (en) * | 2020-11-17 | 2022-05-27 | 平安科技（深圳）有限公司 | Decentralized task scheduling method, apparatus, device, and medium |
| WO2023082800A1 (en) * | 2021-11-11 | 2023-05-19 | 中兴通讯股份有限公司 | Main node selection method, distributed database and storage medium |
| CN115185723A (en) * | 2022-06-02 | 2022-10-14 | 广州市玄武无线科技股份有限公司 | Method, system, device and storage medium for repairing Region meta-information |
Non-Patent Citations (1)
| Title |
|---|
| MySQL数据库服务器监控系统设计与实现;张伟龙;吕明;胡宏;杜宝珠;张捷;;工业控制计算机(第12期);22-24 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116795636A (en) | 2023-09-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8321479B2 (en) | Efficient processing of time series data | |
| US9400733B2 (en) | Pattern matching framework for log analysis | |
| CN111756575B (en) | Performance analysis method and device of storage server and electronic equipment | |
| US8095514B2 (en) | Treemap visualizations of database time | |
| US8601442B2 (en) | Marker correlation of application constructs with visualizations | |
| CN109669798B (en) | Crash analysis method, crash analysis device, electronic equipment and storage medium | |
| CN109144862A (en) | Statistical method, device, computer equipment and the storage medium of test data | |
| CN111414351A (en) | Performance diagnosis method and device of MySQ L database | |
| CN116795636B (en) | Service system data monitoring method and device, electronic equipment and storage medium | |
| CN112783906A (en) | Log data management method and system for industrial internet | |
| CN115203192B (en) | Cleaning method and device based on visual data and related components | |
| CN112162908A (en) | Program call link monitoring implementation method and device based on bytecode injection technology | |
| CN115225470B (en) | Business abnormality monitoring method and device, electronic equipment and storage medium | |
| CN110929097A (en) | Video recording display method, device and storage medium | |
| CN108108467A (en) | Data-erasure method and device | |
| CN113535538B (en) | Method, device, electronic equipment and storage medium for automatically testing application full link | |
| CN114490558A (en) | OTT video service monitoring method and device | |
| CN114564515A (en) | Unified storage method, device and medium for multi-version knowledge graph | |
| CN112685262A (en) | iOS application program embedded point acquisition method and device based on log | |
| CN112540930A (en) | Evaluation method and device for software update and electronic equipment | |
| Liu et al. | Extraction of attribute dependency graph from database applications | |
| CN112003741B (en) | Alarm data processing method, device, equipment and readable storage medium | |
| CN117033210A (en) | Flow playback test system and method | |
| CN117331566A (en) | Method and equipment for detecting existence of multiple versions of front-end code dependent module | |
| CN115934381A (en) | Dynamic call chain generation and analysis device based on graph database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |