Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Before describing the embodiment of the present invention, an application scenario of the embodiment of the present invention is described in an exemplary manner: in the prior art, if an abnormal service system is to be located from the service systems interacted with each other, a system responsible person of each service system needs to query in log information of each service system based on a query condition related to the abnormality, for example, query in log information of an order system based on an order number, query in log information of a distribution system based on a distribution number, and the like; furthermore, the system responsible person can determine whether the responsible business system has abnormality according to the query result. It should be noted that, even if the same query condition is applicable to at least two service systems, for example, the same order number is applicable to at least two service systems, it is also required to query in at least two service systems respectively according to the same query condition, and obviously, such abnormal positioning efficiency is relatively low. In addition, the service system can be a system for realizing a certain service function, such as an order system, a distribution system and the like; the system responsible person can be operation and maintenance personnel, development personnel, testing personnel and the like of the business system; the order number and the delivery number may be one of the service number, i.e. the service number may have different meanings in different service systems.
Correspondingly, the log processing method provided by the embodiment of the invention can be applied to a log processing system, the log processing system is in communication connection with a plurality of connected service systems, the connected service systems can be service systems which are connected with the log processing system and are used for realizing certain service functions, the log processing system comprises a log database, and log information of each connected service system is stored in the log database. In this way, the user only needs to query in the log processing system according to the query condition, specifically, query in each log information of the log database, so that the target log information matched with the query condition can be queried, the target log information can be derived from each connected service system, and the user can be an operator, a developer, a tester and the like of the log processing system. It should be noted that each piece of log information includes service system source information, which may indicate from which connected service system the log information originates. Therefore, after the user screens out the abnormal target log information from the target log information, the connected service system with the abnormality can be directly positioned according to the service system source information in the abnormal target log information. In other words, during abnormal positioning, the user can query the connected service system with abnormality through the unique entry of the log processing system without contacting the system responsible person of each connected service system one by one to query in each connected service system, thereby improving the abnormal positioning efficiency.
Example 1
Fig. 1 is a flowchart of a log processing method according to a first embodiment of the present invention. The present embodiment is applicable to a case where the log processing system is used as a unique entry to query out target log information matching the query condition. The method can be performed by the log processing device provided by the embodiment of the invention, the device can be realized by software and/or hardware, and the device can be integrated on a log processing system.
Referring to fig. 1, the method of the embodiment of the present invention specifically includes the following steps:
s110, when the positioning trigger event of abnormal positioning is monitored, acquiring the query condition corresponding to the positioning trigger event, and querying in a log database according to the query condition.
The location triggering event may be a user-triggered event for performing abnormal location, where the abnormality may be an abnormality discovered by a user and/or a customer, and the customer may be a user of a connected service system, such as a consignor of a logistics system, a purchaser of an order system, and so on. The log processing system, when acquiring the query condition input by the user through the front-end page, is an positioning trigger event for monitoring abnormal positioning, where the front-end page may be a page for inputting the query condition.
Further, a query condition corresponding to the positioning trigger event is obtained, where the query condition may be a keyword related to the anomaly, such as a time period, a service order number, and the like, and the service order number may be an order number, a delivery order number, and the like. Thus, since the log information of each connected service system connected thereto is stored in the log database of the log processing system, a query can be made in the log database according to the query condition.
And S120, screening target log information matched with the query condition from the log information according to the query result, and displaying the target log information.
When inquiring in the log database according to the inquiry condition, the target log information matched with the inquiry condition can be screened out from the log information, wherein the target log information can be the log information directly related to the abnormality, the log information can contain the abnormality information, and the abnormality information can show the specific abnormal condition; alternatively, the target log information may be log information indirectly associated with an anomaly, for example, a certain service chain includes a plurality of service links, and the target log information may be log information on a service chain with an anomaly, but is not log information on a link with an anomaly on the service chain, and such log information does not include anomaly information; etc. Further, the target log information is displayed, and each item of target log information comprises service system source information, so that a user can determine which connected service system the item of target log information originates from according to the service system source information in the displayed target log information, and the connected service system with the abnormality can be rapidly positioned according to each item of target log information.
On the basis, optionally, some target log information comprises abnormal information, and some target log information does not comprise abnormal information, for example, taking four links of pre-sorting verification, client information verification, site information collection verification and single inventory verification in the single service chain as examples, and assuming that an interface of the pre-sorting verification is requested to be called, the return result of the interface is normal, namely the log information corresponding to the current request calling process does not comprise abnormal information; the interface of the client information verification is called by a request, and the returned result of the interface is abnormal, namely the log information corresponding to the calling process of the request contains abnormal information, such as error stack information. When the target log information is displayed, the target log information including the abnormal information and the target log information not including the abnormal information can be distinguished based on different display effects, for example, the target log information including the abnormal information is marked with a red background color and the target log information not including the abnormal information is marked with a green background color, so that a user can be helped to quickly locate the target log information including the abnormal information from a large number of target log information, and further quickly locate the connected service system including the abnormal information according to the service system source information in the target log information including the abnormal information. Still alternatively, each piece of log information may further include a service system contact, where the service system contact may be a system responsible person of the connected service system corresponding to the service system source information. Thus, after locating the abnormal connected service system, the user can inform the service system contact person of the connected service system to correspondingly adjust and optimize the connected service system, and the like. Illustratively, the display effect of the target log information is as shown in fig. 2, and the target log information containing the abnormality information is marked with a gray background.
According to the technical scheme provided by the embodiment of the invention, when the log processing system acquires the query condition related to abnormal positioning, the log processing system can query in a log database according to the query condition, and the log database is a database in the log processing system; because the log information of each connected service system is stored in the log database, that is, the log information in the log database originates from each connected service system, the target log information which is screened from each log information according to the query result and matches with the query condition can originate from each connected service system, and the target log information comprises service system source information, after the target log information is displayed, the user can locate the connected service system with abnormality according to the displayed target log information. According to the technical scheme, the target log information related to the query condition is queried through the unique entry provided by the log processing system, so that a user can position the abnormal connected service system according to the service system source information in the target log information, and the effect of quickly positioning the abnormal connected service system is achieved.
Based on this, an optional technical scheme, the number of the target log information is at least two, and the target log information is displayed, which specifically may include: acquiring request single numbers associated with each target log information, wherein the request single numbers are generated when interfaces in a connected service system are requested to be called; and displaying the target log information in groups according to the request list number. An interface is an interface that can implement a certain function, and may also be understood as a service, a method, a function, and the like. When the interface is requested to be called, a corresponding request single number is generated, wherein the request single number is mainly used for connecting links called by the interface request in series, and the format of the request single number can be a time string and a multi-bit random number. Therefore, when at least two target log information are displayed, the request list number associated with each target log information can be acquired, and the target log information associated with the same request list number can be displayed as a group.
It should be noted that, when an interface is requested to be called, a request unit number is generated, but the interface may include multiple sub-interfaces, where the request call of the interface means that multiple sub-interfaces in the interface are sequentially called, and the calling process of these sub-interfaces will not generate new request unit numbers, which is just the meaning that one request unit number can connect the links of the interface request call in series. However, the invocation of these subinterfaces still generates log information, meaning that the number of target log information associated with the same request ticket may be one, two, or more.
In order to better understand the specific implementation procedure of the above steps, an exemplary description is given below of the log processing method of the present embodiment in conjunction with a specific example. As shown in fig. 3, the front-end page of the query machine in the log processing system provides an input box of a service number or a request number, which can be selected through a drop-down menu, where a service number of a certain service is taken as an example, after the service number input by a user in the input box is acquired, the query is performed in an Hbase cluster according to the service number, where the Hbase cluster is a cluster formed by a plurality of hbases, and log information of each connected service system is stored. Further, target log information related to the ordered service may be determined based on the query results, and the target log information may originate from different connected service systems. It should be noted that, a plurality of request single numbers may be related to one service single number, and the following single service and the modification service respectively correspond to two request single numbers under one service single number, so that each target log information belonging to the same request single number can be displayed under the same tab, so as to display the complete link called by the request. Of course, one, two or more interfaces may be involved in a link of a service chain and called by a request, i.e. the log information in a link may be associated with one, two or more request numbers, which is not specifically limited herein.
Example two
Fig. 4 is a flowchart of a log processing method according to a second embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, the log processing system may include an information sending client, and the connected service system may store the log information in the log database by: when a calling trigger event called by an interface is monitored, acquiring log information corresponding to the calling trigger event, and storing the log information in a context; when the interface call is finished, the log information in the context is sent to the information sending client, so that the log information is stored in the log database through the information sending client, and the log information in the context is deleted; the log information may include parameter information, or parameter information and anomaly information, where the parameter information includes a parameter in and a parameter out. Wherein, the explanation of the same or corresponding terms as the above embodiments is not repeated herein.
Referring to fig. 4, the method of this embodiment may specifically include the following steps:
s210, when a calling trigger event called by an interface is monitored, acquiring log information corresponding to the calling trigger event, and storing the log information in a context, wherein the log information comprises parameter information or parameter information and abnormal information, and the parameter information comprises parameter entering parameters and parameter exiting parameters.
The call triggering event may be an event triggered when a certain interface in a certain connected service system is called, for example, after the connected service system related to the service is monitored that the down button is clicked, the connected service system may call an interface of the pre-sorting check, and at this time, the connected service system may monitor the call triggering event of the interface call. Further, when the interface is called, the connected service system can acquire log information generated in the calling process of the interface, and store the log information in the context. It should be noted that, the parameter in and parameter out may be involved in the interface calling process, and these parameter information is a part of the log information. In addition, when an interface call is abnormal, abnormal information may also appear, and the abnormal information may be a part of log information.
And S220, when the interface call is finished, the log information in the context is sent to the information sending client so as to be stored into the log database through the information sending client, and the log information in the context is deleted.
When the interface call is finished, all log information related to the interface call is stored in the context, at the moment, the log information stored in the context can be sent to the information sending client side, so that the log information is stored in the log database through the information sending client side, and the log information in the context can be deleted after the log information is sent out.
In practical applications, with respect to the log writing logic executed by the connected service system, for example, the log processing system may encapsulate the processing logic related to log writing into a jar packet, so that the connected service system executes a corresponding log writing function by introducing the jar packet, where the log writing function may be implemented by means of annotation, API call, and the like, and the specific implementation logic of the log writing logic and the log writing logic are substantially consistent. By way of example, when the connected service system monitors a call trigger event, the connected service system can acquire corresponding parameter entering and parameter exiting based on the tangent plane technology, and of course, when call abnormality exists, abnormal information can also be acquired, and the information is stored in a context through the ThreadLocal technology, wherein the information is part of log information. It should be noted that, a certain interface may implement a corresponding function based on sequential calls of multiple sub-interfaces in the interface, and information such as parameter in, parameter out, exception information and the like in the calling process of these sub-interfaces may also be stored in a context, and they may be stored in a stack manner. At this time, after the interface call is finished, the information in the stack is returned layer by layer, and the returned information can be sent to a consumption end through the MQ client, and then is consumed into the Hbase cluster through the consumption end. Of course, after the information is sent out, the information in the context may be deleted.
S230, when the positioning trigger event of abnormal positioning is monitored, acquiring the query condition corresponding to the positioning trigger event, and querying in the log database according to the query condition.
S240, screening target log information matched with the query condition from the log information according to the query result, and displaying the target log information.
On this basis, as shown in fig. 5, for example, log information of each connected service system (such as star system, many mail order system and order center system) may be sent to an Hbase cluster through an MQ cluster, and a query machine may query the Hbase cluster for target log information matched with the query condition.
According to the technical scheme, when the connected service system monitors the calling trigger event of the interface call, log information corresponding to the calling trigger event can be stored in the context; and when the interface call is finished, the log information stored in the context can be sent to the information sending client side so as to be stored into the log database through the information sending client side, and the log information in the context is deleted after the log information is sent, so that the effect of writing the log information in the connected service system into the log processing system is realized.
In practical application, when the log writing function is implemented based on the annotation mode, some parameters may be swallowed due to an abnormality of the connected service system, for example, the displayed abnormality prompt is not displayed, the output parameter is not output, and the parameters may be referred to as abnormality parameters, where the annotation in the annotation mode cannot acquire the abnormality parameters. Therefore, the log processing method may further include: when an abnormal triggering event with abnormal parameters is monitored, acquiring abnormal parameters and a parameter setting interface corresponding to the abnormal triggering event, and calling the parameter setting interface to set the abnormal parameters; and determining the abnormal information corresponding to the abnormal parameters, and storing the abnormal parameters and the abnormal information in the context. That is, log information in the context is manipulated through a parameter setting interface provided inside the interface, thereby re-acquiring or resetting the engulfed abnormal parameters, and further storing the abnormal information corresponding to the abnormal parameters and the abnormal parameters in the context, and optionally, the parameter setting interface may be an API interface.
Example III
Fig. 6 is a flowchart of a log processing method provided in the third embodiment of the present invention. The present embodiment is optimized based on the above technical solutions. In this embodiment, optionally, the log processing method may further include: when a connection trigger event of service system connection is monitored, acquiring a log type to be connected of a service system to be connected corresponding to the connection trigger event, wherein the log type to be connected can comprise a service type, an operation type and service system source information; and if the log type to be connected is inconsistent with the log type connected with the connected service system, allowing the service system to be connected to the log processing system. Wherein, the explanation of the same or corresponding terms as the above embodiments is not repeated herein.
Referring to fig. 6, the method of this embodiment may specifically include the following steps:
s310, when a connection trigger event of the service system connection is monitored, acquiring a log type to be connected of the service system to be connected corresponding to the connection trigger event, wherein the log type to be connected comprises a service type, an operation type and service system source information.
The connection triggering event monitored by the log processing system may be an event triggered after the user inputs a log type to be connected for connection through a front end page, where the log type to be connected includes a type of log information of a service system to be connected, which is set by the user according to an actual situation, and the service system to be connected is a service system that is not yet connected to the log processing system. Therefore, when the connection trigger event of the service system connection is monitored, the log type to be connected of the service system to be connected corresponding to the connection trigger event can be obtained, where the log type to be connected can include the service type, the operation type and the source information of the service system, and also can include the service system contact person and the like, and is not limited specifically herein. In other words, the user may apply for its log type to be connected to the log processing system for configuration of the user's required log type before connecting to the log processing system. If the service system to be connected is an order system, the source information of the service system can be an order system, the service type can be an order placing service, and the operation type can be a link in the order placing service, such as pre-sorting verification, client information verification, site information verification of a dispatch, inventory verification of the order, and the like.
S320, if the log type to be connected is inconsistent with the log type connected with the connected service system, allowing the service system to be connected to the log processing system.
The connected log type may be a type of log information of a connected service system connected to the log processing system, and similar to a log type to be connected, the connected log type may include a service type, an operation type, service system source information, a service system contact person, and the like, which is not specifically limited herein. The connected log type of each connected service system has uniqueness, so that the log type to be connected can be compared with each connected log type, if the log type to be connected does not conflict with each connected log type, the log processing system can allow the connected service system to be connected to the log processing system, and the log type to be connected of the connected service system can be returned to the connected service system. Of course, when there is a conflict, a corresponding prompt message may be returned to prompt the user to modify the log type to be connected of the service system to be connected, so that the service system to be connected is successfully connected to the log processing system.
S330, when the positioning trigger event of abnormal positioning is monitored, acquiring the query condition corresponding to the positioning trigger event, and querying in the log database according to the query condition.
S340, screening target log information matched with the query condition from the log information according to the query result, and displaying the target log information.
The connected log types can be embodied in the log information of the connected service system, so that the target log information matched according to the query condition can contain service system source information, service types and operation types, which is helpful for a user to know which operation type under which service type under which connected service system belongs to from the target log information, and the efficiency of subsequent abnormal positioning is improved. Particularly, the setting of the connected log type realizes the effective and unified effect of the log information in the distributed scene in the multi-dimension according to the source information of the service system, the service type and the operation type.
According to the technical scheme provided by the embodiment of the invention, the log processing system allows the to-be-connected service system to be connected to the log processing system under the condition that the to-be-connected service system and the connected log type of the connected service system have no conflict by comparing the to-be-connected log type of the to-be-connected service system corresponding to the connection triggering event, so that the effect of effectively connecting the to-be-connected service system and the log processing system is realized.
An optional technical scheme is that when a configuration trigger event of life cycle configuration is monitored, each connected log type corresponding to the configuration trigger event is used as a life cycle; correspondingly, displaying the target log information may specifically include: determining a target life cycle associated with the target log information from the life cycles; if the missing type which belongs to the target life cycle and is not contained in each connected log type of the target log information exists, the target log information and the missing type are displayed.
The configuration triggering event may be an event triggered by the user after the front end page inputs the connected log type for configuration, and the number of connected log types input by the user on the front end page may be one, two or more, i.e. at least one connected log type may be used as a life cycle. If the connected log types input by the user include order system, order placing service and pre-sorting verification, order system, order placing service and customer information verification, order system, order placing service and dispatching site information, and order system, order placing service and order placing inventory verification, four links in the order placing service can be used as a life cycle.
The target life cycle associated with the target log information can be determined from the configured life cycles, specifically, the connected log type of each connected service system connected to the log processing system has uniqueness, and the connected log type can be contained in the log information of the connected service system, namely, the connected log type is contained in the target log information, and on the basis, the life cycle is configured according to the connected log type, so that the target life cycle associated with the target log information can be determined from the life cycles according to the connected log type contained in the target log information and the connected log type corresponding to each life cycle. For example, the connected log types for each entry marking log information include log type 1, log type 3, and log type 4, and a lifecycle is configured according to log type 1, log type 2, log type 3, and log type 4, meaning that the lifecycle is a target lifecycle associated with each target log information.
Further, the connected log types in the target life cycle are compared with the connected log types contained in the target log information, and if a connected log type belongs to the connected log types in the target life cycle and is not contained in the target log information, the connected log types can be called as a missing type, and the target log information and the missing type are displayed. Illustratively, log type 2 in the above example is the miss type. In order to better understand the application effect of the life cycle, taking 4 links in the above-mentioned order service as an example, as shown in fig. 3, if the log type 1 is an order system, an order service and a pre-sorting check, the log type 2 is an order system, an order service and a client information check, the log type 3 is an order system, an order service and a dispatch site information, and the log type 4 is an order system, an order service and a face inventory check, when displaying, the corresponding target life cycle matched according to the connected log type of the target log information can be displayed, and because the log type 2 is a missing type, the client information check in the log type 2 can be thickened and displayed, which is helpful for a user to quickly confirm whether a missing link exists in the target life cycle, that is, whether one link is missing in the order service, thereby further improving the abnormal positioning efficiency.
An alternative solution, since there may be multiple invokers in a certain interface, the invoker may be a certain interface in a certain connected service system, for example, the invoker of interface a is interface B in service system 1 and interface C in service system 2, and the prior art simply monitors the invocation procedure of interface a for anomalies, which has a low degree of distinction, because it cannot distinguish the invocation procedure of interface a for a specific connected service system (such as service system 1, service system 2) and a specific interface (such as interface B, interface C), which is detrimental to the subsequent anomaly analysis of the user.
In order to solve the above problem, the log processing method may further include: acquiring a preset number threshold matched with a target log type in each connected log type; and if the number of the log information which belongs to the target log type and is prestored in the log database in the first preset time range is larger than a preset number threshold value, sending out alarm information. The target log type may be a preset log type with an abnormal monitoring requirement, and the corresponding preset number threshold value is obtained, and the preset number threshold value is a preset certain value; when the number of the log information which belongs to the target log type and is prestored in the log database in the first preset time range is larger than a preset number threshold, namely when the calling times of interfaces corresponding to the target log type in the first preset time range are larger than the preset number threshold, abnormal calling conditions possibly exist, and alarm information can be sent. That is, the above solution can be understood as an early warning mechanism of multiple operations of a normal service flow, and when the normal service flow is operated for multiple times, a potential threat may be formed to a connected service system, so that, to avoid this situation, the log processing system may monitor the operating frequency in multiple dimensions according to source information, service type and operation type of the service system, and give an alarm when an abnormality occurs. For example, taking an interface call of order status return as an example, alarm information is sent when the return number of times is more than 2 in one minute.
In addition, in the context of anomaly monitoring, the log processing system may also determine the normal number and the abnormal number for each connected log type based on statistical analysis within a second preset time range, which may be daily, hourly, every minute, and so forth. In this way, if the number of exceptions corresponding to a certain connected log type is suddenly increased, an alarm message can be sent out. In addition, the log processing system can also perform exception display according to different dimensions of source information of the service system, service types, operation types and the like, and can also provide an exception curve analysis function and the like on different time dimensions, which are not particularly limited herein.
Example IV
Fig. 7 is a block diagram of a log processing device according to a fourth embodiment of the present invention, where the log processing device is configured to execute the log processing method according to any of the foregoing embodiments. The device and the log processing method of each embodiment belong to the same invention conception, and the details of the log processing device, which are not described in detail in the embodiment of the log processing device, can be referred to the embodiment of the log processing method. Referring to fig. 7, the apparatus is configured in a log processing system, where the log processing system is connected to a plurality of connected service systems, log information of each connected service system is stored in a log database of the log processing system, and the log information includes service system source information, and the apparatus specifically may include: a log query module 410 and a log display module 420.
The log query module 410 is configured to obtain a query condition corresponding to a positioning trigger event when the positioning trigger event of abnormal positioning is detected, and query in a log database according to the query condition;
the log display module 420 is configured to screen target log information matching the query condition from the log information according to the query result, and display the target log information.
Optionally, on this basis, the apparatus may further include:
the log type acquisition module is used for acquiring a log type to be connected of a service system to be connected corresponding to a connection trigger event when the connection trigger event of the service system connection is monitored, wherein the log type to be connected comprises a service type, an operation type and service system source information;
and the service system connection module is used for allowing the service system to be connected to the log processing system if the log type to be connected is inconsistent with the connected log type of the connected service system.
Optionally, on this basis, the apparatus may further include:
the life cycle configuration module is used for taking each connected log type corresponding to the configuration triggering event as a life cycle when the configuration triggering event of the life cycle configuration is monitored;
Correspondingly, the log display module 420 may specifically include:
the target life cycle screening unit is used for determining a target life cycle associated with the target log information from each life cycle;
and the deletion type display unit is used for displaying the target log information and the deletion types if the deletion types which are affiliated to the target life cycle and are not contained in the connected log types of the target log information exist.
Optionally, on this basis, the apparatus may further include:
the threshold value acquisition module is used for acquiring a preset number of threshold values matched with the target log types in the connected log types; the alarm module is used for sending out alarm information if the number of the log information which belongs to the target log type and is prestored in the log database in the first preset time range is larger than a preset number threshold value.
Optionally, the number of the target log information is at least two, and based on this, the log display module 420 may specifically include:
the request single number acquisition unit is used for acquiring request single numbers associated with each target log information, wherein the request single numbers are generated when interfaces in the connected service system are requested to be called;
and the log display unit is used for displaying the target log information in groups according to the request single number.
Optionally, the log processing system includes an information sending client, and the log information is stored in a log database through the following modules:
the first storage module is used for acquiring log information corresponding to a calling trigger event when the calling trigger event called by the interface is monitored, and storing the log information in a context, wherein the log information comprises parameter information or parameter information and abnormal information, and the parameter information comprises parameter entering parameters and parameter exiting parameters;
and the second storage module is used for sending the log information in the context to the information sending client when the interface call is finished, so that the log information is stored in the log database through the information sending client, and the log information in the context is deleted.
Optionally, on this basis, the apparatus may further include:
the abnormal setting module is used for acquiring abnormal parameters and parameter setting interfaces corresponding to the abnormal triggering events when the abnormal triggering events of the parameter anomalies are monitored, and calling the parameter setting interfaces to set the abnormal parameters;
and the third storage module is used for determining the abnormal information corresponding to the abnormal parameters and storing the abnormal parameters and the abnormal information in the context.
According to the log processing device provided by the fourth embodiment of the invention, when the query condition related to abnormal positioning is obtained through the log query module, the query can be performed in the log database according to the query condition, and the log database is a database in a log processing system; because the log information of each connected service system is stored in the log database, that is, the log information in the log database is derived from each connected service system, the target log information which is screened from each log information according to the query result and matched with the query condition by the log display module can also be derived from each connected service system, and in consideration of the fact that the target log information comprises service system source information, after the target log information is displayed, a user can locate the connected service system with abnormality according to the displayed target log information. According to the device, the target log information related to the query condition is queried through the unique entry provided by the log processing system, so that a user can position the abnormal connected service system according to the service system source information in the target log information, and the effect of quickly positioning the abnormal connected service system is achieved.
The log processing device provided by the embodiment of the invention can execute the log processing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
It should be noted that, in the above embodiment of the log processing apparatus, each unit and module included are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the present invention.
Example five
Fig. 8 is a schematic structural diagram of a log processing system according to a fifth embodiment of the present invention, and as shown in fig. 8, the log processing system includes a memory 510, a processor 520, an input device 530 and an output device 540. The number of processors 520 in the log processing system may be one or more, one processor 520 being taken as an example in fig. 8; the memory 510, processor 520, input device 530, and output device 540 in the log processing system may be connected by a bus or other means, as exemplified by connection via bus 550 in fig. 8.
The memory 510 is a computer readable storage medium, and may be used to store software programs, computer executable programs, and modules, such as program instructions/modules corresponding to the log processing method in the embodiment of the present invention (for example, the log query module 410 and the log display module 420 in the log processing device). The processor 520 executes various functional applications of the log processing system and data processing by executing software programs, instructions, and modules stored in the memory 510, i.e., implements the log processing method described above.
The memory 510 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, at least one application program required for functions; the storage data area may store data created from the use of the log processing system, and the like. In addition, memory 510 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, memory 510 may further include memory located remotely from processor 520, which may be connected to the device 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 input device 530 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the device. The output 540 may include a display device such as a display screen.
Example six
A sixth embodiment of the present invention provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a log processing method, where the method is applied to a log processing system, the log processing system being connectable to a plurality of connected service systems, log information of each connected service system being stored in a log database of the log processing system, the log information including service system source information, the method may include:
When a positioning trigger event of abnormal positioning is monitored, acquiring a query condition corresponding to the positioning trigger event, and querying in a log database according to the query condition;
and screening target log information matched with the query condition from the log information according to the query result, and displaying the target log information.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present invention is not limited to the method operations described above, and may also perform the related operations in the log processing method provided in any embodiment of the present invention.
From the above description of embodiments, it will be clear to a person skilled in the art that the present invention may be implemented by means of software and necessary general purpose hardware, but of course also by means of hardware, although in many cases the former is a preferred embodiment. In light of such understanding, the technical solution of the present invention may be embodied essentially or in part in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, read-Only Memory (ROM), random-access Memory (Random Access Memory, RAM), FLASH Memory (FLASH), hard disk, optical disk, etc., of a computer, which may be a personal computer, a server, a network device, etc., and which includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the methods described in the embodiments of the present invention.
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.