CN112416897B - Log query method and device, storage medium and electronic device - Google Patents
Log query method and device, storage medium and electronic device Download PDFInfo
- Publication number
- CN112416897B CN112416897B CN202011296389.0A CN202011296389A CN112416897B CN 112416897 B CN112416897 B CN 112416897B CN 202011296389 A CN202011296389 A CN 202011296389A CN 112416897 B CN112416897 B CN 112416897B
- Authority
- CN
- China
- Prior art keywords
- log
- target
- scene
- log data
- identifier
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computational Linguistics (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Mathematical Physics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a log query method and device, a storage medium and an electronic device. Wherein the method comprises the following steps: acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; inquiring log data corresponding to a target log mark in a target system log in response to an inquiry request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; and taking the log data corresponding to the target log identification as a target log, and displaying the target log on a user interface. The invention solves the technical problem of low efficiency of log query.
Description
Technical Field
The present invention relates to the field of computers, and in particular, to a log query method and apparatus, a storage medium, and an electronic device.
Background
An enterprise is often configured with a plurality of different systems, such as a scene center, a field model, a chain tracking system, etc., but the plurality of different systems are independent of each other, so that a scene execution link is long, and the operation of tracking a log is complicated. If the inquiry of one scene fails to be successfully executed, the log files need to be searched in different systems of the scene, the inquiry call chain is searched in the chain tracking system, finally, the parameters issued to the field model are found and provided for the field model responsible person, the field model responsible person finds the call through filtering in the log, the specific failure cause is analyzed, and the long log inquiry process is adopted, so that the inquiry efficiency of the log is quite low.
In view of the above problems, no effective solution has been proposed at present.
Disclosure of Invention
The embodiment of the invention provides a log query method and device, a storage medium and an electronic device, which are used for at least solving the technical problem of low log query efficiency.
According to an aspect of an embodiment of the present invention, there is provided a log query method, including: acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; responding to the query request, and querying log data corresponding to the target log identifier in a target system log, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; and taking the log data corresponding to the target log mark as the target log, and displaying the target log on the user interface.
According to another aspect of the embodiment of the present invention, there is also provided a log query device, including: the system comprises an acquisition unit, a query unit and a storage unit, wherein the acquisition unit is used for acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; a response unit, configured to respond to the query request, and query, in a target system log, log data corresponding to the target log identifier, where the target system log includes log data obtained by integrating first log data generated by a scene center system and second log data generated by a domain model system, where the first log data includes behavior record data after a scene trigger of the scene center system, and the second log data includes action record data after an action is executed by calling a domain model in the domain model system; and a display unit configured to display log data corresponding to the target log identifier as the target log, and to display the target log on the user interface.
According to yet another aspect of the embodiments of the present invention, there is also provided a computer-readable storage medium having a computer program stored therein, wherein the computer program is configured to perform the above log query method when run.
According to still another aspect of the embodiments of the present invention, there is further provided an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor executes the log query method described above through the computer program.
In the embodiment of the invention, a query request triggered on a user interface is acquired, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; responding to the query request, and querying log data corresponding to the target log identifier in a target system log, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; and taking the log data corresponding to the target log mark as the target log, displaying the target log on the user interface, and inquiring the log data corresponding to the log mark based on the log mark, thereby achieving the purpose of quickly inquiring and displaying the log data even though the system is crossed, further realizing the effect of improving the efficiency of the log inquiry, and further solving the technical problem of lower efficiency of the log inquiry.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiments of the invention and together with the description serve to explain the invention and do not constitute a limitation on the invention. In the drawings:
FIG. 1 is a schematic illustration of an application environment of an alternative log query method according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a flow chart of an alternative log query method according to an embodiment of the invention;
FIG. 3 is a schematic diagram of an alternative log query method according to an embodiment of the invention;
FIG. 4 is a schematic diagram of another alternative log query method according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of another alternative log query method according to an embodiment of the invention;
FIG. 6 is a schematic diagram of another alternative log query method according to an embodiment of the invention;
FIG. 7 is a schematic diagram of an alternative log querying device according to an embodiment of the invention;
FIG. 8 is a schematic diagram of another alternative log querying device according to an embodiment of the invention;
FIG. 9 is a schematic diagram of another alternative log querying device according to an embodiment of the invention;
Fig. 10 is a schematic structural view of an alternative electronic device according to an embodiment of the present invention.
Detailed Description
In order that those skilled in the art will better understand the present invention, a technical solution in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in which it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present invention without making any inventive effort, shall fall within the scope of the present invention.
It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
According to an aspect of the embodiment of the present invention, a log query method is provided, optionally, as an optional implementation manner, the log query method may be applied, but is not limited to, in the environment shown in fig. 1. Including but not limited to a user device 102, a network 110, and a server 112, where the user device 102 may include but is not limited to a display 108, a processor 106, and a memory 104. The display 108 may be, but is not limited to, used to display the target log queried after the log query interface triggers a query request.
The specific process comprises the following steps:
step S102, the user equipment 102 obtains a query request triggered by a man-machine interaction screen corresponding to a log query interface, wherein the query request carries a target log identifier;
steps S104-S106, the user equipment 102 sends the query request to the server 112 through the network 110;
step S108, the server 112 searches the log data corresponding to the target log mark through the database 114 and processes the log data through the processing engine 116 so as to generate a target log;
in steps S110-S112, the server 112 sends the target log to the user device 102 over the network 110, the processor 106 in the user device 102 displays the target log in the display 108, and the target log is stored in the memory 104.
In addition, the server 112 may also, but is not limited to, send a query result, where the query result carries an index identifier corresponding to the target log, where the index identifier is used to directly index the target log in the memory 104 of the user device 102; further, the user device 102 receives the index identification and queries the memory 104 for the target log.
Optionally, as an optional implementation manner, as shown in fig. 2, the log query method includes:
s202, acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier;
s204, inquiring log data corresponding to the target log mark in a target system log in response to the inquiring request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions;
S206, taking the log data corresponding to the target log identification as a target log, and displaying the target log on a user interface.
Optionally, the log query method can be applied to query log data of a plurality of systems which are independent but have interconnection relationship, and can be configured with a user interface for man-machine interaction, so that a user can input a log identifier corresponding to the log data to be queried through the user interface to quickly query a target log, and further, different departments of the plurality of systems which are independent but have interconnection relationship do not need to coordinate with each other, and query and index are performed on a relatively integral log only by using the log identifier, thereby improving the efficiency of log query.
Optionally, in this embodiment, the target system log may, but is not limited to, include a plurality of system logs corresponding to systems that are independent of each other and have an interconnection relationship, for example, the first log data generated by the scene center system and the second log data generated by the domain model system, and optionally, the plurality of system logs corresponding to systems that are independent of each other and have an interconnection relationship are integrated, for example, the plurality of system logs are integrated, and then, for example, call addresses of the plurality of system logs are written, and in the query process, log data corresponding to the target log identifier can be called across systems by using the call addresses.
Optionally, in this embodiment, the scene center system is configured to invoke a series of execution events in different scenes, for example, a home-returning scene, and in case that a triggering condition of the home-returning scene is identified to be triggered, trigger a series of execution events corresponding to the home-returning scene in turn based on a pre-configuration of the home-returning scene, for example, control an air conditioner to adjust a room temperature to a preset temperature (for example, 26.4 ℃), control a curtain of a living room to close, turn on a water heater, and so on.
Alternatively, in this embodiment, a domain model system may, but is not limited to, store a plurality of domain models, where the domain models may, but are not limited to, be used to represent entity devices that execute a series of execution events in different scenarios as described above, for example, execute an intelligent air conditioner that adjusts a room temperature to a preset temperature (e.g., 26.4 ℃ and so on) event, an intelligent curtain that controls curtain closing of a living room, an intelligent temperature control system that opens a water heater, and so on.
The method includes the steps that a query request triggered on a user interface is obtained, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; inquiring log data corresponding to a target log mark in a target system log in response to an inquiry request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; and taking the log data corresponding to the target log identification as a target log, and displaying the target log on a user interface.
Further by way of example, the operation scenario of the log query method may be selected, for example, as shown in fig. 3, first, the user triggers a query request on the log query interface, where the query request carries a target log identifier 302, and optionally, the target log identifier 302 may be, but is not limited to, manually input by the user or selected on the log query interface; further, in response to the query request, based on the received target log identifier 302, querying and acquiring log data 304 corresponding to the target log identifier 302 in the target system log; after traversing the target system log, the log data 304 is further integrated into a complete target log 306, and the target log 306 is output and displayed on the log query interface.
According to the embodiment provided by the application, a query request triggered on a user interface is obtained, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; inquiring log data corresponding to a target log mark in a target system log in response to an inquiry request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; the method has the advantages that the log data corresponding to the target log mark is used as the target log and is displayed on the user interface, and the log data corresponding to the log mark is queried based on the log mark, so that the purpose of quickly querying and displaying the log data even though the system is crossed is achieved, and the effect of improving the efficiency of log query is achieved.
As an alternative, querying the target system log for log data corresponding to the target log identifier includes:
s1, calling a scene center system under the condition that a target log identifier comprises a target scene identifier, and inquiring target scene log data corresponding to the target scene identifier in a scene trigger log of a target system log, wherein the target scene log data is used for representing a target scene of the scene center system, and the scene trigger log comprises first log data;
s2, calling a scene center system under the condition that the target log mark also comprises a target scene trigger mark, and inquiring target trigger log data corresponding to the target scene trigger mark in the target scene log data, wherein the target trigger log data is used for representing a trigger target scene;
s3, calling a scene center system under the condition that the target log identifier further comprises a target action identifier, and inquiring target model log data corresponding to the target log identifier in target trigger log data, wherein the target model log data is used for representing a target field model in a calling field model system.
Optionally, in this embodiment, before acquiring the query request triggered on the user interface, the target system log is preconfigured, for example, when different scenes in the scene center system are called, different scene identifiers id are set, a current trigger scene identifier sn is generated in each trigger scene, and different execution actions set different action identifiers actionSn. And further, the trigger log of the scene is recorded in a database scene trigger log table, corresponding actions are triggered when a single scene is executed, and each action is recorded in a database action log table. While the exit and entrance of each service are printed with the target system log.
Further, when the domain model is called to execute the action, the entry log and the exit log are correspondingly printed to the target system log. When the domain model returns data, the detailed concrete execution result is printed to a log. If the device fails to execute the action, the error reason needs to be written into the target system log. Optionally, the target system log also needs an open log query interface.
In addition, an offline management system may be provided, but not limited to, the offline management system is used for querying offline or online log data, and the offline management system is optionally connected with the database by adopting a dual data source switching mode, such as an offline management system login and the like. And when the scene execution log is inquired, switching to a scene database of the scene center system.
Under the condition that the target log mark comprises the target scene mark, a scene center system is called, and target scene log data corresponding to the target scene mark is queried in a scene trigger log of a target system log, wherein the target scene log data is used for representing a target scene of the scene center system, and the scene trigger log comprises first log data; under the condition that the target log mark also comprises a target scene trigger mark, a scene center system is called, and target trigger log data corresponding to the target scene trigger mark is queried in the target scene log data, wherein the target trigger log data is used for representing a trigger target scene; and under the condition that the target log identifier further comprises a target action identifier, calling a scene center system, and inquiring target model log data corresponding to the target log identifier in target trigger log data, wherein the target model log data is used for representing a target domain model in a calling domain model system.
Further by way of example, an optional scenario for invoking a scenario-centric system to query a target log is shown in FIG. 4, and the specific steps are as follows: s402, a user logs in an offline management system 402; s404, a query request is triggered, where the query request is used to query a scenario execution (e.g., a series of scenario event executions) corresponding to a target log identifier, and specifically, a specific query method may, but is not limited to, based on an identifier type included in the target log identifier, for example, query a target scenario (log data) of the scenario execution if the target log identifier includes the scenario identifier, query a target trigger event (log data) of the scenario execution if the target log identifier includes the scenario trigger identifier, and query a target domain model (log data) of the scenario execution if the target log identifier includes the action identifier.
Furthermore, taking the target log identifier including the target scene identifier, the target scene trigger identifier and the target action identifier as an example, the searched target scene log data corresponding to the target scene identifier is used for indicating that the execution of the scene is executed under the target scene, the searched target trigger log data corresponding to the target scene trigger identifier is used for indicating an event or condition triggering the execution of the scene, and in addition, the searched target model log data corresponding to the target action identifier is used for indicating a target field model required to be invoked by the execution of the scene.
According to the embodiment provided by the application, under the condition that the target log identifier comprises the target scene identifier, a scene center system is called, and target scene log data corresponding to the target scene identifier is queried in a scene trigger log of a target system log, wherein the target scene log data is used for representing a target scene of the scene center system, and the scene trigger log comprises first log data; under the condition that the target log mark also comprises a target scene trigger mark, a scene center system is called, and target trigger log data corresponding to the target scene trigger mark is queried in the target scene log data, wherein the target trigger log data is used for representing a trigger target scene; and under the condition that the target log identifier further comprises a target action identifier, a scene center system is called, and target model log data corresponding to the target log identifier is queried in target trigger log data, wherein the target model log data is used for representing a target field model in a calling field model system, so that the purpose of comprehensively querying the target log is achieved, and the effect of improving the comprehensiveness of log query is achieved.
As an alternative, querying the target system log for log data corresponding to the target log identifier includes:
And under the condition that the target log mark comprises the target action mark, invoking the chained tracking system, and inquiring target action log data corresponding to the target action mark in the chained tracking log of the target system log, wherein the target action log data is used for representing that a target domain model in the domain model invoking system executes the target action, and the chained tracking log comprises second log data.
When the target log identifier includes the target action identifier, the chained trace system is called, and target action log data corresponding to the target action identifier is queried in the chained trace log of the target system log, wherein the target action log data is used for indicating that the target domain model in the domain model calling system executes the target action, and the chained trace log includes the second log data. Optionally, the chain tracking system is used to record continuous action log data, such as event log data executed by invoking the target domain model in a target scenario.
Further by way of example, based on the scenario shown in fig. 4, continuing to select, for example, as shown in fig. 5, in the case that only or the target action identifier is included in the target log identifier, invoking the chain tracking system 502, executing step S502 to query the target action log data, and in the case that the query is found, executing step S504 to return the target action log data to the offline management system 402, and further displaying the returned target action log data in the offline management system 402, that is, step S506.
According to the embodiment provided by the application, the chained tracking system is called under the condition that the target log identifier comprises the target action identifier, and the target action log data corresponding to the target action identifier is queried in the chained tracking log of the target system log, wherein the target action log data are used for representing that the target domain model in the domain model system is called to execute the target action, and the chained tracking log comprises the second log data, so that the purpose of comprehensively querying the target log is achieved, and the comprehensive effect of improving the log query is achieved.
As an alternative, before acquiring the query request triggered on the user interface, the method includes:
and receiving a scene trigger log list of the scene center system, wherein the scene trigger log list comprises at least two log identifiers and log data corresponding to the at least two log identifiers, the log identifiers comprise target log identifiers, and the log data comprise target logs.
It should be noted that, a scenario trigger log list of the scenario center system is received, where the scenario trigger log list includes at least two log identifiers and log data corresponding to the at least two log identifiers, the log identifiers include target log identifiers, and the log data includes target logs. Optionally, log identifiers for fast querying or indexing log data may be recorded in the scene trigger log list, but not limited to.
Further by way of example, optional, e.g., as shown in FIG. 6, includes a scene center system 602, a domain model system 604, and a chain tracking system 606, the specific steps are as follows:
step S602, determining a trigger of a scene event, optionally, the scene trigger may be, but not limited to, a preset trigger event being completed, such as a door opening command trigger, a remote command trigger, etc.;
step S604, recording a trigger log in the scene center system 602;
step S606, starting to execute the action of the scene event;
step S608, the action of starting to execute the scene event is completely recorded in a chain tracking log;
step S610, calling a domain model corresponding to the scene event in the domain model 604 for executing the action;
step S612, the call of the domain model is completely recorded in a chain tracking log;
step S614, calling the domain model corresponding to the scene event in the domain model 604 to execute the action;
step S616, the domain model execution action corresponding to the scene event in the calling domain model 604 is completely recorded in the chain tracking log;
step S618, returning the execution result to the scene center system 602;
step S620, the execution result is completely recorded in a chain tracking log;
In step S622, the scene center system 602 also records the execution result.
According to the embodiment of the application, the scene trigger log list of the scene center system is received, wherein the scene trigger log list comprises at least two log identifications and log data corresponding to the at least two log identifications, the log identifications comprise target log identifications, the log data comprise target logs, the corresponding log identifications are distributed for the log data to be queried in advance, and the log identifications and the log data are stored in the list together, so that the aim of facilitating the query of the logs is fulfilled, and the effect of improving the query efficiency of the logs is achieved.
As an alternative, the scene trigger log list includes at least one of the following:
s1, at least two scene identifications and scene log data respectively corresponding to the at least two scene identifications, wherein the scene log data are used for representing scenes of a scene center system;
s2, at least two scene trigger identifiers and trigger log data respectively corresponding to the at least two scene trigger identifiers, wherein the trigger log data are used for representing the scene of the trigger scene center system;
s3, at least two action identifiers and call log data respectively corresponding to the at least two action identifiers, wherein the call log data are used for representing a model of a call domain model.
The system comprises at least two scene identifications and scene log data corresponding to the at least two scene identifications, wherein the scene log data are used for representing scenes of a scene center system; the system comprises at least two scene trigger identifiers and trigger log data respectively corresponding to the at least two scene trigger identifiers, wherein the trigger log data are used for representing the scene of the trigger scene center system; the system comprises at least two action identifiers and call log data respectively corresponding to the at least two action identifiers, wherein the call log data are used for representing a model of a call domain model.
Further, as shown in fig. 6, in the optional steps S604 and S608, the scene identifier and the scene trigger identifier are used to record the target scene and the target trigger event of the scene trigger, in the step S612, the action identifier is used to record the domain model called by the execution action, in the step S616, the action identifier is also used to record the domain model called by the execution action, and in the steps S620 and S622, the scene trigger complete execution process is recorded by using the above-mentioned scene identifier, scene trigger identifier and action identifier in time sequence.
By the embodiment provided by the application, at least two scene identifications and scene log data respectively corresponding to the at least two scene identifications, wherein the scene log data are used for representing scenes of a scene center system; the system comprises at least two scene trigger identifiers and trigger log data respectively corresponding to the at least two scene trigger identifiers, wherein the trigger log data are used for representing the scene of the trigger scene center system; the system comprises at least two action identifiers and call log data respectively corresponding to the at least two action identifiers, wherein the call log data are used for representing a model of a call field model, the aim of completely recording a history execution log is achieved, and the effect of improving the integrity of log records is achieved.
As an alternative, before acquiring the query request triggered on the user interface, the method includes:
and receiving a chain tracking log list of the domain model system, wherein the chain tracking log list comprises at least two action identifiers and action log data respectively corresponding to the at least two action identifiers, and the action log data is used for representing that a domain model in the domain model system is called to execute corresponding actions.
It should be noted that, the chained trace log list of the domain model system is received, where the chained trace log list includes at least two action identifiers and action log data corresponding to the at least two action identifiers respectively, and the action log data is used to indicate that the domain model in the domain model system is called to execute the corresponding action.
Further, as shown in fig. 6, in the optional steps S604 and S608, the scene identifier and the scene trigger identifier are used to record the target scene and the target trigger event of the scene trigger, in the step S612, the action identifier is used to record the domain model called by the execution action, in the step S616, the action identifier is also used to record the domain model called by the execution action, and in the steps S620 and S622, the scene trigger complete execution process is recorded by using the above-mentioned scene identifier, scene trigger identifier and action identifier in time sequence.
According to the embodiment, the chained trace log list of the domain model system is received, wherein the chained trace log list comprises at least two action identifiers and action log data corresponding to the at least two action identifiers respectively, the action log data are used for representing that the domain model in the domain model system is called to execute corresponding actions, the purpose of completely recording history execution logs is achieved, and the effect of improving the integrity of log records is achieved.
It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present invention is not limited by the order of acts described, as some steps may be performed in other orders or concurrently in accordance with the present invention. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required for the present invention.
According to another aspect of the embodiment of the invention, a log query device for implementing the log query method is also provided. As shown in fig. 7, the apparatus includes:
an obtaining unit 702, configured to obtain a query request triggered on a user interface, where the query request carries a target log identifier, and the query request is used to request to query a target log corresponding to the target log identifier;
a response unit 704, configured to respond to the query request, and query, in a target system log, log data corresponding to the target log identifier, where the target system log includes log data obtained by integrating first log data generated by the scene center system and second log data generated by the domain model system, the first log data includes behavior record data after scene triggering of the scene center system, and the second log data includes action record data after invoking a domain model in the domain model system to execute an action;
and a display unit 706, configured to take the log data corresponding to the target log identifier as a target log, and display the target log on the user interface.
Optionally, the log query device can be applied to query log data of a plurality of systems which are independent but have interconnection relationship, and can be configured with a user interface for man-machine interaction, so that a user can input a log identifier corresponding to the log data to be queried through the user interface to quickly query a target log, and further, different departments of the plurality of systems which are independent but have interconnection relationship do not need to coordinate with each other, and query and index are performed on a relatively integral log only by using the log identifier, thereby improving the efficiency of log query.
Optionally, in this embodiment, the target system log may, but is not limited to, include a plurality of system logs corresponding to systems that are independent of each other and have an interconnection relationship, for example, the first log data generated by the scene center system and the second log data generated by the domain model system, and optionally, the plurality of system logs corresponding to systems that are independent of each other and have an interconnection relationship are integrated, for example, the plurality of system logs are integrated, and then, for example, call addresses of the plurality of system logs are written, and in the query process, log data corresponding to the target log identifier can be called across systems by using the call addresses.
Optionally, in this embodiment, the scene center system is configured to invoke a series of execution events in different scenes, for example, a home-returning scene, and in case that a triggering condition of the home-returning scene is identified to be triggered, trigger a series of execution events corresponding to the home-returning scene in turn based on a pre-configuration of the home-returning scene, for example, control an air conditioner to adjust a room temperature to a preset temperature (for example, 26.4 ℃), control a curtain of a living room to close, turn on a water heater, and so on.
Alternatively, in this embodiment, a domain model system may, but is not limited to, store a plurality of domain models, where the domain models may, but are not limited to, be used to represent entity devices that execute a series of execution events in different scenarios as described above, for example, execute an intelligent air conditioner that adjusts a room temperature to a preset temperature (e.g., 26.4 ℃ and so on) event, an intelligent curtain that controls curtain closing of a living room, an intelligent temperature control system that opens a water heater, and so on.
The method includes the steps that a query request triggered on a user interface is obtained, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; inquiring log data corresponding to a target log mark in a target system log in response to an inquiry request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; and taking the log data corresponding to the target log identification as a target log, and displaying the target log on a user interface.
Specific embodiments may refer to examples shown in the above log query method, and in this example, details are not described herein.
According to the embodiment provided by the application, a query request triggered on a user interface is obtained, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier; inquiring log data corresponding to a target log mark in a target system log in response to an inquiry request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions; the method has the advantages that the log data corresponding to the target log mark is used as the target log and is displayed on the user interface, and the log data corresponding to the log mark is queried based on the log mark, so that the purpose of quickly querying and displaying the log data even though the system is crossed is achieved, and the effect of improving the efficiency of log query is achieved.
As an alternative, for example, as shown in fig. 8, the response unit 704 includes:
the first query module 802 is configured to invoke a scenario center system when the target log identifier includes a target scenario identifier, and query, in a scenario trigger log of a target system log, target scenario log data corresponding to the target scenario identifier, where the target scenario log data is used to represent a target scenario of the scenario center system, and the scenario trigger log includes first log data;
the second query module 804 is configured to invoke a scenario center system if the target log identifier further includes a target scenario trigger identifier, and query target trigger log data corresponding to the target scenario trigger identifier in the target scenario log data, where the target trigger log data is used to represent a trigger target scenario;
and a third query module 806, configured to invoke the scene center system if the target log identifier further includes a target action identifier, and query target model log data corresponding to the target log identifier in the target trigger log data, where the target model log data is used to represent a target domain model in the invoke domain model system.
Specific embodiments may refer to examples shown in the above log query method, and in this example, details are not described herein.
As an alternative, the response unit 704 includes:
and the fourth query module is used for calling the chained tracking system under the condition that the target log identifier comprises the target action identifier, and querying target action log data corresponding to the target action identifier in the chained tracking log of the target system log, wherein the target action log data is used for representing that a target domain model in the domain model calling system executes the target action, and the chained tracking log comprises the second log data.
Specific embodiments may refer to examples shown in the above log query method, and in this example, details are not described herein.
As an alternative, for example as shown in fig. 9, it includes:
the first receiving unit 902 is configured to receive, before obtaining a query request triggered on a user interface, a scenario trigger log list of a scenario center system, where the scenario trigger log list includes at least two log identifiers and log data corresponding to the at least two log identifiers, the log identifiers include a target log identifier, and the log data includes a target log.
Specific embodiments may refer to examples shown in the above log query method, and in this example, details are not described herein.
As an alternative, the scene trigger log list includes at least one of the following:
the system comprises at least two scene identifications and scene log data respectively corresponding to the at least two scene identifications, wherein the scene log data are used for representing scenes of a scene center system;
the system comprises at least two scene trigger identifiers and trigger log data respectively corresponding to the at least two scene trigger identifiers, wherein the trigger log data are used for representing the scene of the trigger scene center system;
the system comprises at least two action identifiers and call log data respectively corresponding to the at least two action identifiers, wherein the call log data are used for representing a model of a call domain model.
Specific embodiments may refer to examples shown in the above log query method, and in this example, details are not described herein.
As an alternative, it includes:
the second receiving unit is used for receiving a chain tracking log list of the domain model system before acquiring the query request triggered on the user interface, wherein the chain tracking log list comprises at least two action identifiers and action log data respectively corresponding to the at least two action identifiers, and the action log data is used for representing that the domain model in the domain model system is called to execute corresponding actions.
Specific embodiments may refer to examples shown in the above log query method, and in this example, details are not described herein.
According to a further aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the above-described log-query method, as shown in fig. 10, the electronic device comprising a memory 1002 and a processor 1004, the memory 1002 having stored therein a computer program, the processor 1004 being arranged to perform the steps of any of the method embodiments described above by means of the computer program.
Alternatively, in this embodiment, the electronic apparatus may be located in at least one network device of a plurality of network devices of the computer network.
Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:
s1, acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier;
s2, inquiring log data corresponding to the target log mark in a target system log in response to the inquiring request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions;
And S3, taking the log data corresponding to the target log mark as a target log, and displaying the target log on a user interface.
Alternatively, it will be understood by those skilled in the art that the structure shown in fig. 10 is only schematic, and the electronic device may also be a terminal device such as a smart phone (e.g. an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, and a mobile internet device (Mobile Internet Devices, MID), a PAD, etc. Fig. 10 is not limited to the structure of the electronic device. For example, the electronic device may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 10, or have a different configuration than shown in FIG. 10.
The memory 1002 may be configured to store software programs and modules, such as program instructions/modules corresponding to the log query method and apparatus in the embodiment of the present invention, and the processor 1004 executes the software programs and modules stored in the memory 1002 to perform various functional applications and data processing, that is, implement the log query method described above. The memory 1002 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid state memory. In some examples, the memory 1002 may further include memory located remotely from the processor 1004, which may be connected to the terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. The memory 1002 may be, but is not limited to, for storing information such as a query request, a target log identifier, and a target log. As an example, as shown in fig. 10, the memory 1002 may include, but is not limited to, the acquiring unit 702, the responding unit 704, and the displaying unit 706 in the log querying device. In addition, other module units in the log query device may be included, but are not limited to, and are not described in detail in this example.
Optionally, the transmission device 1006 is configured to receive or transmit data via a network. Specific examples of the network described above may include wired networks and wireless networks. In one example, the transmission means 1006 includes a network adapter (Network Interface Controller, NIC) that can be connected to other network devices and routers via a network cable to communicate with the internet or a local area network. In one example, the transmission device 1006 is a Radio Frequency (RF) module for communicating with the internet wirelessly.
In addition, the electronic device further includes: a display 1008 for displaying the information such as the query request, the target log identifier, and the target log; and a connection bus 1010 for connecting the respective module parts in the above-described electronic device.
According to a further aspect of embodiments of the present invention, there is also provided a computer readable storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.
Alternatively, in the present embodiment, the above-described computer-readable storage medium may be configured to store a computer program for executing the steps of:
S1, acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, and the query request is used for requesting to query a target log corresponding to the target log identifier;
s2, inquiring log data corresponding to the target log mark in a target system log in response to the inquiring request, wherein the target system log comprises log data obtained by integrating first log data generated by a scene center system and second log data generated by a field model system, the first log data comprises behavior record data after scene triggering of the scene center system, and the second log data comprises action record data after calling a field model in the field model system to execute actions;
and S3, taking the log data corresponding to the target log mark as a target log, and displaying the target log on a user interface.
Alternatively, in this embodiment, it will be understood by those skilled in the art that all or part of the steps in the methods of the above embodiments may be performed by a program for instructing a terminal device to execute the steps, where the program may be stored in a computer readable storage medium, and the storage medium may include: flash disk, read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), magnetic or optical disk, and the like.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
The integrated units in the above embodiments may be stored in the above-described computer-readable storage medium if implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present invention may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing one or more computer devices (which may be personal computers, servers or network devices, etc.) to perform all or part of the steps of the method described in the embodiments of the present invention.
In the foregoing embodiments of the present invention, the descriptions of the embodiments are emphasized, and for a portion of this disclosure that is not described in detail in this embodiment, reference is made to the related descriptions of other embodiments.
In several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely exemplary, and the division of the units, such as the division of the units, is merely a logical function division, and may be implemented in another manner, for example, multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interfaces, units or modules, or may be in electrical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The foregoing is merely a preferred embodiment of the present invention and it should be noted that modifications and adaptations to those skilled in the art may be made without departing from the principles of the present invention, which are intended to be comprehended within the scope of the present invention.
Claims (10)
1. A method for querying a log, comprising:
pre-configuring a target system log, comprising: presetting a scene identifier and an action identifier;
Acquiring a query request triggered on a user interface, wherein the query request carries a target log identifier, the query request is used for requesting to query a target log corresponding to the target log identifier, and the target log comprises: when the target log identification comprises the scene identification, calling scene log data corresponding to the scene identification, which is obtained by inquiring a scene center system, and when the target log identification comprises the action identification, calling action log data corresponding to the action identification, which is obtained by inquiring a domain model system;
responding to the query request, querying log data corresponding to the target log identifier in the target system log, wherein the target system log comprises log data obtained by integrating first log data generated by the scene center system and second log data generated by the domain model system, the first log data comprises behavior record data after scene triggering of the scene center system, the second log data comprises action record data after action is executed by calling a domain model in the domain model system, the scene center system is used for calling at least one execution event in different scenes, the domain model system comprises a plurality of domain models, and the domain models are used for executing entity equipment of the at least one execution event;
And taking the log data corresponding to the target log identification as the target log, and displaying the target log on the user interface.
2. The method of claim 1, wherein the querying the target system log for log data corresponding to the target log identification comprises:
under the condition that the target log mark comprises a target scene mark, calling the scene center system, and inquiring target scene log data corresponding to the target scene mark in target scene log data of the target system log, wherein the target scene log data is used for representing a target scene of the scene center system;
under the condition that the target log mark also comprises a target scene trigger mark, invoking the scene center system, and inquiring target trigger log data corresponding to the target scene trigger mark in a scene trigger log, wherein the target trigger log data is used for representing triggering the target scene, and the scene trigger log comprises the first log data;
and under the condition that the target log identifier further comprises a target action identifier, calling the domain model system, and inquiring target model log data corresponding to the target action identifier in the target trigger log data, wherein the target model log data is used for representing calling a target domain model in the domain model system.
3. The method according to claim 1 or 2, wherein the querying the target system log for log data corresponding to the target log identification comprises:
and under the condition that the target log identifier comprises a target action identifier, invoking a chained tracking system, and querying target action log data corresponding to the target action identifier in the chained tracking log of the target system log, wherein the target action log data is used for indicating that a target domain model in the domain model system is invoked to execute a target action, and the chained tracking log comprises the second log data.
4. The method of claim 1, comprising, prior to the obtaining the query request triggered on the user interface:
and receiving a scene trigger log list of the scene center system, wherein the scene trigger log list comprises at least two log identifiers and log data corresponding to the at least two log identifiers, the log identifiers comprise the target log identifiers, and the log data comprise the target logs.
5. The method of claim 4, wherein the scene trigger log list comprises at least one of:
The system comprises at least two scene identifications and scene log data respectively corresponding to the at least two scene identifications, wherein the scene log data are used for representing scenes of the scene center system;
the system comprises at least two scene trigger identifiers and trigger log data respectively corresponding to the at least two scene trigger identifiers, wherein the trigger log data are used for representing scenes triggering the scene center system;
the system comprises at least two action identifiers and call log data respectively corresponding to the at least two action identifiers, wherein the call log data are used for representing calling of a domain model in the domain model system.
6. The method according to claim 1 or 4, comprising, prior to said obtaining a query request triggered on a user interface:
and receiving a chain tracking log list of the domain model system, wherein the chain tracking log list comprises at least two action identifiers and action log data respectively corresponding to the at least two action identifiers, and the action log data is used for representing calling a domain model in the domain model system to execute corresponding actions.
7. A log query device, comprising:
The device is used for pre-configuring a target system log, and comprises the following steps: presetting a scene identifier and an action identifier;
the system comprises an acquisition unit, a query unit and a storage unit, wherein the acquisition unit is used for acquiring a query request triggered on a user interface, the query request carries a target log identifier, the query request is used for requesting to query a target log corresponding to the target log identifier, and the target log comprises: when the target log identification comprises the scene identification, calling scene log data corresponding to the scene identification, which is obtained by inquiring a scene center system, and when the target log identification comprises the action identification, calling action log data corresponding to the action identification, which is obtained by inquiring a domain model system;
the response unit is used for responding to the query request, querying log data corresponding to the target log identifier in the target system log, wherein the target system log comprises log data obtained by integrating first log data generated by the scene center system and second log data generated by the domain model system, the first log data comprises behavior record data after scene triggering of the scene center system, the second log data comprises action record data after action is executed by calling a domain model in the domain model system, the scene center system is used for calling at least one execution event in different scenes, the domain model system comprises a plurality of domain models, and the domain models are used for executing entity equipment of the at least one execution event;
And the display unit is used for taking the log data corresponding to the target log identifier as the target log and displaying the target log on the user interface.
8. The apparatus of claim 7, wherein the response unit comprises:
the first query module is used for calling the scene center system under the condition that the target log identifier comprises the target scene identifier, and querying target scene log data corresponding to the target scene identifier in target scene log data of the target system log, wherein the target scene log data is used for representing a target scene of the scene center system;
the second query module is used for calling the scene center system under the condition that the target log identifier further comprises a target scene trigger identifier, and querying target trigger log data corresponding to the target scene trigger identifier in a scene trigger log, wherein the target trigger log data is used for representing triggering the target scene, and the scene trigger log comprises the first log data;
and the third query module is used for calling the domain model system under the condition that the target log identifier further comprises a target action identifier, and querying target model log data corresponding to the target action identifier in the target trigger log data, wherein the target model log data is used for representing calling a target domain model in the domain model system.
9. A computer readable storage medium, characterized in that the computer readable storage medium comprises a stored program, wherein the program when run performs the method of any of the preceding claims 1 to 6.
10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of the claims 1 to 6 by means of the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011296389.0A CN112416897B (en) | 2020-11-18 | 2020-11-18 | Log query method and device, storage medium and electronic device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011296389.0A CN112416897B (en) | 2020-11-18 | 2020-11-18 | Log query method and device, storage medium and electronic device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112416897A CN112416897A (en) | 2021-02-26 |
| CN112416897B true CN112416897B (en) | 2023-07-21 |
Family
ID=74774532
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011296389.0A Active CN112416897B (en) | 2020-11-18 | 2020-11-18 | Log query method and device, storage medium and electronic device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112416897B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108108285A (en) * | 2017-12-26 | 2018-06-01 | 广东欧珀移动通信有限公司 | Log processing method, device, storage medium and terminal device |
| CN110659349A (en) * | 2019-09-23 | 2020-01-07 | 深圳前海微众银行股份有限公司 | Log query method, device, equipment and computer readable storage medium |
| CN111352902A (en) * | 2020-02-28 | 2020-06-30 | 中国平安人寿保险股份有限公司 | Log processing method and device, terminal equipment and storage medium |
| CN111522922A (en) * | 2020-03-26 | 2020-08-11 | 浙江口碑网络技术有限公司 | Log information query method and device, storage medium and computer equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11740981B2 (en) * | 2018-12-19 | 2023-08-29 | Blackberry Limited | Method and apparatus for generating log data having increased filterability |
-
2020
- 2020-11-18 CN CN202011296389.0A patent/CN112416897B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108108285A (en) * | 2017-12-26 | 2018-06-01 | 广东欧珀移动通信有限公司 | Log processing method, device, storage medium and terminal device |
| CN110659349A (en) * | 2019-09-23 | 2020-01-07 | 深圳前海微众银行股份有限公司 | Log query method, device, equipment and computer readable storage medium |
| CN111352902A (en) * | 2020-02-28 | 2020-06-30 | 中国平安人寿保险股份有限公司 | Log processing method and device, terminal equipment and storage medium |
| CN111522922A (en) * | 2020-03-26 | 2020-08-11 | 浙江口碑网络技术有限公司 | Log information query method and device, storage medium and computer equipment |
Non-Patent Citations (1)
| Title |
|---|
| 分布式应用软件的日志分析***的设计与实现;李娟;《中国优秀博硕士学位论文全文数据库(硕士)信息科技辑（月刊）》;20200315(第03期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112416897A (en) | 2021-02-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107169094B (en) | Information aggregation method and device | |
| CN112073471B (en) | Control method and device of equipment, storage medium and electronic device | |
| CN110851364A (en) | Software testing method, system and related equipment | |
| CN106302448B (en) | Remote access control method and device | |
| EP3057281A1 (en) | M2m application remote registration method, device, system and storage medium | |
| CN114244644B (en) | Control method and device for intelligent home, storage medium and electronic device | |
| CN111045893B (en) | Method, device and system for executing monitoring task, storage medium and electronic device | |
| CN112104663B (en) | Method and equipment for managing login user and user equipment | |
| CN103885865A (en) | Method and device for managing sensors | |
| CN111353136B (en) | Method and device for processing operation request | |
| CN111371645B (en) | Method, system, computer equipment and storage medium for testing service connectivity | |
| CN113572669A (en) | Scene processing method and device, intelligent gateway and processor | |
| CN111813418A (en) | Distributed link tracking method, device, computer equipment and storage medium | |
| CN110198227B (en) | Log file processing method and device, storage medium and electronic device | |
| CN111209368A (en) | Information prompting method and device, computer readable storage medium and electronic device | |
| CN111897843B (en) | Configuration method and device of data flow strategy of Internet of things and computer equipment | |
| CN112416897B (en) | Log query method and device, storage medium and electronic device | |
| CN113094157A (en) | Generation method and device for calling topological graph, storage medium and electronic device | |
| CN110457202B (en) | TPC-E testing method for quickly establishing ODBC connection and driver equipment | |
| CN111767481B (en) | Access processing method, device, equipment and storage medium | |
| CN108647139B (en) | System test method, device, storage medium and electronic device | |
| US20130290245A1 (en) | Database history management method and system thereof | |
| CN113434190B (en) | Data processing method and device, storage medium and electronic equipment | |
| CN112751716B (en) | Test method and system for controlling response of file server and electronic equipment | |
| CN115499333A (en) | Method, system, storage medium and electronic device for determining association relationship |
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 |