Method for managing log information and electronic apparatus thereof

Abstract

This invention discloses a log information management method implemented in an electronic device, comprising the following steps: generating outline information related to the outline of a first object provided to a user device; receiving first log information generated from the first server based on the outline information in response to a first event related to the first object on the first server; and generating monitoring information related to the first event based on the first log information.

Description

Technical Field

[0001] The present invention relates to an electronic device and a method for managing log information, and more specifically, to an electronic device and a method for managing logs based on schema information associated with an object. Prior Art

[0002] With the development of electronic technology, e-commerce has taken a place in the shopping field. Customers can buy items online without having to go to shopping malls, markets or stores in person, and the items purchased online will be delivered to the delivery location requested by the customer.

[0003] For e-commerce, providing detailed and accurate information about products has a significant impact on service satisfaction, so various solutions for providing more detailed and accurate information are being discussed.

[0004] On the other hand, as shopping through e-commerce becomes more popular, the amount of data that needs to be processed in the servers providing e-commerce services is becoming increasingly large, so there is an increasing need to propose efficient methods for managing information related to various e-commerce services.

[0005] For related content, please refer to previous literature such as KR101756594B1 or KR101500849B1. Summary of the invention

[0006] [Problems that the invention aims to solve] According to the method of the present invention, the electronic device can obtain log information corresponding to events associated with visual objects and manage the obtained log information.

[0007] According to the method of the present invention, the electronic device can confirm whether the events related to the object are normally provided to the user based on the log information.

[0008] According to the method of the present invention, the electronic device can generate monitoring information based on log information to implement monitoring of events associated with the object.

[0009] The technical issues to be solved by the present invention are not limited to the technical issues mentioned above. Those with common knowledge in the technical field to which the present invention belongs can clearly understand other technical issues not mentioned based on the following description. [Technical means to solve the problem]

[0010] Various embodiments may provide a method for managing log information and an electronic device supporting the same.

[0011] The various embodiments of the log information management method implemented in an electronic device disclosed in this document may include the following steps: generating schema information related to the schema of the first object provided to the user device; corresponding to the first event related to the above-mentioned first object of the first server, receiving the first log information generated based on the above-mentioned schema information from the above-mentioned first server; and generating monitoring information related to the above-mentioned first event based on the above-mentioned first log information.

[0012] Furthermore, the above-mentioned outline information may at least include the identification information of the above-mentioned outline, including the name information of the above-mentioned outline, the name information of the above-mentioned first event, the category information of the above-mentioned first event, the type information of the above-mentioned first event, the domain information of the above-mentioned first object, the page information of the above-mentioned first object and at least a part of the version information of the above-mentioned outline.

[0013] Furthermore, the first log information may be generated in the second server based on the schema information, and the second server provides the execution data related to the first object including the first log information to the second server based on the request related to the first event received from the first server.

[0014] Furthermore, the first server may provide the user device with events related to the first object based on the execution data related to the first object, and transmit the first log information included in the execution data related to the first object back to the electronic device.

[0015] Furthermore, the step of generating the above-mentioned monitoring information may further include the following steps: generating monitoring setting information including identification information of the schema of the above-mentioned first object; based on the schema information, obtaining the first log information associated with the above-mentioned first object from the log information received from the above-mentioned first server, and the schema information is confirmed based on the above-mentioned monitoring setting information; based on the collected first log information, generating monitoring information of the above-mentioned first event.

[0016] Furthermore, the monitoring setting information includes identification information of a schema corresponding to the at least one object and information of at least one parameter related to the first event confirmed based on the schema information; the step of generating the monitoring information may further include the following steps: classifying the first log information based on the parameters; and generating the monitoring information based on the classification.

[0017] Furthermore, the monitoring information may include numerical information related to the first log information, and the first log information corresponds to the first event; the log information management method further includes the following steps: based on the numerical information, providing a notification message to one or more operator devices corresponding to the electronic device.

[0018] In addition, the above-mentioned log information management method may further include the following steps: based on the threshold value information, providing a notification message to one or more operator devices corresponding to the above-mentioned electronic device, and the threshold value information is confirmed corresponding to the above-mentioned monitoring information and the historical information related to the above-mentioned first log information.

[0019] Furthermore, the log information management method may further include the following steps: corresponding to the first event, receiving the second log information from the first server, the second log information being generated based on information related to the user device requesting the first event and the first event; and generating monitoring information related to the first event based on the first log information and the second log information.

[0020] Furthermore, the above information may include at least a portion of the IP (Internet Protocol) information of the above user device, the identification information of the above user device, the platform information of the above user device and the identification information related to the above first event.

[0021] Furthermore, the step of generating the above-mentioned monitoring information may further include the following steps: based on the above-mentioned outline information, confirming whether the received above-mentioned first log information is valid; and based on the above-mentioned validity, generating the above-mentioned monitoring information.

[0022] Furthermore, the above-mentioned outline information may further include information related to the valid value of the log, and the above-mentioned step of confirming whether it is valid further includes the following steps: based on the above-mentioned first log information, confirm the identification information of the outline; compare the information related to the valid value with the above-mentioned first log information, and the valid value is confirmed corresponding to the confirmed identification information of the above-mentioned outline.

[0023] Furthermore, the first object may include a graphical user interface (GUI) object, and the first event may include a display event related to the display of the first object, or a click event related to the user's input, and the user's input corresponds to the first object.

[0024] The electronic device of various embodiments disclosed in this document may include a transceiver, a storage and a processor, and the processor is configured as follows: generating schema information related to the schema of the first object provided to the user device, corresponding to the first event related to the first object of the first server, receiving the first log information generated based on the schema information from the first server, and generating monitoring information related to the first event based on the first log information. [Effects of the Invention]

[0025] According to the method of the present invention, the electronic device can manage schema information including information associated with an object, thereby systematically generating and managing log information related to events of the object.

[0026] The electronic device 101 can confirm that the log information is accumulated normally to generate monitoring information, and confirm that the events of the user object that becomes the monitoring object are provided to the user normally.

[0027] According to the method of the present invention, the electronic device can generate monitoring information based on log information related to the event of the object, thereby effectively monitoring the object-related events provided to the user.

[0028] According to the method of the present invention, the electronic device can generate monitoring setting information based on the category information to efficiently manage the object events to be monitored.

[0029] The effects of the present invention are not limited to the effects mentioned above, and a person skilled in the art can clearly understand other effects not mentioned according to the description of the patent application scope. Simple diagram description

