WO2014156825A1 - ログ出力制御装置、方法及びプログラム - Google Patents
ログ出力制御装置、方法及びプログラム Download PDFInfo
- Publication number
- WO2014156825A1 WO2014156825A1 PCT/JP2014/057311 JP2014057311W WO2014156825A1 WO 2014156825 A1 WO2014156825 A1 WO 2014156825A1 JP 2014057311 W JP2014057311 W JP 2014057311W WO 2014156825 A1 WO2014156825 A1 WO 2014156825A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- log
- client
- log output
- program
- information
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0778—Dumping, i.e. gathering error/state information after a fault for later diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
Definitions
- the present invention relates to a log output control device, method, and program.
- the client sends a failure analysis log to the server.
- the amount of logs sent to the server increases explosively as the number of users increases.
- the load on the server and the network becomes high, which affects not only the own system but also other systems. Therefore, there is a problem that it becomes difficult to operate a large-scale system on the cloud.
- Patent Document 1 describes a system that avoids an enormous amount of logs being recorded by collecting only the logs of a failed terminal using terminal information.
- the present invention has been made in view of the above problems, and an object of the present invention is to provide a log output control device, method, and program capable of efficiently controlling log output processing in a client.
- the present invention uses a log history output by a client, illegal operation information related to an illegal operation of a program detected from the log, and log generation information related to a log output process inserted in a program executed on the client.
- a log output control device that dynamically controls a log output location in a program requested by a client.
- the present invention uses a log history output by a client, illegal operation information related to an illegal operation of a program detected from the log, and log generation information related to a log output process inserted in a program executed on the client.
- This is a log output control method for dynamically controlling a log output location in a program requested by a client.
- the present invention provides a computer with a log history output by a client, illegal operation information regarding an illegal operation of a program detected from the log, log generation information regarding a log output process inserted into a program executed by the client, and Is used to execute processing for dynamically controlling the log output location in the program requested by the client.
- log output processing at the client can be controlled efficiently.
- FIG. 1 is a conceptual diagram of the present invention.
- FIG. 2 is a block diagram of the first embodiment of the present invention.
- FIG. 3 is a diagram illustrating log generation information.
- FIG. 4 is a diagram illustrating illegal operation information.
- FIG. 5 is a diagram illustrating an event history.
- FIG. 6 is a diagram showing the components of the system according to the first embodiment and the flow of each operation process.
- FIG. 7 is a diagram for explaining a process of embedding a log output process for failure analysis in a script file.
- FIG. 8 is a flowchart for explaining the log output process insertion process.
- FIG. 9 is a flowchart for explaining the event history writing process.
- FIG. 10 is a flowchart for explaining the illegal information writing process.
- FIG. 10 is a flowchart for explaining the illegal information writing process.
- FIG. 11 is a diagram illustrating a script in which a log output process is inserted.
- FIG. 12 is a block diagram of the second embodiment of the present invention.
- FIG. 13 is a diagram for explaining a rule for identifying a user.
- FIG. 14 is a diagram illustrating an example of an output result in the second embodiment.
- FIG. 15 is a block diagram of the third embodiment of the present invention.
- the present invention relates to a log history output by a client, illegal operation information related to an illegal operation of a program detected from the log, and log output processing inserted in a program executed by the client.
- the present invention relates to a log output control apparatus that dynamically controls log output locations in a program requested by a client using log generation information.
- FIG. 2 is a configuration diagram of the first embodiment of the present invention.
- the first embodiment includes a log output control device 100 and a script execution device 200.
- the log output control device 100 is a portal server
- the script execution device is a client that includes a Web browser, a script execution engine, and the like. These are connected by a network such as the Internet.
- server-side log output control device 100 which is the main part of the present invention, will be mainly described.
- the log output control apparatus 100 includes a data transmission / reception unit 110, a data analysis unit 120, a log processing unit 130, and a storage management unit 140.
- the data transmission / reception unit 110 includes a request reception unit 111, a log reception unit 112, and a response transmission unit 113.
- the data analysis unit 120 includes a log analysis unit 121 and an unauthorized operation analysis unit 122.
- the log analysis unit 121 calculates the log ID from the recorded log message and registers it in the event history.
- the unauthorized operation analysis unit 122 detects unauthorized information when an error is set in a message registered in the event history.
- the log processing unit 130 mainly corresponds to the log output control unit in FIG. 1, and includes a log output location determination unit 131 and a log output processing embedding unit 132.
- the log output location determination unit 131 determines the log output location in the script supplied to the client side based on the illegal operation information and the log generation information related to the past log output.
- the log output process embedding unit 132 is for actually embedding the log output process.
- the storage management unit 140 stores log generation information 141, unauthorized operation information 142, and event history information 143.
- the log generation information 141 is information related to log output processing inserted into the script, and is information including a log ID, an insertion location (script file name and ID, number of lines), and a request URL, as illustrated in FIG. is there.
- the illegal operation information is information relating to the illegal operation of the script detected based on the log, and is information including the log ID and the illegal operation content of the log in which the illegal operation is detected as illustrated in FIG.
- the event history is information related to the log received from the client, and includes a log ID and an output log message as illustrated in FIG.
- FIG. 6 illustrates the components of the system and the flow of each operation process.
- the Web browser of the client (script execution device 200) transmits an HTTP request for acquiring a server resource including a JavaScript source to the portal server (log output control device 100) (a1).
- the portal server When the portal server receives the HTTP request (a2), it determines the script language to be sent to the client (a3), and executes the log output processing insertion processing (a4) for JavaScript.
- log generation information (B1) and illegal operation information (B2) are read. If there is illegal operation information, the log generation information of the same log ID is searched from the log ID of the illegal operation information. Then, the execution result of the log output process embedded in the JavaScript line is specified, and the location of the failure in the script is found (b1).
- the script file to be requested is actually read, and the embedding location of the log output process is determined (b2). Increase the number of log output locations around the failure detection location identified earlier.
- log ID event history information
- log output processing is set to be slightly reduced.
- a log message [function name start / end / error / additional information such as variable and signature] is created according to the processing content, and the log output process is inserted (b4-b7).
- a log transmission process to the server is inserted (b8).
- the log generation information (B1) is also recorded in the log generation information table.
- the client browser When response data including script (JavaScript) is received from the portal server (c1), the client browser analyzes and executes HTML and JavaScript script (c2). The browser reloads only the updated JavaScript, and uses the cache for other JavaScript files. When re-reading, the original defined function is overwritten by the function describing the new log output process. When the log transmission process is described in the executed script (c3), the log is transmitted to the portal server (c5).
- script JavaScript
- the portal server receives the log (c6), analyzes the received log (c7), and writes the analysis result in the event history information (C2) (C8).
- An unauthorized operation analysis unit 122 is used for detecting unauthorized information.
- the unauthorized operation analysis unit 122 reads the event history (d1), and if there is an event (d2), determines whether it is an expected result, that is, a correct result (d3).
- determination criterion data in which an event and a normal result are associated with each other may be stored in advance, and the unauthorized operation analysis unit 122 may determine with reference to the determination criterion data. Further, the administrator may make a determination, and the unauthorized operation analysis unit 122 may accept an input of a determination result by the administrator.
- the first effect is that the log output can be changed without reducing the amount of debug log information required in the event of a failure.
- the reason is that the log output location can be determined by the log output location determination unit 131 and the log output processing embedding unit 132 and the log output processing can be embedded.
- the second effect is that the log output location can be changed according to the program execution results. The reason is that by using the log generation information 141 and the illegal operation information 142, the log output processing can be embedded by the log output location determination unit 131 and the log output processing embedding unit 132 in the location where the failure has occurred.
- a role of administrator or general user is assigned to each user, and the operation range and operation characteristics differ depending on the authority (role) of each role.
- a user assigned to the administrator role performs a management operation
- a user assigned to the general user role is mainly a reference operation.
- FIG. 12 is a block diagram of the second embodiment of the present invention.
- processing by the user identification unit 123 is added after processing by the request reception unit 111 in FIG.
- the user identification unit 123 performs user identification using user identification rule information defined in advance.
- the user identification rule information 144 is stored in the storage unit management unit 140.
- the user identification unit 123 executes a method according to the interface and performs user identification.
- the user identification rule describes a rule for identifying a user in the Java language.
- the server executes the registered class file and classifies the user, such as the user ID, the role assigned to the user, and the IP of the terminal to which the request was sent. Get information for.
- the log output location determination unit 131 determines the content to be determined using the user identification information.
- user identification information identification information according to a rule such as role information and user ID
- the user's operation tendency can be determined based on the identified user information. Note that user identification information may be added to the unauthorized operation information. In addition, user identification information may be added to the log generation information.
- the log output location determination unit 131 may determine to insert log output processing into the program requested by the client according to the user identification information. Further, the log output location determination unit 131 may change the insertion range of the log output processing of the program requested from the client according to the user identification information.
- FIG. 14 shows an example of log output processing insertion results when user identification is performed and when user identification is not performed.
- log output processing is embedded in JavaScript for both administrators and general users when an error occurs.
- the log output location determination unit 131 determines that only an administrator has an error from the event history, the illegal operation information, and the log generation information, and only when the request is from the administrator JavaScript Embed log output process in.
- information such as an execution range by an administrator and an execution range by a general user is registered in advance, and an embedding target is narrowed down to an administrator operation, whereby log output locations can also be narrowed down.
- the effect of the second embodiment is that the log output location can be determined more efficiently than the log output location determined only from the illegal operation information.
- the reason is that by using the user information identified by the user identifying unit 123, it is possible to embed the log output process only within the operation range according to the user characteristics.
- FIG. 15 is a configuration diagram of the third embodiment of the present invention.
- processing by the request pattern analysis unit 124 is added after processing by the request reception unit 111 in FIG.
- a list of requests received from the client is accumulated and stored in the storage unit management unit 140.
- the request pattern analysis unit 124 analyzes the pattern of the reception order of requests when an illegal operation has occurred from the received request list and the illegal operation information 142, and associates the request pattern with the illegal operation information.
- the correspondence relationship is stored in the request pattern information 145. For example, when it is analyzed that a failure occurs when requests are transmitted to the server in the order of request A ⁇ request B ⁇ request C, the patterns of these requests are associated with the illegal operation information.
- the log output location determination unit 131 determines the insertion location of the log output process based on the received request pattern. When there is a request having the same pattern as the pattern registered in the request pattern information 145 (for example, request A ⁇ request B ⁇ request C) and there is an illegal operation, the log output location determination unit 131 requests a script. A log output process is inserted at a location corresponding to C.
- the third embodiment controls whether or not to embed log output processing according to the request pattern. By embedding log output processing in a specific pattern, unnecessary log output can be avoided and the load on the server side can be reduced.
- the effect of the third embodiment is that the log output location can be determined more efficiently than the log output location determined only from illegal information.
- the reason is that by using the pattern detected by the request reception pattern analysis unit, it is possible to embed the log output process only in the operation range in accordance with the work flow of the client.
- the apparatus according to the embodiment of the present invention described above may be realized by a CPU (Central Processing Unit) of the apparatus reading and executing an operation program or the like stored in a storage unit, or configured by hardware. May be. Only some functions of the above-described embodiments can be realized by a computer program.
- a CPU Central Processing Unit
- the invention can also be applied to portal products and rich client systems provided in the cloud area and mobile smartphone area.
- the unauthorized operation information includes identification information of a log in which the unauthorized operation is detected,
- the log generation information includes a place where the log output process in the program is inserted, and log identification information corresponding to the inserted log output process,
- the supplementary note 1 wherein an output portion of a log in which an illegal operation is detected in a program requested by a client is identified based on the unauthorized operation information and the log generation information, and a log output process is inserted into the identified portion.
- Appendix 3 Get the client's user identity, The log output control apparatus according to appendix 1 or 2, which controls insertion processing of log output processing of a program requested by a client using user identification information of the client.
- Appendix 4 The log output control device according to appendix 3, wherein in the control of the log output process, the log output process is determined to be inserted into the program requested by the client in accordance with user identification information.
- Appendix 6 The log output control device according to any one of appendix 1 to appendix 5, which controls insertion processing of log output processing of a program requested from the client based on a request pattern received from the client.
- the unauthorized operation information includes identification information of a log in which the unauthorized operation is detected,
- the log generation information includes a place where the log output process in the program is inserted, and log identification information corresponding to the inserted log output process, Item 8.
- the appendix 7 that specifies an output part of a log in which an illegal operation is detected in a program requested by a client based on the illegal operation information and the log generation information, and inserts log output processing at the specified part. Log output control method.
- Appendix 12 The log output control method according to any one of appendix 7 to appendix 11, wherein an insertion process of a log output process of a program requested from the client is controlled based on a request pattern received from the client.
- the unauthorized operation information includes identification information of a log in which the unauthorized operation is detected,
- the log generation information includes a place where the log output process in the program is inserted, and log identification information corresponding to the inserted log output process,
- the computer Based on the unauthorized operation information and the log generation information, the computer identifies the log output location where the unauthorized operation is detected in the program requested by the client, and inserts log output processing at the identified location
- the program according to appendix 13, which causes the process to be executed.
- Appendix 16 The program according to appendix 15, wherein in the control of the insertion process of the log output process, it is determined to insert the log output process into the program requested by the client in accordance with user identification information.
- Appendix 18 In the computer, 18.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
図2は、本発明の第1の実施形態の構成図である。
ポータル製品ではユーザ毎に管理者や一般ユーザのロールが割り当てられ、各ロールの権限(役割)によって操作範囲や操作の特性が異なる。例えば管理者ロールに割り当てられたユーザは管理系の操作を実施し、一般ユーザロールに割り当てられたユーザは参照系の操作が中心になる。ログ出力箇所の分析時にリクエストを送信したユーザのロール情報を用いることで、出力箇所決定時の絞り込み精度を上げることができる。
連続した操作を含む処理の場合、特定の処理シーケンスからの場合のみ操作が失敗するといったケースがある。ログイン後の操作(サーバへの送信リクエスト)のパターンに着目することで、ログ出力箇所の分析時に出力箇所決定時の絞り込み精度を上げることができる。第3の実施形態は、操作A→操作B→操作Cのときは特にエラーが発生しないが、操作A’→操作B’→操作Cのときに操作Cでエラーが出る場合、操作Cまでのリクエストをリストとして保持することで、操作A’→操作B’→操作Cの流れの場合のみ操作Cにログ出力処理を埋め込み、エラーが発生しないケースでの不要なログ出力をなくす。
クライアントが出力したログの履歴と、前記ログから検出されたプログラムの不正動作に関する不正動作情報と、クライアントで実行されるプログラムに挿入されたログ出力処理に関するログ生成情報とを用いて、クライアントから要求されたプログラムにおけるログ出力箇所を動的に制御する
ログ出力制御装置。
前記不正動作情報は、不正動作が検出されたログの識別情報を含み、
前記ログ生成情報は、プログラムにおけるログ出力処理が挿入された場所と、挿入されたログ出力処理に対応するログの識別情報とを含み、
前記不正動作情報と前記ログ生成情報とに基づいて、クライアントから要求されたプログラムにおいて不正動作が検出されたログの出力箇所を特定し、前記特定した箇所にログ出力処理を挿入する
付記1に記載のログ出力制御装置。
クライアントのユーザ識別情報を取得し、
クライアントのユーザ識別情報を用いて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する
付記1又は2に記載のログ出力制御装置。
前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムにログ出力処理を挿入することを決定する
付記3に記載のログ出力制御装置。
前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムのログ出力処理の挿入範囲を変更する
付記3又は付記4に記載のログ出力制御装置。
クライアントから受信したリクエストのパターンに基づいて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する
付記1から付記5のいずれかに記載のログ出力制御装置。
クライアントが出力したログの履歴と、前記ログから検出されたプログラムの不正動作に関する不正動作情報と、クライアントで実行されるプログラムに挿入されたログ出力処理に関するログ生成情報とを用いて、クライアントから要求されたプログラムにおけるログ出力箇所を動的に制御する
ログ出力制御方法。
前記不正動作情報は、不正動作が検出されたログの識別情報を含み、
前記ログ生成情報は、プログラムにおけるログ出力処理が挿入された場所と、挿入されたログ出力処理に対応するログの識別情報とを含み、
前記不正動作情報と前記ログ生成情報とに基づいて、クライアントから要求されたプログラムにおいて不正動作が検出されたログの出力箇所を特定し、前記特定した箇所にログ出力処理を挿入する
付記7に記載のログ出力制御方法。
クライアントのユーザ識別情報を取得し、
クライアントのユーザ識別情報を用いて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する
付記7又は8に記載のログ出力制御方法。
前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムにログ出力処理を挿入することを決定する
付記9に記載のログ出力制御方法。
前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムのログ出力処理の挿入範囲を変更する
付記9又は付記10に記載のログ出力制御方法。
クライアントから受信したリクエストのパターンに基づいて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する
付記7から付記11のいずれかに記載のログ出力制御方法。
コンピュータに、
クライアントが出力したログの履歴と、前記ログから検出されたプログラムの不正動作に関する不正動作情報と、クライアントで実行されるプログラムに挿入されたログ出力処理に関するログ生成情報とを用いて、クライアントから要求されたプログラムにおけるログ出力箇所を動的に制御する処理
を実行させるプログラム。
前記不正動作情報は、不正動作が検出されたログの識別情報を含み、
前記ログ生成情報は、プログラムにおけるログ出力処理が挿入された場所と、挿入されたログ出力処理に対応するログの識別情報とを含み、
前記コンピュータに、前記不正動作情報と前記ログ生成情報とに基づいて、クライアントから要求されたプログラムにおいて不正動作が検出されたログの出力箇所を特定し、前記特定した箇所にログ出力処理を挿入する処理を実行させる付記13に記載のプログラム。
前記コンピュータに、
クライアントのユーザ識別情報を取得する処理、
クライアントのユーザ識別情報を用いて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する処理
を実行させる付記13又は付記14に記載のプログラム。
前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムにログ出力処理を挿入することを決定する
付記15に記載のプログラム。
前記ログ出力処理の挿入処理の制御処理では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムのログ出力処理の挿入範囲を変更する
付記15又は付記16に記載のプログラム。
前記コンピュータに、
クライアントから受信したリクエストのパターンに基づいて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する処理を実行させる付記13から付記17のいずれかに記載のプログラム。
この出願は、2013年3月26日に出願された日本出願特願2013-63593を基礎とする優先権を主張し、その開示の全てをここに取り込む。
110 データ送受信部
120 データ解析部
130 ログ処理部
140 記憶管理部
111 リクエスト受信部
112 ログ受信部
113 レスポンス送信部
121 ログ解析部
122 不正動作解析部
131 ログ出力箇所決定部
132 ログ出力処理埋め込み部
141 ログ生成情報
142 不正動作情報
143 イベント履歴情報
200 スクリプト実行装置
Claims (8)
- クライアントが出力したログの履歴と、前記ログから検出されたプログラムの不正動作に関する不正動作情報と、クライアントで実行されるプログラムに挿入されたログ出力処理に関するログ生成情報とを用いて、クライアントから要求されたプログラムにおけるログ出力箇所を動的に制御する
ログ出力制御装置。 - 前記不正動作情報は、不正動作が検出されたログの識別情報を含み、
前記ログ生成情報は、プログラムにおけるログ出力処理が挿入された場所と、挿入されたログ出力処理に対応するログの識別情報とを含み、
前記不正動作情報と前記ログ生成情報とに基づいて、クライアントから要求されたプログラムにおいて不正動作が検出されたログの出力箇所を特定し、前記特定した箇所にログ出力処理を挿入する
請求項1に記載のログ出力制御装置。 - クライアントのユーザ識別情報を取得し、
クライアントのユーザ識別情報を用いて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する
請求項1又は2に記載のログ出力制御装置。 - 前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムにログ出力処理を挿入することを決定する
請求項3に記載のログ出力制御装置。 - 前記ログ出力処理の挿入処理の制御では、ユーザ識別情報に応じて、前記クライアントから要求されたプログラムのログ出力処理の挿入範囲を変更する
請求項3又は請求項4に記載のログ出力制御装置。 - クライアントから受信したリクエストのパターンに基づいて、クライアントから要求されたプログラムのログ出力処理の挿入処理を制御する
請求項1から請求項5のいずれかに記載のログ出力制御装置。 - クライアントが出力したログの履歴と、前記ログから検出されたプログラムの不正動作に関する不正動作情報と、クライアントで実行されるプログラムに挿入されたログ出力処理に関するログ生成情報とを用いて、クライアントから要求されたプログラムにおけるログ出力箇所を動的に制御する
ログ出力制御方法。 - コンピュータに、
クライアントが出力したログの履歴と、前記ログから検出されたプログラムの不正動作に関する不正動作情報と、クライアントで実行されるプログラムに挿入されたログ出力処理に関するログ生成情報とを用いて、クライアントから要求されたプログラムにおけるログ出力箇所を動的に制御する処理
を実行させるプログラム。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2015508364A JP6015849B2 (ja) | 2013-03-26 | 2014-03-18 | ログ出力制御装置、方法及びプログラム |
US14/772,125 US20160011928A1 (en) | 2013-03-26 | 2014-03-18 | Log output control device, method, and computer-readable recording medium |
CN201480019049.XA CN105074670B (zh) | 2013-03-26 | 2014-03-18 | 日志输出控制设备、方法和计算机可读记录介质 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2013063593 | 2013-03-26 | ||
JP2013-063593 | 2013-03-26 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014156825A1 true WO2014156825A1 (ja) | 2014-10-02 |
Family
ID=51623805
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2014/057311 WO2014156825A1 (ja) | 2013-03-26 | 2014-03-18 | ログ出力制御装置、方法及びプログラム |
Country Status (4)
Country | Link |
---|---|
US (1) | US20160011928A1 (ja) |
JP (1) | JP6015849B2 (ja) |
CN (1) | CN105074670B (ja) |
WO (1) | WO2014156825A1 (ja) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11210362B2 (en) * | 2014-05-31 | 2021-12-28 | International Business Machines Corporation | Script logging for markup language elements |
TWI632453B (zh) * | 2015-10-02 | 2018-08-11 | 緯穎科技服務股份有限公司 | 監測伺服器的方法、監測裝置及監測系統 |
JP6834234B2 (ja) * | 2016-08-10 | 2021-02-24 | 株式会社リコー | 情報処理装置、情報処理方法、及びプログラム |
CN108959051A (zh) * | 2018-06-29 | 2018-12-07 | 深圳市同泰怡信息技术有限公司 | 服务器系统日志收集方法 |
CN112817922B (zh) * | 2021-01-22 | 2023-02-10 | 平安普惠企业管理有限公司 | 日志动态打印方法、装置、计算机设备及存储介质 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030131052A1 (en) * | 2002-01-10 | 2003-07-10 | International Business Machines Corporatioin | Method and system for HTTP time-on-page monitoring without client-side installation |
JP2008140162A (ja) * | 2006-12-01 | 2008-06-19 | Hitachi Ltd | デバッグ情報収集方法 |
JP2009009469A (ja) * | 2007-06-29 | 2009-01-15 | Kyocera Mita Corp | ログ蓄積装置およびログ蓄積プログラム |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6182086B1 (en) * | 1998-03-02 | 2001-01-30 | Microsoft Corporation | Client-server computer system with application recovery of server applications and client applications |
US6230198B1 (en) * | 1998-09-10 | 2001-05-08 | International Business Machines Corporation | Server-to-server event logging |
JP3699919B2 (ja) * | 2001-10-22 | 2005-09-28 | 株式会社アドバンテスト | 光集積回路 |
CN1189822C (zh) * | 2001-11-07 | 2005-02-16 | 华为技术有限公司 | 一种异常逻辑业务仿真测试装置 |
US7801945B1 (en) * | 2002-07-03 | 2010-09-21 | Sprint Spectrum L.P. | Method and system for inserting web content through intermediation between a content server and a client station |
JP4353051B2 (ja) * | 2004-09-30 | 2009-10-28 | ブラザー工業株式会社 | ログ管理プログラム、ログ管理サーバ、及び、ログ管理システム |
JP4164516B2 (ja) * | 2006-05-11 | 2008-10-15 | キヤノン株式会社 | 画像出力装置、履歴管理方法、および履歴管理プログラム |
CN101452408B (zh) * | 2007-11-28 | 2013-07-17 | 国际商业机器公司 | 在软件应用程序中进行错误报告的系统和方法 |
JP5129640B2 (ja) * | 2008-04-08 | 2013-01-30 | キヤノン株式会社 | 出力装置とその制御方法 |
-
2014
- 2014-03-18 WO PCT/JP2014/057311 patent/WO2014156825A1/ja active Application Filing
- 2014-03-18 CN CN201480019049.XA patent/CN105074670B/zh active Active
- 2014-03-18 JP JP2015508364A patent/JP6015849B2/ja active Active
- 2014-03-18 US US14/772,125 patent/US20160011928A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030131052A1 (en) * | 2002-01-10 | 2003-07-10 | International Business Machines Corporatioin | Method and system for HTTP time-on-page monitoring without client-side installation |
JP2008140162A (ja) * | 2006-12-01 | 2008-06-19 | Hitachi Ltd | デバッグ情報収集方法 |
JP2009009469A (ja) * | 2007-06-29 | 2009-01-15 | Kyocera Mita Corp | ログ蓄積装置およびログ蓄積プログラム |
Also Published As
Publication number | Publication date |
---|---|
CN105074670B (zh) | 2017-11-17 |
JP6015849B2 (ja) | 2016-10-26 |
CN105074670A (zh) | 2015-11-18 |
JPWO2014156825A1 (ja) | 2017-02-16 |
US20160011928A1 (en) | 2016-01-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP2010128877A (ja) | ウェブシステムおよび処理記録収集方法 | |
US7970946B1 (en) | Recording and serializing events | |
US20090083714A1 (en) | Remote monitoring of local behavior of network applications | |
JP6015849B2 (ja) | ログ出力制御装置、方法及びプログラム | |
US7203940B2 (en) | Automated installation of an application | |
JP4906672B2 (ja) | ウェブアプリケーションの処理記録方法および処理記録装置 | |
US20150128121A1 (en) | Dynamic application version selection | |
US20130160130A1 (en) | Application security testing | |
EP1576487B1 (en) | Web server hit multiplier and redirector | |
Pellegrino et al. | jäk: Using dynamic analysis to crawl and test modern web applications | |
US9003235B2 (en) | Indicating coverage of web application testing | |
US20080275951A1 (en) | Integrated logging for remote script execution | |
US8949462B1 (en) | Removing personal identifiable information from client event information | |
US9497252B2 (en) | On-demand code version switching | |
US10606730B2 (en) | Networked digital data processor log file viewer | |
WO2013130066A1 (en) | Network service interface analysis | |
US8108513B2 (en) | Remote monitoring of local behavior of network applications | |
US8997076B1 (en) | Auto-updating an application without requiring repeated user authorization | |
US9043440B2 (en) | Automatic WSDL download of client emulation for a testing tool | |
US8898263B2 (en) | Detecting change of settings stored on a remote server by making use of a network filter driver | |
CN111459577A (zh) | 应用安装来源跟踪方法、装置、设备及存储介质 | |
EP2760183A1 (en) | System for detecting hyperlink faults | |
WO2016072973A1 (en) | Web services generation based on client-side code | |
US20090083363A1 (en) | Remote monitoring of local behavior of network applications | |
US20080222157A1 (en) | Information providing method and information providing system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201480019049.X Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 14773782 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14772125 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2015508364 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 14773782 Country of ref document: EP Kind code of ref document: A1 |