[0030] FIG. 1 is a diagram of a log information management system for illustrating a method for managing log information implemented by an electronic device according to various embodiments. FIG. 2 is a diagram showing the configuration of an electronic device, a first server, a second server, an operator device, and a user device according to various embodiments. FIG. 3 is a flowchart of the operation of managing log information of an electronic device according to various embodiments. FIG. 4 is a diagram showing the first page of the electronic device for managing category information in various embodiments. FIG. 5 is a diagram showing schematic information of various embodiments by way of example. FIG. 6 is an example of additional schema information in various embodiments. FIG. 7 is a diagram for illustrating object-related events according to various embodiments. FIG. 8 is an illustrative diagram of log information according to various embodiments. FIG. 9 is a diagram showing a second page for managing monitoring information according to various embodiments. FIG. 10 is a diagram showing the third page for generating monitoring setting information according to various embodiments. FIG. 11 is a diagram for illustrating monitoring information of various embodiments. FIG. 12 is a diagram showing a dashboard page displaying monitoring information according to various embodiments. FIG. 13 is a diagram showing a user interface for operators to set a dashboard page according to various embodiments. FIG. 14 is a diagram showing a user interface for setting conditions for a dashboard page according to various embodiments. FIG. 15 is a flowchart showing the operation of generating monitoring information by an electronic device in various embodiments. FIG. 16 is a flowchart of an electronic device according to various embodiments that generates monitoring information based on log information. Implementation

[0031] The following embodiments are those that combine the components and features of various embodiments into specific forms. Unless otherwise explicitly stated, each component or feature can be considered optional. Each component or feature can be implemented in a form that is not combined with other components or features. In addition, some components and features can be combined to form various embodiments. The order of actions described in various embodiments can be changed. Some components or features of an embodiment can be included in other embodiments, or can be interchanged with corresponding components or features of other embodiments.

[0032] In the description of the drawings, no procedures or steps are described that would confuse the main points of the various embodiments, nor are any procedures or steps described that are understandable to a person having common sense in the technical field.

[0033] When it is mentioned throughout the specification that a certain part "comprising or including" a certain constituent element, it means that other constituent elements are not excluded unless otherwise stated, but other constituent elements may be further included. In addition, the terms "...part", "...device", "module" and the like recorded in the specification refer to a unit that processes at least one function or action, which can be implemented by hardware, software, or a combination of hardware and software. In addition, in the text describing various embodiments (especially, in the scope of the following invention application), unless otherwise indicated in this specification or explicitly refuted in the text, "a (or an)", "one (one)", "the (the)" and similar related words can be used in the meaning of including both the single and the plural.

[0034] Hereinafter, with reference to the accompanying drawings, the preferred implementations of various embodiments are described in detail. The detailed description disclosed below together with the accompanying drawings is for illustrating exemplary implementations of various embodiments, and is not intended to represent the only implementation.

[0035] Furthermore, the specific terms used in the various embodiments are provided to help understand the various embodiments, and the use of such specific terms may be changed to other forms without departing from the technical ideas of the various embodiments.

[0036] At this point, it should be understood that the combination of each block of the processing flow chart and the flow chart can be implemented by computer program instructions. Such computer program instructions can be loaded on a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the instructions executed by the processor of the computer or other programmable data processing device will produce a method for implementing the functions described in the blocks of the flow chart. In order to achieve the functions in a specific manner, such computer program instructions can be stored in a computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing device, so that the instructions stored in the computer-usable or computer-readable memory can also produce an article of manufacture containing the following instruction method, which implements the functions described in the blocks of the flow chart. Computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of action steps are executed on the computer or other programmable data processing device to produce a process executed by the computer, so that the instructions executed by the computer or other programmable data processing device can also provide steps for performing the functions described in the blocks of the flow chart.

[0037] In addition, each block may represent a module, a segment or a portion of code including one or more executable instructions for performing a specific logical function. In addition, it should be noted that in some alternative embodiments, the functions mentioned in the blocks may not be performed in order. For example, two blocks shown in succession may be executed substantially at the same time, or may occasionally be executed in the opposite order according to the corresponding functions.

[0038] FIG. 1 is a diagram of a log information management system 100 for illustrating a method for managing log information implemented by an electronic device according to various embodiments.

[0039] 1 , the log information management system 100 of various embodiments can be implemented in various types of devices. For example, the log information management system 100 can be implemented in an electronic device 101, a first server 102, a second server 103, an operator device 104, and a user device 105. In other words, the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 can perform the actions of various embodiments of the present invention based on the log information management system 100 implemented in each device. On the other hand, the log information management system 100 of various embodiments can also be implemented in various electronic devices and servers, and is not limited to the above-mentioned FIG. 1 .

[0040] The electronic device 101 of various embodiments may be a device that performs wired and wireless communication with the first server 102, the second server 103, and one or more operator devices 104, and includes a storage device with a large storage capacity. For example, the electronic device 101 may be a cloud device connected to one or more operator devices 104.

[0041] The first server 102 of various embodiments may be a device that performs wired and wireless communication with the electronic device 101, the second server 103, one or more operator devices 104, and one or more user devices 105, and includes a storage device with a large unit of storage capacity. For example, the first server 102 may be a cloud device connected to one or more user devices 105. In an embodiment, the first server 102 may be a front-end server that receives a request associated with an event of a user object from the user device 105 and transmits it to the second server 103, and receives execution data from the second server 103 based on the request, and provides the user device 105 with events associated with the user object based on the execution data. Events associated with the user object may include events associated with a user interface object, and the user interface object constitutes at least a part of an application or website (e.g., a web application) for providing services to the user device 105.

[0042] The second server 103 of various embodiments may be a device that performs wired and wireless communication with the electronic device 101, the first server 102, and one or more operator devices 104, and includes a storage device with a large unit of storage capacity. For example, the second server 103 may be a cloud device connected to one or more operator devices 104. In an embodiment, the second server 103 may be a back-end server that provides the first server 102 with execution data corresponding to a request associated with an event of a user object received from the first server.

[0043] The operator device 104 of various embodiments may be a device available to individual users, such as a desktop computer, a tablet computer, a mobile terminal, etc. In addition, other electronic devices that perform similar functions may be used as the operator device 104.

[0044] The user device 105 of various embodiments can be a device available to individual users, such as a desktop computer, a tablet computer, a mobile terminal, etc. In addition, other electronic devices that perform similar functions can be used as the user device 105.

[0045] The log information management system 100 of various embodiments may include various modules for actions. The modules included in the log information management system 100 may be computer codes or one or more instructions implemented in a manner that enables a physical device (e.g., electronic device 101) that implements the log information management system 100 (or included in the physical device) to perform a specified action. In other words, the physical device that implements the log information management system 100 stores a plurality of modules in the form of computer codes in a memory, and when executing the plurality of modules stored in the memory, the plurality of modules can enable the physical device to perform the specified actions corresponding to the plurality of modules.

[0046] FIG. 2 is a diagram showing the structure of an electronic device and a user device according to various embodiments.

[0047] 2 , the electronic device 101 , the first server 102 , the second server 103 , the operator device 104 , and the user device 105 may include an input / output unit 210 , a communication unit 220 , a storage 230 , and a processor 240 .

[0048] The input / output unit 210 may be various interfaces or ports for receiving user input or outputting information to the user. The input / output unit 210 may include an input module and an output module, and the input module receives user input from the user. User input may be implemented in various forms including key input, touch input, and voice input. Examples of input modules that can receive such user input include not only traditional keypads or keyboards, and mice, but also touch sensors that sense user touch, microphones that receive voice signal input, cameras that recognize gestures through image recognition, proximity sensors that include at least one of an illumination sensor or an infrared sensor that senses user approach, motion sensors that recognize user movements through acceleration sensors or gyroscope sensors, and other input mechanisms that sense or receive various forms of user input. The input module of the embodiment of the present invention may include at least one of the above-listed devices. Here, the touch sensor can be implemented as a piezoelectric or electrostatic touch sensor that senses touch by a touch panel or touch film attached to the display panel, and an optical touch sensor that senses touch by an optical method, etc. In addition, the input module can also be implemented in the form of an input interface (USB (Universal Serial Bus) port, PS / 2 (Personal System / 2, second generation personal system) port, etc.) connected to an external input device that receives user input, rather than a device that senses user input itself. In addition, the output module can output various information. The output module may include a display that outputs images, a speaker that outputs sounds, a tactile device that generates vibrations, and at least one of various output mechanisms in addition to these. In addition, the output module can also be implemented in the form of a port-type output interface that connects to the above-mentioned individual output mechanisms.

[0049] As an example, an output module in the form of a display can display text, static images, and videos. The display may include a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flat panel display (FPD), a transparent display, a curved display, a flexible display, a 3D display, a holographic display, a projector, and at least one of other devices of various forms that can perform image output functions. This type of display may also be in the form of a touch display that is integrally formed with a touch sensor of an input module.

[0050] The communication unit 220 can communicate with other devices. Therefore, the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 can send and receive information with other devices through the communication unit. For example, the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 can use the communication unit to communicate with each other or communicate with other devices.

[0051] Here, communication, i.e., the sending and receiving of data, can be realized in a wired or wireless form. For this purpose, the communication unit may include: a wired communication module connected to the Internet via a LAN (Local Area Network), a mobile communication module connected to a mobile communication network via a mobile communication base station to send and receive data, a short-range communication module using a communication method of the WLAN (Wireless Local Area Network) series such as Wireless Fidelity (Wi-Fi) or a communication method of the WPAN (Wireless Personal Area Network) series such as Bluetooth and Zigbee, a satellite communication module using a GNSS (Global Navigation Satellite System) such as GPS (Global Positioning System), or a combination thereof.

[0052] The storage 230 can store various information. The storage can store data temporarily or semi-permanently. For example, the storage of the electronic device 101 can store the operating program (OS, Operating System; operating system) used to drive the electronic device 101, the data used to host the website, or the data of the program or application (e.g., web application) used to generate Braille. In addition, the storage can store the module in the form of computer code as described above.

[0053] Examples of the storage 230 may include: a hard disk (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), a random access memory (RAM), etc. Such storage may be provided in a built-in type or a removable type.

[0054] The processor 240 controls the overall operation of the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105. To this end, the processor 240 can perform various information calculations and processing, and control the operation of the components of the electronic device 101. For example, the processor 240 can execute a program or application for managing log information. The processor 240 can be implemented by a computer or a similar device through hardware, software, or a combination thereof. In terms of hardware, the processor 240 can be implemented in the form of an electronic circuit that processes electrical signals to perform control functions, and in terms of software, it can be implemented in the form of a program that drives the hardware processor 240. On the other hand, if it is not specifically mentioned in the following description, it can be interpreted that the operation of the electronic device 101, the first server 102, the second server 103, the operator device 104, and the user device 105 is performed by the control of the processor 240. That is, when executing the module implemented in the above-mentioned log information management system 100, the module can be interpreted as the processor 240 controlling the electronic device 101, the first server 102, the second server 103, the operator device 104 and the user device 105 to perform the following actions.

[0055] In summary, various embodiments can be implemented by various mechanisms. For example, various embodiments can be implemented by hardware, firmware, software, or a combination thereof.

[0056] When implemented by hardware, the methods of various embodiments can be implemented by one or more ASICs (application specific integrated circuits), DSPs (digital signal processors), DSPDs (digital signal processing devices), PLDs (programmable logic devices), FPGAs (field programmable gate arrays), processors, controllers, microcontrollers, microprocessors, etc.

[0057] When implemented by firmware or software, the methods of various embodiments can be implemented in the form of modules, sequences, or functions that implement the functions or actions described below. For example, the software code can be stored in a memory and driven by a processor. The above memory can be located inside or outside the processor and can exchange data with the processor through various well-known mechanisms.

[0058] The following describes various embodiments in more detail based on the above technical ideas. The various embodiments described below can apply the contents described above. For example, actions, functions, terms, etc. not defined in the various embodiments described below can be implemented and described based on the contents described above.

[0059] In the following description, various embodiments are described on the premise that the electronic device 101 performs log information management operations. According to various embodiments, the electronic device 101 can send and receive information related to the log information management operations between the first server 102, the second server 103, the operator device 104 and the user device 105.

[0060] FIG. 3 is a flowchart of the operation of managing log information of an electronic device according to various embodiments.

[0061] According to various embodiments, the electronic device 101 may generate outline information (S301). The outline information may include at least information associated with a user object provided to the user device 105. The user object may include a graphical user interface (GUI) included in at least a portion of an application or website (e.g., a web application) that accompanies the provision of services to the user. The user object may provide the user with events associated with the user object, and the events may include, for example, an impression event that displays the user object or a click event that occurs based on the user's input to the user device 105. The event corresponding to the user object may occur on a specified page that provides an application or website for providing services. In an embodiment, the outline information may include one or more information associated with an event (e.g., a first event) corresponding to a specified user object (e.g., a first object). The electronic device 101 may generate the outline information of the first event corresponding to the first object based on the input received through the operator device 104, and store the generated outline information. The so-called outline may include various meta information about the specified object and the event corresponding to the object. For example, it may include the structure information of the object, the form information, the domain (category) information of the object, and the type information of the event corresponding to the object. In an embodiment, the outline information may at least include the identification information of the outline of the specified object (e.g., the first object) and the event corresponding to the object (e.g., the first event). In an embodiment, the outline information may include at least a part of the name information of the outline, the name information of the first event, the category information of the first event, the type information of the first event, the domain information of the first object, the page information including the first object, and the version information of the outline. According to one embodiment, the schema information related to the first object and the first event corresponding to the first object can be refreshed or changed, and the version information of the schema can be changed corresponding to the refreshing or changing of the schema information. The electronic device 101 can store historical information corresponding to each version of the schema.

[0062] According to various embodiments, the electronic device 101 may provide the second server 103 with the framework information S302. The second server 103 may include a backend server that receives a request associated with the execution data of an application or website used to provide services to a user from the first server 102, and provides the first server 102 with the execution data corresponding to the request. In an embodiment, the second server 103 may receive the framework information from the electronic device 101, and generate the first log information based on the framework information (S310). The first log information may include log information generated based on the framework information. The first log information may include data used to generate monitoring information corresponding to the first event of the first object. For example, the first log information may be information corresponding to the first object and the first event generated based on the framework information. In an embodiment, the first log information may include at least a portion of the framework information. For example, the first log information may include at least a portion of the schema identification information, the schema name information, the first event name information, the first event category information, the first event type information, the first object domain information, the first object page information, and the schema version information.

[0063] According to various embodiments, the user device 105 may transmit a request related to the first event to the second server 103. In an embodiment, the user device 105 may transmit a request related to the first event corresponding to the first object to the second server 103. The request related to the first event may include a request for receiving execution data related to the first event from the second server 103. According to one embodiment, the user device 105 transmits the first event request to the first server 102 S311, and the first server 102 that receives the request related to the first event transmits the request related to the first event to the second server 103 (S312), so that the request related to the first event can be transmitted from the user device 105 to the second server 103. Alternatively, the user device 105 may use an application associated with service provision stored in the user device 105 to directly transmit the request related to the first event to the second server 103. The second server 103 receiving the request related to the first event may transmit execution data to the first server 102 based on the request related to the first event (S313), and the first server 102 may provide the first event to the user device 105 based on the execution data (S314). According to one embodiment, when the user device 105 directly transmits a request to the second server 103 using an application program related to service provision stored in the user device 105, the user device 105 may directly receive the execution data from the second server 103, and the user device 105 may provide the first event based on the execution data.

[0064] According to an embodiment, the execution data corresponding to the first event provided by the second server 103 may include the first log information. The second server 103 may insert the first log information into the execution data related to the first object corresponding to the first event. The execution data related to the first object may include the first log information in at least a portion.

[0065] According to various embodiments, the electronic device 101 may receive log information S303 from the first server 102. In an embodiment, the electronic device 101 may receive log information including at least the first log information included in the execution data from the first server 102. In an embodiment, the first server 102 may return the first log information included in the execution data related to the first object to the electronic device 101. In an embodiment, the log information may include the first log information and the second log information. The second log information may be generated based on the information related to the user device 105 and the first event. The second log information may be generated by the first server 102 or the user device 105 based on the first event and transmitted to the electronic device 101. According to one embodiment, the second log information may include at least a portion of the IP address information (internet protocol address information) corresponding to the user device 105, the platform information of the user device 105, the UUID (universally unique identifier), the PCID (personal computer identifier), the time information, and the application version information. According to one embodiment, the first server 102 may transmit log information including the first log information included in the execution data and the second log information generated by the first server 102 to the electronic device 101 in response to receiving the execution data S313 and / or providing the first event S314.

[0066] According to various embodiments, the electronic device 101 may generate monitoring information (S304). In an embodiment, the electronic device 101 may generate monitoring information corresponding to the first event based on the log information. The electronic device 101 may classify the log information based on the first log information and / or the second log information included in each of more than one log information. In an embodiment, the electronic device 101 may process a plurality of log information based on various data such as a schema identifier included in the first log information corresponding to the first event, and generate monitoring information associated with the first event based on the processed plurality of log information. The electronic device 101 may use a distributed messaging system (e.g., Kafka) to consume distributed log information according to a topic based on a schema identifier to generate monitoring information related to the first event. In an embodiment, the electronic device 101 can count the consumed log information, generate numerical information related to the first log information corresponding to the first event, and provide a notification related to the first event to the operator device 104 based on the generated numerical information.

[0067] FIG. 4 is a diagram showing the first page of the electronic device for managing category information in various embodiments.

[0068] 4 , the electronic device 101 of various embodiments can manage category information through the first page 400 .

[0069] According to various embodiments, the electronic device 101 may provide the operator device 104 with a first page 400 for managing schema information.

[0070] According to various embodiments, the first page 400 may provide a schema generation interface 401 for generating new schema information. The schema generation interface 401 may receive input of data related to the new schema, and may store the schema information generated based on the input data.

[0071] According to various embodiments, the first page 400 may provide a category index 402 in at least a portion. The category index 402 may display more than one category information. The electronic device 101 may provide a category information window 403 based on an operator input corresponding to at least one category information included in the category index 402. The category information window 403 may display the selected category information in the category index 402 based on the operator input. Referring to FIG. 4 , the category index 402 may include at least a portion of the category identification information (id), the corresponding application information (tenant), the category name (name), and the update information (updated at). At this time, when the same category information is updated and changed to a different version, the update information may include information related to the time of the update. Referring to FIG. 4 , the category information window 403 may be at least a portion of the first page 400 that specifically displays the category information displayed in the category index 402. For example, the schema information window 403 may provide schema identification information (id), corresponding application information (tenant), schema name (name), update information (updated), description information (description), and creation information (created). The creation information and update information may include a portion of operator information and time information associated with the creation operation or update operation corresponding to the schema information.

[0072] According to various embodiments, the first page 400 may include a version generation interface 404 in at least a portion of the area. The electronic device 101 may receive input related to a new version of the outline information selected in the outline index 402 based on the operator input corresponding to the version generation interface 404. For example, the input related to the new version may mean changing, deleting, or adding various data included in the outline information. In this case, at least the identification information of the outline may be retained. In an embodiment, the first page 400 may provide a version management window 405 in at least a portion of the area to display information related to each version, and each version corresponds to the outline information displayed in the outline information window 403. For example, referring to FIG. 4, the version management window 405 may display at least a portion of version information (version), version status information (state), update time information (updated at), and project information (project).

[0073] FIG. 5 is a diagram showing schematic information of various embodiments by way of example.

[0074] FIG. 6 is an example of additional schema information in various embodiments.

[0075] 5 , the schema information may include information associated with an event of a user object. Referring to FIG. 5 , the schema information 500 may include at least schema identification information (schema id). Each schema information 500 may be assigned with inherent schema identification information and may be identified based on the schema identification information. In an embodiment, the schema information 500 may include state information (state), project information (project), application information (tenant) corresponding to the user object, schema name information (schema name), schema description information (schema description), schema version information (version), version description information (version description), event category information (log category), event type information (log type), domain information (domain), page information (page name) of the user object corresponding to the schema, event name information (event name), generation information, and at least a portion of update information. In an embodiment, the first log information associated with the event corresponding to the specified object may be generated based on the schema information 500. The first log information may include at least a portion of the schema information 500.

[0076] 6 , the outline information 500 may include additional information 600 . Depending on the outline, the additional information 600 may include different types of data. In an embodiment, the additional information 600 may include data items associated with an object specified according to the outline information 500 or an event corresponding to the object. For example, referring to the example of FIG. 6 , the outline information 500 of FIG. 5 may be outline information associated with an event corresponding to a widget object, and the outline information 500 may include data associated with the widget object, such as widget position information (widget position name) as the additional information 600 . In addition, the outline information 500 of FIG. 5 may be outline information related to a widget that exposes a specific item, and the additional information 600 corresponding to the outline information 500 of FIG. 5 may include item identification information (item id). In an embodiment, the first log information may be generated based on the additional information 600 included in the outline information 500 . The first log information may include at least a portion of the additional information 600 .

[0077] FIG. 7 is a diagram for illustrating object-related events according to various embodiments.

[0078] Referring to FIG. 7 , an example of an application page 700 for providing services to users is shown. The application page 700 is at least a portion of a website or application for providing services to users, and may be a page provided from the first server 102 and / or the second server 103 of FIG. 1 to the user device 105. In an embodiment, the application page 700 may include at least one object (e.g., the first object 701). The at least one object may include at least one portion of one or more images, one or more texts, and one or more user interfaces. Referring to the example of FIG. 7 , the application page 700 may be a product detail page associated with a specific item. Referring to the example of FIG. 7 , the first object 701 may be an interface tool set for exposing price and discount information of second-hand goods or goods with broken boxes associated with the item corresponding to the product detail page. At this time, the event associated with the first object 701 may include, for example, an impression event for displaying the first object 701 or a click event for the first object 701 that occurs based on the user's input to the user device 105 .

[0079] In an embodiment, the electronic device 101 may generate schema information associated with an event of the first object 701. On the other hand, there may be more than one event associated with the first object 701. For example, a display event of displaying the first object 701, a click event occurring in at least a portion of the first object 701, and a display or click event corresponding to each of more than one user interface included in the first object 701 may all be events corresponding to the first object 701. The electronic device 101 may generate schema information corresponding to each of at least a portion of the more than one event, and the more than one event corresponds to a certain object as described above.

[0080] In an embodiment, the electronic device 101 may receive the first log information corresponding to the event of the first object 701. For example, when an exposure event corresponding to the first object 701 occurs, that is, when the first server 102 receives the execution data associated with the first object 701 from the second server 103, the first server 102 may transmit the first log information associated with the exposure event of the first object 701 included in the execution data to the electronic device 101. The first server 102 may include the second log information associated with the user device 105 in the log information and transmit it to the electronic device 101 together with the first log information. The electronic device 101 may receive the first log data and the second log data corresponding to the first event (e.g., exposure event) associated with the first object 701, wherein the first log data includes information associated with the first event, and the second log data includes information associated with the user device 105 that requested the first event.

[0081] FIG. 8 is an illustrative diagram of log information according to various embodiments.

[0082] 8 , log information 800 may include first log information 801 and second log information 802 .

[0083] According to various embodiments, the first log information 801 may be log information generated based on schema information. The first log information 801 may include various information associated with the user object and the event corresponding to the user object. Referring to FIG. 8 , the first log information 801 may include at least schema identification information (schema id). In an embodiment, the first log information 801 may include at least a portion of schema version information (schema version), event type information (log type), event reference information (event referrer), category information (domain), event name information (event name), event category information (log category), and page information (page name) corresponding to the user object. At this time, the event reference information may include information corresponding to an event that must be performed first in order for the event corresponding to the corresponding schema information to occur. For example, before a click event related to a user object included in a certain interface tool set, an exposure event of the corresponding interface tool set may be performed first, and the event reference information corresponding to the outline information of the click event may be information associated with the exposure information of the interface tool set.

[0084] According to various embodiments, the second log information 802 may include information related to the user device 105. In an embodiment, the second log information 802 may be confirmed and / or generated based on the occurrence of an event associated with the user object. Referring to FIG. 8 , the second log information 802 may include at least a portion of platform information (platform), UUID (universally unique identifier), PCID (personal computer identifier), language information (lang), resolution information (resolution), time information (event time), application model information (model), and application version information (e.g., application version name information (app version name), application version code information (app version code)) corresponding to the user device 105.

[0085] In the embodiment, the second server 103 may generate the first log information 801 based on the schema information, and may include the generated first log information 801 in the execution data of the user object corresponding to the schema information. The second server 103 may transmit the execution data of the event including the first log information 801 to the first server 102 in response to receiving the request of the event related to the user object. The first server 102 may provide the electronic device 101 with the first log information 801 included in the execution data and the second log information 802 confirmed and / or generated by the first server 102 in response to the occurrence of the event.

[0086] FIG. 9 is a diagram showing a second page for managing monitoring information according to various embodiments.

[0087] 9 , the electronic device 101 may provide the operator device 104 with a second page 900 for managing monitoring information.

[0088] According to various embodiments, the second page 900 may provide a monitoring setting index including one or more monitoring setting information 902 corresponding to an event related to a user object. The monitoring setting index may include an index related to the monitoring setting information corresponding to each of the more than one monitoring information. The monitoring setting information may include information that serves as a basis for generating the monitoring information. For example, the monitoring setting information may at least include the schema identification information of one or more schemas that serve as monitoring objects in the monitoring information. In an embodiment, the second page 900 may provide a monitoring generation interface 901 to generate new monitoring setting information. The electronic device 101 may generate the monitoring setting information based on the input received from the operator device 104 corresponding to the monitoring generation interface 901. In an embodiment, the electronic device 101 may display the monitoring setting information that is selected based on the input to at least a portion of the area of ​​the second page 900 corresponding to the monitoring setting information 902. In an embodiment, the second page 900 may display at least a portion of the operation type information (processing time), the monitoring type, and the name of the monitoring information corresponding to the monitoring setting information. The electronic device 101 may generate monitoring information corresponding to the monitoring setting information based on the log information and the monitoring setting information. For example, referring to the monitoring setting information 902, the operation type is near-real-time, and the log information may be processed nearly in real time to generate monitoring information. The monitoring type corresponds to the raw log count method, so the electronic device 101 may classify the log information corresponding to the monitoring setting information 902, and generate monitoring information based on the numerical information of the classified log information.

[0089] FIG. 10 is a diagram showing the third page for generating monitoring setting information according to various embodiments.

[0090] Referring to FIG. 10 , the third page 1000 may be a page provided based on input to the monitoring generation interface 901 of FIG. 9 . Referring to FIG. 10 , the third page 1000 may provide various interfaces for receiving input of monitoring setting information. For example, the third page 1000 may include a name interface 1001 for receiving input of a name of monitoring information, a category selection interface 1002 for receiving input of category information to be monitored, and at least a portion of category identification information 1003 corresponding to the category information selected based on input to the category selection interface 1002, category name information 1004, and category description information 1005. In an embodiment, the electronic device 101 may generate monitoring information based on the monitoring setting information. For example, the electronic device 101 may confirm log information based on one or more category information confirmed based on the monitoring setting information, and generate monitoring information corresponding to the monitoring setting information based on the confirmed log information.

[0091] Referring to FIG. 10 , the third page 1000 may include a filter setting interface 1006. The filter setting interface 1006 may set conditions for filtering log information related to the category information selected corresponding to the monitoring setting information. The filter conditions may be set differently corresponding to each category information. The filter conditions may be set corresponding to a plurality of items included in the log information. For example, a filter related to platform information among the items included in the log information may be set. In this case, only the log information related to the platform information may become the basis of the monitoring information, and the platform information corresponds to the set filter.

[0092] 10 , the third page 1000 may include a label interface 1007. The electronic device 101 may group one or more category information selected corresponding to the monitoring setting information based on the input to the label interface 1007, and set labels for distinguishing each group.

[0093] FIG. 11 is a diagram for illustrating monitoring information of various embodiments.

[0094] Referring to FIG. 11 , a monitoring page 1100 showing monitoring information corresponding to the monitoring setting information 902 selected in the second page 900 of FIG. 9 may be shown. According to various embodiments, the monitoring page 1100 may display monitoring information generated corresponding to the selected monitoring setting information. The monitoring information may include numerical information generated based on the log information. In an embodiment, the numerical information may include a chart 1102 generated based on the log information. The electronic device 101 may confirm the log information based on the monitoring setting information, and generate monitoring information based on the confirmed log information. For example, in FIG. 11 , the monitoring setting information may include information for selecting the category information corresponding to the category identification information of “10”, “116”, and “124”, respectively. Therefore, the monitoring information (e.g., chart 1102) generated based on the monitoring setting information may be generated based on the log information corresponding to each of the category identification information “10”, “116”, and “124”, respectively. That is, the chart 1102 of FIG. 11 can be understood as being generated based on log information corresponding to each of the schema identification information "10", "116" and "124", and the log information is received by the electronic device 101 corresponding to the event of the object.

[0095] Referring to FIG. 11 , the monitoring page 1100 may display monitoring setting information 1103 corresponding to the monitoring information being monitored in at least a portion. Referring to FIG. 11 , the monitoring setting information 1103 may include at least a portion of the processing type, the name information of the monitoring information, the description information of the monitoring information, the generation information of the monitoring setting information, the latest update information of the monitoring setting information, and the expiry date of the monitoring setting information. In an embodiment, the monitoring page 1100 may include a dashboard icon 1101 for displaying a dashboard page, and the dashboard page displays more than one monitoring information. The electronic device 101 may provide a dashboard page displaying more than one monitoring information based on an input to the dashboard icon 1101.

[0096] FIG. 12 is a diagram showing a dashboard page displaying monitoring information according to various embodiments.

[0097] FIG. 13 is a diagram showing a user interface for operators to set a dashboard page according to various embodiments.

[0098] 12, the dashboard page 1200 can display more than one monitoring information. According to one embodiment, the dashboard page 1200 can generate and display more than one monitoring information based on more than one log information, and the more than one log information is confirmed based on the monitoring setting information.

[0099] In an embodiment, the dashboard page 1200 can display the monitoring name corresponding to the monitoring setting information about the monitoring object on the first interface 1201.

[0100] According to various embodiments, the dashboard page 1200 may include one or more interfaces for richly displaying monitoring information. The dashboard page 1200 may generate various numerical information corresponding to the log information based on the settings made through the one or more interfaces. For example, the electronic device 101 may classify one or more log information selected based on the monitoring setting information based on the settings made through the one or more interfaces of the dashboard page 1200, and may generate numerical information corresponding to each of the classified log information, thereby generating one or more monitoring information.

[0101] In an embodiment, the dashboard page 1200 may include at least a portion of the second interface 1202, the third interface 1203, the fourth interface 1204, the fifth interface 1205, and the sixth interface 1206. The second interface 1202 is used to select application information (tenant), the third interface 1203 is used to select at least a portion of one or more outline information corresponding to the monitoring setting information, the fourth interface 1204 is used to select at least one version of one or more versions corresponding to the selected outline information, the fifth interface 1205 is used to select according to the platform in the log information confirmed based on the monitoring setting information, and the sixth interface 1206 is used to set the time range. The electronic device 101 can generate one or more monitoring information based on the selection items set in each of the one or more interfaces of the dashboard page 1200. For example, the dashboard page 1200 can generate monitoring information that sorts the log information corresponding to the monitoring setting information based on the platform information based on the corresponding monitoring setting information and the settings of one or more interfaces (e.g., the fifth interface 1205), i.e., the first chart 1207. Alternatively, for another example, the dashboard page 1200 can generate monitoring information that sorts the log information corresponding to the monitoring setting information based on the outline information based on the corresponding monitoring setting information and the settings of one or more interfaces (e.g., the third interface 1203), i.e., the second chart 1208.

[0102] 13, a time range interface 1300 for setting a time range is provided corresponding to the sixth interface 1206 of FIG. 12. The time range interface 1300 may include a first area 1301 for setting a range based on an absolute time and a second area 1302 for setting a range based on a relative time. The dashboard page 1200 may generate and display monitoring information corresponding to the time range set based on the settings of the time range interface 1300.

[0103] FIG. 14 is a diagram showing a query area 1400 for setting conditions for a dashboard page according to various embodiments.

[0104] 14, the dashboard page 1200 of FIG. 12 may include a query area 1400 for setting notification conditions corresponding to each monitoring information in at least a portion of the area. In an embodiment, the electronic device 101 may set notification conditions corresponding to each of the one or more monitoring information based on the one or more interfaces included in the query area 1400. The electronic device 101 may provide notifications related to the corresponding monitoring information to the operator device 104 based on the set notification conditions.

[0105] 14 , the query area 1400 may include a rule interface 1410 for setting a rule and a condition interface 1420 for setting a condition. In an embodiment, the rule interface 1410 may set at least a part of a name 1411 corresponding to the notification condition, periodic information 1412 for confirming whether the notification condition is satisfied, and notification time interval information 1413. In an embodiment, the condition interface 1420 may receive input of one or more condition instruction statements 1421, 1423, 1425 and values ​​1422, 1424, 1426 corresponding to the target value of the condition instruction statement. For example, referring to FIG. 14 , the electronic device 101 may provide a notification message corresponding to the monitoring information to the operator device 104 based on the condition interface 1420 when the average value (avg()) of "A" as monitoring information from 5 minutes (5m) ago to the present (now) exceeds "100".

[0106] FIG. 15 is a flow chart showing the operation of generating monitoring information by an electronic device in various embodiments.

[0107] According to various embodiments, in action S1501, the electronic device 101 may generate outline information. The outline information may include at least information associated with the user object provided to the user device 105. The user object may provide the user with an event associated with the user object, and the outline information may include information related to the event corresponding to the user object. The event may include, for example, an exposure event of displaying the user object or a click event of the user object occurring based on the user's input to the user device 105. The event corresponding to the user object may occur on a specified page that provides an application or website for providing a service. In an embodiment, the outline information may include one or more information associated with an event (e.g., the first event) corresponding to the specified user object (e.g., the first object). The electronic device 101 may generate the outline information of the first event corresponding to the first object based on the input received through the operator device 104, and store the generated outline information. The so-called outline may include various meta information associated with the specified object and the event corresponding to the object. For example, it may include the structure information of the object, the form information, the domain (category) information of the object, and the type information of the event corresponding to the object. In an embodiment, the outline information may at least include the identification information of the outline of the specified object (e.g., the first object) and the event corresponding to the object (e.g., the first event). In an embodiment, the outline information may include at least a part of the name information of the outline, the name information of the first event, the category information of the first event, the type information of the first event, the domain information of the first object, the page information including the first object, and the version information of the outline. According to one embodiment, the schema information related to the first object and the first event corresponding to the first object can be refreshed or changed, and the version information of the schema can be changed corresponding to the refreshing or changing of the schema information. The electronic device 101 can store historical information corresponding to each version of the schema.

[0108] According to various embodiments, in action S1502, the electronic device 101 may receive the first log information generated based on the outline information. The first log information may include log information generated based on the outline information. The first log information may include data used to generate monitoring information corresponding to the first event of the first object. For example, the first log information may be information corresponding to the first object and the first event generated based on the outline information. In an embodiment, the first log information may include at least a portion of the outline information. For example, the first log information may include at least a portion of the identification information of the outline, the name information of the outline, the name information of the first event, the category information of the first event, the type information of the first event, the domain information of the first object, the page information including the first object, and the version information of the outline.

[0109] According to various embodiments, in action S1503, the electronic device 101 may generate monitoring information based on the first log information. In an embodiment, the electronic device 101 may generate monitoring information corresponding to the event based on the log information. The electronic device 101 may classify the log information based on the first log information and / or the second log information included in each of more than one log information. In an embodiment, the electronic device 101 may process a plurality of log information based on various data (such as a schema identifier) ​​included in the first log information corresponding to the first event, and generate monitoring information associated with the first event based on the processed plurality of log information. The electronic device 101 may use a distributed messaging system (e.g., Kafka) to consume distributed log information according to a topic based on a schema identifier to generate monitoring information related to the first event. In an embodiment, the electronic device 101 can sort and / or count the consumed log information, generate numerical information related to the first log information corresponding to the first event, and provide a notification related to the first event to the operator device 104 based on the generated numerical information.

[0110] According to one embodiment, the electronic device 101 may set a threshold value for monitoring information. For example, the threshold value may be a threshold value for providing a notification message by comparing with the numerical information included in the monitoring information. For example, the electronic device 101 may provide a notification message related to the first event to the operator device 104 based on the comparison between the monitoring information and the threshold value. In an embodiment, the monitoring setting information may include information related to the threshold value. According to one embodiment, the electronic device 101 may set the threshold value corresponding to the historical information related to the log information. For example, the threshold value corresponding to the monitoring information may be set based on the transition of the numerical information related to the log information by period.

[0111] FIG. 16 is a flowchart of an electronic device according to various embodiments that generates monitoring information based on log information.

[0112] According to various embodiments, in action S1601, the electronic device 101 may obtain log information. The electronic device 101 may obtain log information related to the event from the first server 102 in response to the event provided by the first server 102 to the user device 105. The log information may include first log information included in execution data related to the event corresponding to the user object, and second log information including information related to the user device 105. The electronic device 101 may receive first log information and second log information from the first server 102 in response to a request for an event associated with the object, the first log information including execution data received by the first server 102 from the second server 103, and the second log information confirmed by the first server 102 based on the user device 105.

[0113] According to various embodiments, in action S1602, the electronic device 101 may confirm whether the received log information is valid. In an embodiment, the electronic device 101 may confirm whether the log information is valid based on the schema information. For example, the electronic device 101 may confirm whether the log information is valid based on the first log information included in the log information and the schema information corresponding to the first log information. The first log information is generated based on the schema information, so by confirming the schema information, it can be confirmed whether the log information is effectively generated. The electronic device 101 may confirm the corresponding schema identification information based on the first log information. The electronic device 101 may compare the schema information confirmed based on the schema identification information with the first log information in the received log information, and may confirm whether the first log information is valid based on the comparison. According to one embodiment, the schema information may include information of a valid value. For example, the schema information may include an item related to a valid value among one or more items included in the schema information. The electronic device 101 can compare the first log information based on information related to the valid value to confirm whether the log information is valid. The valid value is confirmed based on the outline information.

[0114] According to various embodiments, in action S1603, the electronic device 101 may generate monitoring information related to an event of an object based on log information and monitoring setting information. In an embodiment, the electronic device 101 may classify the monitoring setting information based on the received log information. The monitoring setting information may include information that is used as a basis for generating the monitoring information. For example, the monitoring setting information may at least include category identification information of one or more categories that are monitored objects in the monitoring information. The electronic device 101 may generate the monitoring setting information based on the input received from the operator device 104. In an embodiment, the electronic device 101 may generate monitoring information corresponding to the monitoring setting information based on the log information and the monitoring setting information. The electronic device 101 may classify the log information corresponding to the corresponding monitoring setting information based on the monitoring setting information, and generate the monitoring information based on the numerical information of the classified log information. For example, the electronic device 101 may confirm the log information corresponding to the category information confirmed based on the monitoring setting information. The electronic device 101 may classify the log information based on the category identification information corresponding to the monitoring setting information, and may generate numerical information based on the classified log information. The generated numerical information may be included in the monitoring information corresponding to the monitoring setting information.

[0115] According to one embodiment, the electronic device 101 may generate monitoring information based on whether the log information is valid. The electronic device 101 may generate monitoring information based on the log information in action S1603 using the valid log information confirmed in action S1602. In another embodiment, even in the case of invalid log information, the electronic device 101 may generate monitoring information based on this. The electronic device 101 may confirm the category identification information based on the invalid log information, and classify the invalid logs according to the category identification information. The electronic device 101 may generate monitoring information based on the invalid log information corresponding to the category identification information, and may provide a notification message based on the numerical information included in the generated monitoring information.

[0116] 100: Log Information Management System 101: Electronic devices 102: Server 1 103: Server 2 104: Operator Device 105: User device 210: Input / output unit 220: Communications Department 230: Storage 240: Processor 400: Page 1 401: Outline generation interface 402: Index of categories 403: Gangmu Information Window 404: Version generation interface 405: Version management window 500: Gangmu Information 600: Additional information 700: Application page 701: Object 1 800: Log information 801: Log information No. 1 802: Log information No. 2 900: Page 2 901: Monitoring interface 902: Monitoring setting information 1000: Page 3 1001: Name interface 1002:Outline selection interface 1003: Classification Information 1004: Name information of the outline 1005: Information about the outline 1006: Filter setting interface 1007:Tag interface 1100: Monitoring page 1101: Dashboard Icon 1102: Chart 1103: Monitoring setting information 1200: Dashboard page 1201: Interface 1 1202: Interface 2 1203: Interface 3 1204: Interface 4 1205: Interface 5 1206: Interface 6 1207: Chart 1 1208: Chart 2 1300: Time Range Interface 1301: Area 1 1302: Area 2 1400: Query area 1410: Rules Interface 1411: Name 1412: Regular Information 1413: Notification time interval information 1420: Conditional Interface 1421: Conditional statement 1422: value 1423: Conditional statement 1424: value 1425: Conditional statement 1426: value S301: Action S302: Action S303: Action S304: Action S310: Action S311: Action S312: Action S313: Action S314: Action S1501: Action S1502: Action S1503: Action S1601: Action S1602: Action S1603: Action

Claims

1. A log information management method, implemented in an electronic device, comprising the following steps: generating outline information related to an outline of a first object provided to a user device; receiving first log information generated from the first server based on the outline information in accordance with a first event related to the first object on the first server; generating monitoring information related to the first event according to the log information consumed based on the topic of the outline identifier included in the first log information; and counting the consumed log information to generate numerical information related to the first log information corresponding to the first event, wherein... The first event mentioned above includes a display event related to the display of the first object mentioned above, or a click event related to user input corresponding to the first object mentioned above.

2. The log information management method of request item 1, wherein the above-mentioned category information includes at least a portion of the above-mentioned category identification information, including the name information of the above-mentioned category, the name information of the above-mentioned first event, the category information of the above-mentioned first event, the type information of the above-mentioned first event, the scope information of the above-mentioned first object, the page information of the above-mentioned first object, and the version information of the above-mentioned category.

3. The log information management method of request item 1, wherein the first log information is generated in the second server based on the outline information, and the second server provides execution data related to the first object, including the first log information, to the second server based on the request received from the first server related to the first event.

4. The log information management method of claim 3, wherein the first server provides the user device with events related to the first object based on execution data related to the first object, and sends the first log information included in the execution data related to the first object back to the electronic device.

5. The log information management method of request item 1, wherein the step of generating the above-mentioned monitoring information further includes the following steps: generating monitoring setting information including the identification information of the outline of the above-mentioned first object; obtaining, based on the outline information, the first log information associated with the above-mentioned first object from the log information received from the above-mentioned first server, wherein the outline information is confirmed based on the above-mentioned monitoring setting information; generating the monitoring information of the above-mentioned first event based on the collected above-mentioned first log information.

6. The log information management method of claim 5, wherein the monitoring setting information includes identification information of an outline corresponding to the at least one object, and information of at least one parameter related to the first event confirmed based on the outline information; the step of generating the monitoring information further includes the following steps: classifying the first log information based on the parameters; and generating the monitoring information based on the classification.

7. The log information management method of request item 1, wherein the monitoring information includes the numerical information related to the first log information, the first log information corresponding to the first event; the log information management method further includes the following steps: providing a notification message to one or more operator devices corresponding to the electronic device based on the numerical information.

8. The log information management method of request item 1 further includes the following steps: providing a notification message to one or more operator devices corresponding to the above-mentioned electronic device based on the threshold information, wherein the threshold information is confirmed in accordance with the above-mentioned monitoring information and historical information related to the above-mentioned first log information.

9. The log information management method of request item 1 further includes the following steps: receiving second log information from the first server in response to the first event, the second log information being generated based on information related to the user device requesting the first event and the first event; and generating monitoring information related to the first event based on the first log information and the second log information.

10. The log information management method as described in Request 9, wherein the aforementioned information includes at least a portion of the IP information of the aforementioned user device, the identification information of the aforementioned user device, the platform information of the aforementioned user device, and the identification information related to the aforementioned first event.

11. The log information management method of request item 1, wherein the step of generating the above-mentioned monitoring information further includes the following steps: based on the above-mentioned outline information, confirming whether the received first log information is valid; and based on whether it is valid, generating the above-mentioned monitoring information.

12. The log information management method of request item 11, wherein the above-mentioned category information further includes information related to the valid value of the log, and the above-mentioned step of confirming whether it is valid further includes the following steps: Based on the above-mentioned first log information, confirm the identification information of the category; compare the information related to the valid value with the above-mentioned first log information, wherein the valid value is confirmed in accordance with the confirmed identification information of the above-mentioned category.

13. The log information management method as described in request item 1, wherein the first object mentioned above includes a graphical user interface object.

14. An electronic device comprising a transceiver, a storage unit, and a processor; wherein the processor is configured to: generate outline information related to the outline of a first object provided to a user device; receive first log information generated from the first server based on the outline information corresponding to a first event related to the first object on a first server; consume scattered log information based on the topic of the outline identifier included in the first log information; generate monitoring information related to the first event; and count the consumed log information to generate numerical information related to the first log information corresponding to the first event, wherein... The first event mentioned above includes a display event related to the display of the first object mentioned above, or a click event related to user input corresponding to the first object mentioned above.

15. A non-transitory computer-readable recording medium recording a program for performing the method as described in claim 1 on a computer.

Images