WO2013161522A1 - Log collection server, log collection system, log collection method - Google Patents

Log collection server, log collection system, log collection method Download PDF

Info

Publication number
WO2013161522A1
WO2013161522A1 PCT/JP2013/060047 JP2013060047W WO2013161522A1 WO 2013161522 A1 WO2013161522 A1 WO 2013161522A1 JP 2013060047 W JP2013060047 W JP 2013060047W WO 2013161522 A1 WO2013161522 A1 WO 2013161522A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
log
terminal
identification information
error
Prior art date
Application number
PCT/JP2013/060047
Other languages
French (fr)
Japanese (ja)
Inventor
玄 奥山
Original Assignee
日本電気株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電気株式会社 filed Critical 日本電気株式会社
Priority to JP2014512443A priority Critical patent/JP6015750B2/en
Publication of WO2013161522A1 publication Critical patent/WO2013161522A1/en

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/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/0766—Error or fault reporting or storing

Definitions

  • the present invention relates to a log collection server, a log collection system, and a log collection method.
  • the terminal log is necessary.
  • debugging can be performed more efficiently by collecting logs from a plurality of terminals.
  • Patent Document 1 describes a log collection system that identifies a device that collects a log according to an instruction from a developer or the like and collects a log from the identified device. According to this, it becomes possible to collect logs from a plurality of devices.
  • the error log when collecting error logs indicating that an error has occurred uniformly from multiple terminals, the error log has a small amount of information, so it is possible to avoid an increase in the load on the network and the CPU of the terminal. Debugging cannot be performed efficiently.
  • an object of the present invention is to provide a log collection server, a log collection system, and a log collection method that collect logs without increasing the load on the CPU of the network or terminal and enable developers to debug efficiently. There is.
  • the log collection server of the present invention A log collection server that collects logs from multiple terminals, A first database that stores application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed; When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database And a log level change determining unit that identifies the terminal in which the application is installed and notifies the identified terminal to increase the log level indicating the detail level of the log of the application.
  • the log collection system of the present invention A log collection system comprising a plurality of terminals and a log collection server that collects logs from the plurality of terminals,
  • the log collection server A first database that stores application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed;
  • the terminal identification information of the terminal an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database
  • a log level change determination unit that identifies a terminal in which the application is installed and notifies the identified terminal to increase the log level indicating the detail level of the log of the application,
  • Each of the plurality of terminals is When an error occurs in an application, the error log of the application is acquired, and the acquired error log, the terminal identification information of its own terminal, and the application identification information of the application are transmitted to the log collection server.
  • a log acquisition unit When the notification is received from the log collection server, a log level changing unit that raises a log level of an application log to be notified among logs acquired by the log acquisition unit, The log acquisition unit subsequently acquires a detailed log of the application when an error occurs in the application to be notified, the acquired detailed log, the terminal identification information of its own terminal, the application The application identification information is transmitted to the log collection server.
  • the first log collection method of the present invention is: A log collection method by a log collection server that collects logs from multiple terminals, Application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed are associated with each other and stored in the first database, When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database Then, the terminal in which the application is installed is identified, and the identified terminal is notified to increase the log level indicating the detail level of the log of the application.
  • the second log collection method of the present invention is: A log collection method by a log collection system comprising a plurality of terminals and a log collection server that collects logs from the plurality of terminals,
  • the log collection server associates application identification information for identifying an application with terminal identification information for identifying a terminal in which the application is installed, and stores the associated information in the first database.
  • each of the plurality of terminals acquires an error log of the application, the acquired error log, the terminal identification information of its own terminal, the application identification information of the application, To the log collection server,
  • the log collection server receives the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application from any of the plurality of terminals, Referring to the first database, the terminal in which the application is installed is identified, and the identified terminal is notified to increase the log level indicating the detail level of the log of the application,
  • the specific terminal that has received the notification from the log collection server increases the log level of the log of the application that is the target of the notification, and subsequently acquires a detailed log of the application when an error occurs in the application.
  • the acquired detailed log, the terminal identification information of its own terminal, and the application identification information of the application are transmitted to the log collection server.
  • the log collection server increases the log level of the log of the application for a specific terminal on which the application is installed. Notice.
  • logs can be collected without increasing the load on the network and the CPU load on terminals other than the specific terminals. Since logs can be collected, the developer can debug efficiently.
  • FIG. 1 It is a block diagram which shows the structure of the log collection system of one Embodiment of this invention. It is a figure which shows an example of defect management DB shown in FIG. It is a figure which shows an example of policy management DB shown in FIG. It is a figure explaining schematic operation
  • the log collection system of this embodiment includes a log collection server 10 and a plurality of terminals 20. Note that the log collection server 10 and the plurality of terminals 20 are connected to each other via a network (not shown).
  • the log collection server 10 first collects error logs from a plurality of terminals 20 when an application error occurs. Then, the log collection server 10 triggers the collection of the error log from a certain terminal 20, and for the log of the application from the specific terminal 20, the log level indicating the degree of detail of the log is raised, and the detailed log To collect.
  • the error log is a log with a low level of detail that simply indicates that an error has occurred in the terminal 20, and the detailed log is not only an error that has occurred but also the terminal 20 when the error has occurred. It is assumed that the log has a high degree of detail indicating the usage status, communication status, etc. (for example, the content of the operation when an error occurs, the content of the data being communicated, etc.). Therefore, the developer can efficiently perform debugging by using the detailed log.
  • the log collection server 10 includes a communication unit 11, a defect management DB (Data Base) 12, a defect management unit 13, a policy management DB 14, a log level change determination unit 15, and a display unit 16. .
  • the communication unit 11 communicates with the terminal 20.
  • the defect management DB 12 includes an application ID (IDentification) that is application identification information for identifying an application, a terminal ID that is terminal identification information for identifying the terminal 20 in which the application is installed, and the specification (model, OS ( This is a first database that stores terminal specification information indicating Operating System) and the like, defect information generated by the application, and the like in association with each other.
  • application ID IDentification
  • terminal ID that is terminal identification information for identifying the terminal 20 in which the application is installed
  • the specification model, OS ( This is a first database that stores terminal specification information indicating Operating System) and the like, defect information generated by the application, and the like in association with each other.
  • the defect management DB 12 includes the developer ID of the developer, the application ID of the application developed by the developer, the terminal ID of the terminal 20 in which the application is installed, Terminal specification information indicating the specifications (model, OS) of the terminal 20 and defect information (detailed log) indicating defects occurring in the application are stored in association with each other.
  • the defect management unit 13 monitors the application installation status of the plurality of terminals 20 and the reception status of the detailed logs from the plurality of terminals 20 on the network, and moves the contents of the defect management DB 12 based on the monitoring result. Update automatically.
  • the defect management unit 13 acquires the application ID of the application, acquires the terminal ID of the terminal 20 and terminal specification information, and then acquires the application of the application.
  • the information of the terminal 20 is stored in the defect management DB 12 in association with the ID.
  • the defect management unit 13 obtains the application ID of the application, obtains the terminal ID of the terminal 20, and terminal specification information.
  • the information of the terminal 20 associated with the application ID is deleted from the defect management DB 12.
  • the defect management unit 13 stores the detailed log in the defect management DB 12 as defect information.
  • the policy management DB 14 is a second database for managing policies when changing the log level. As shown in FIG. 3, the app ID of the app, and whether or not the log level needs to be changed when an error occurs in the app. When the log level needs to be changed, notification destination specification information indicating the specification of the terminal 20 that notifies the change of the log level is stored in association with each other. Note that the contents of the policy management DB 14 are updated as appropriate by the input of the developer of each application.
  • the specification of the terminal 20 that is the notification destination of the log level change is the same model as the terminal 20 in which an error has occurred (regardless of the OS).
  • all terminals 20 are used.
  • the same model and the same OS as the terminal 20 in which the error has occurred are used.
  • the same OS as the terminal 20 in which the error has occurred is used.
  • the log level change determination unit 15 When the log level change determination unit 15 receives the terminal ID of the terminal 20, the error log indicating that an error has occurred in the application, and the application ID of the application from any of the plurality of terminals 20, the policy level change determination unit 15 With reference to the management DB 14, if the necessity information corresponding to the application ID indicates “necessary”, the corresponding notification destination specification information is extracted.
  • the log level change determination unit 15 refers to the defect management DB 12, and the application indicated by the application ID notified from the terminal 20 is installed, and the specification indicated by the notification destination specification information extracted above
  • the matching terminal 20 is specified, and the application ID of the application and an instruction to increase the log level of the application are notified to the specified terminal 20.
  • the address of the terminal 20 may be managed by the defect management DB 12 in association with the terminal ID of the terminal 20, or may be managed by another DB. After receiving the above notification, the terminal 20 transmits a detailed log to the log collection server 10 when an error occurs in the application.
  • the display unit 16 displays a detailed log of an application stored as defect information in the defect management DB 12. The developer uses the detailed log to debug the application and correct the defect of the application.
  • the terminal 20 includes a communication unit 21, a defect monitoring unit 22, a log acquisition unit 23, and a log level change unit 24.
  • the communication unit 21 communicates with the log collection server 10.
  • the defect monitoring unit 22 monitors defects such as application errors.
  • the log acquisition unit 23 acquires the log of the application, and transmits the log, the terminal ID of the terminal 20 of itself, and the application ID of the application to the log collection server 10. .
  • the log level of the log acquired by the log acquisition unit 23 is set to an error log in the initial state.
  • the log level changing unit 24 When the log level changing unit 24 receives an application ID and an instruction to increase the log level of the application indicated by the application ID from the log collection server 10, the log level changing unit 24 increases the log level of the log acquired by the log acquisition unit 23. To a detailed log. Thereafter, when an error occurs in the application, the log acquisition unit 23 acquires a detailed log of the application and transmits it to the log collection server 10.
  • the log acquisition unit 23 of the terminal (# 1) 20 acquires the error log of the application #A, the error log, the terminal ID of the terminal (# 1) 20, the application ID of the application #A, Is transmitted to the log collection server 10 (step A2).
  • the log level change determination unit 15 of the log collection server 10 refers to the policy management DB 14 of FIG.
  • the notification destination specification information corresponding to the application #A is extracted.
  • the notification destination indicated by the notification destination specification information indicates that the terminal 20 has all specifications.
  • the log level change determination unit 15 of the log collection server 10 refers to the defect management DB 12 to identify all the terminals 20 in which the application #A is installed, and notifies the identified terminals 20 of the log level change.
  • the destination is determined (step A3).
  • the terminal (# 1) 20 in which an error has occurred, the terminal (# 2) 20 of the same model as the terminal (# 1) 20, and the terminal (# 3) 20 of a different model from the terminal (# 1) 20 are used. Are determined as notification destinations.
  • the log level change determination unit 15 of the log collection server 10 applies the application ID of the application #A and the application #A to each of the terminals (# 1) 20 to (# 3) 20 determined above. An instruction to increase the log level is notified (steps A4 to A6).
  • the log level changing unit 24 of each of the terminal (# 1) 20 to the terminal (# 3) 20 raises the log level of the log acquired by the log acquiring unit 23 to make a detailed log (step A7). To A9).
  • the log acquisition unit 23 of the terminal (# 2) 20 acquires the detailed log of the application #A, and the detailed log and the terminal (# 2)
  • the terminal ID of 20 and the application ID of the application #A are transmitted to the log collection server 10 (step A10).
  • the log acquisition unit 23 of the terminal (# 1) 20 confirms whether or not the error log can be transmitted to the user of the terminal (# 1) 20 (step B2). This confirmation is performed by displaying a predetermined confirmation screen on a display unit (not shown).
  • step B3 when an answer indicating that the error log transmission is “permitted” is obtained (step B3), the log acquisition unit 23 of the terminal (# 1) 20 acquires the error log of the application #A, and the error log and the terminal (# 1) The terminal ID of 20 and the application ID of the application #A are transmitted to the log collection server 10 (step B4).
  • the log level change determination unit 15 of the log collection server 10 refers to the policy management DB 14 of FIG.
  • the notification destination specification information corresponding to the application #A is extracted.
  • the notification destination indicated by the notification destination specification information indicates that the terminal 20 has all specifications.
  • the log level change determination unit 15 of the log collection server 10 refers to the defect management DB 12 to identify all the terminals 20 in which the application #A is installed, and notifies the identified terminals 20 of the log level change.
  • the destination is determined (step B5).
  • the terminal (# 1) 20 in which an error has occurred, the terminal (# 2) 20 of the same model as the terminal (# 1) 20, and the terminal (# 3) 20 of a different model from the terminal (# 1) 20 are used. Are determined as notification destinations.
  • the log level change determination unit 15 of the log collection server 10 applies the application ID of the application #A and the application #A to each of the terminals (# 1) 20 to (# 3) 20 determined above. An instruction to increase the log level is notified (steps B6 to B8).
  • the log level changing unit 24 of each of the terminal (# 1) 20 to the terminal (# 3) 20 raises the log level of the log acquired by the log acquiring unit 23 to make a detailed log (step B9). To B11).
  • the log acquisition unit 23 of each of the terminal (# 1) 20 to the terminal (# 3) 20 acquires the detailed log of the application #A when the error of the application #A occurs,
  • the terminal ID of the terminal 20 and the application ID of the application #A are transmitted to the log collection server 10 (steps B12 to B14).
  • the detailed log transmitted to the log collection server 10 is stored as defect information in the defect management DB 12 by the defect management unit 13 and displayed by the display unit 16.
  • the developer of application #A refers to the detailed log of application #A (step B15).
  • the developer of the application #A uses the detailed log to debug the application #A and correct the defect of the application #A.
  • the log collection server 10 when the log collection server 10 collects an error log of an application from any of the plurality of terminals 20, the log collection server 10 stores the application's error log for the specific terminal 20 on which the application is installed. Notify you to increase the log level of the log.
  • the target for collecting the detailed log is only the specific terminal 20
  • the log can be collected without increasing the load on the network or the CPU of the terminal 20 other than the specific terminal 20. Since the detailed log can be collected from 20, the effect that the developer can debug efficiently can be obtained.
  • the log collection server 10 when determining the log level change notification destination, refers to the policy management DB 14 that defines the specification of the terminal 20 as the notification destination.
  • the policy relating to the terminal 20 that is the notification destination of the log level change is managed on the log collection server 10 side, it is possible to easily change the policy.
  • the log collection server 10 updates the defect management DB 12 when an application is installed in any of the plurality of terminals 20.
  • the log collection server 10 refers to the defect management DB 12 and the policy management DB 14 to determine the log level change notification destination.
  • the present invention is not limited to this.
  • the log collection server 10 may refer to only the defect management DB 12 and determine all the terminals 20 in which the application in which the error has occurred are installed as the notification destination.
  • the log collection server 10 also targets the terminal 20 in which the error has occurred as the log level change notification destination, but the terminal 20 in which the error has occurred may be excluded from the target.
  • the log collection server 10 notifies the specific terminal 20 to increase only the log level of the application in which an error has occurred. You may notify it to increase the log level of the app.
  • the log collection server 10 not only increases the log level of the application to the specific terminal 20, but also transmits a detailed log before and after the error occurrence when an error occurs in the application. You may be notified.
  • the method for restoring the log level in the log collection server 10 is not particularly limited.
  • an instruction is given at the timing when the developer corrects a defect in the application (or information necessary for correcting the defect is collected), and the log collection server 10 based on the instruction causes the log level to be based on the log level.
  • a method of notifying it to return can be considered.
  • the log collection server 10 may give an incentive such as giving points to the user who provided the detailed log in order to promote the provision of the detailed log.
  • the log collection server 10 manages the model and OS as the specifications of the terminal 20, but is not limited to this.
  • the vendor of the terminal 20, the language used in the terminal 20, and the terminal 20 You may additionally manage the main countries of use.
  • the log collection server 10 may display the detailed log for each specification of the terminal 20 when displaying the detailed log of the application on the display unit 16. For example, by displaying the detailed log of a certain application by the type of the terminal 20, the OS, the vendor, the language used, the country of use, etc., the developer can debug more efficiently.
  • the terminal 20 confirms whether or not the error log can be transmitted to the user when an error of the application occurs.
  • the timing for confirming whether or not the error log can be transmitted to the user is determined when the application is installed. But it ’s okay.
  • the terminal 20 confirms whether or not the error log can be transmitted to the user. However, the terminal 20 may confirm whether or not the detailed log can be transmitted even when the detailed log is transmitted.
  • the terminal 20 transmits an error log every time an error occurs in the application.
  • the timing at which the error log is transmitted may be a timing when a certain number of error logs are accumulated.

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)
  • Debugging And Monitoring (AREA)

Abstract

This log collection server has: a first data base for storing, in association with each other, application identification information for identifying applications and terminal identification information for identifying terminals in which an application is installed; and a log level modification determination unit, which, upon receiving from any of a plurality of terminals the terminal identification information corresponding to the terminal, an error log representing an error occurring in an application, and the application identification information corresponding to the application, references the first database, specifies the terminal in which the application is installed, and communicates to the specified terminal to increase the log level indicating the level of detail of the log for the application.

Description

ログ収集サーバ、ログ収集システム、ログ収集方法Log collection server, log collection system, and log collection method
　本発明は、ログ収集サーバ、ログ収集システム、ログ収集方法に関する。 The present invention relates to a log collection server, a log collection system, and a log collection method.
　近年、アプリケーション（以下、適宜「アプリ」と称す）をダウンロードして使用する端末（代表的には、スマートフォン）が広く普及している。 In recent years, terminals (typically smartphones) that download and use applications (hereinafter referred to as “apps” as appropriate) have become widespread.
　また、最近は、アプリの開発者がアプリを登録し、そのアプリを端末のユーザがダウンロードすることが可能なサイトも存在している。 Recently, there are also sites where an application developer can register an application and the terminal user can download the application.
　このようなサイトにアプリを登録した開発者は、ある端末でアプリにエラーが発生した場合は、そのアプリのデバッグを行って不具合を修正することになる。 Developers who have registered an application on such a site will correct the problem by debugging the application if an error occurs in the application on a certain terminal.
　ここで、アプリのデバッグを効率良く行うためには、端末のログが必要である。しかし、アプリが様々な機種の端末で利用されることを想定すると、複数の端末からログを収集することで、デバッグをさらに効率良く行うことができると考えられる。 Here, in order to debug the application efficiently, the terminal log is necessary. However, assuming that the application is used on various types of terminals, it is considered that debugging can be performed more efficiently by collecting logs from a plurality of terminals.
　例えば、特許文献１には、開発者等からの指示により、ログを収集する機器を特定し、特定した機器からログを収集するログ収集システムが記載されている。これによれば、複数の機器からログを収集することが可能になる。 For example, Patent Document 1 describes a log collection system that identifies a device that collects a log according to an instruction from a developer or the like and collects a log from the identified device. According to this, it becomes possible to collect logs from a plurality of devices.
特開２０１１－１９７７８５号公報JP 2011-197785 A
　特許文献１に記載されたログ収集システムによれば、複数の端末からログを収集することが可能になる。 According to the log collection system described in Patent Document 1, it becomes possible to collect logs from a plurality of terminals.
　しかし、例えば、複数の端末から一律に、デバックに利用可能な詳細ログを収集する場合、開発者がデバッグを効率良く行うことはできるものの、詳細ログは情報量が多いため、詳細ログの送受信のためにネットワークの負荷が増大し、また、詳細ログの取得のために端末のＣＰＵ（Central　Processing　Unit）の負荷が増大してしまう。 However, for example, when collecting detailed logs that can be used for debugging uniformly from multiple terminals, the developer can perform debugging efficiently, but the detailed log has a large amount of information, so it is possible to send and receive detailed logs. For this reason, the load on the network increases, and the load on the CPU (Central Processing Unit) of the terminal increases in order to acquire a detailed log.
　その一方、複数の端末から一律に、エラーが発生したことを示すエラーログを収集する場合、エラーログは情報量が少ないため、ネットワークや端末のＣＰＵの負荷の増大は回避できるものの、開発者がデバッグを効率良く行うことができなくなってしまう。 On the other hand, when collecting error logs indicating that an error has occurred uniformly from multiple terminals, the error log has a small amount of information, so it is possible to avoid an increase in the load on the network and the CPU of the terminal. Debugging cannot be performed efficiently.
　そこで、本発明の目的は、ネットワークや端末のＣＰＵの負荷が増大することなくログを収集し、開発者が効率よくデバッグを行うことができるログ収集サーバ、ログ収集システム、ログ収集方法を提供することにある。 SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to provide a log collection server, a log collection system, and a log collection method that collect logs without increasing the load on the CPU of the network or terminal and enable developers to debug efficiently. There is.
　本発明のログ収集サーバは、
　複数の端末からログを収集するログ収集サーバであって、
　アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて格納する第１データベースと、
　前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知するログレベル変更決定部と、を有する。 The log collection server of the present invention
A log collection server that collects logs from multiple terminals,
A first database that stores application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed;
When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database And a log level change determining unit that identifies the terminal in which the application is installed and notifies the identified terminal to increase the log level indicating the detail level of the log of the application.
　本発明のログ収集システムは、
　複数の端末と、前記複数の端末からログを収集するログ収集サーバと、を有してなるログ収集システムであって、
　前記ログ収集サーバは、
　アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて格納する第１データベースと、
　前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知するログレベル変更決定部と、を有し、
　前記複数の端末の各々は、
　アプリケーションにエラーが発生した場合、該アプリケーションのエラーログを取得し、取得したエラーログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信するログ取得部と、
　前記ログ収集サーバから前記通知を受信した場合、前記ログ取得部が取得するログのうち前記通知の対象となるアプリケーションのログのログレベルを上げるログレベル変更部と、を有し、
　前記ログ取得部は、以降に、前記通知の対象となるアプリケーションにエラーが発生した場合、該アプリケーションの詳細ログを取得し、取得した詳細ログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信する。 The log collection system of the present invention
A log collection system comprising a plurality of terminals and a log collection server that collects logs from the plurality of terminals,
The log collection server
A first database that stores application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed;
When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database A log level change determination unit that identifies a terminal in which the application is installed and notifies the identified terminal to increase the log level indicating the detail level of the log of the application,
Each of the plurality of terminals is
When an error occurs in an application, the error log of the application is acquired, and the acquired error log, the terminal identification information of its own terminal, and the application identification information of the application are transmitted to the log collection server. A log acquisition unit;
When the notification is received from the log collection server, a log level changing unit that raises a log level of an application log to be notified among logs acquired by the log acquisition unit,
The log acquisition unit subsequently acquires a detailed log of the application when an error occurs in the application to be notified, the acquired detailed log, the terminal identification information of its own terminal, the application The application identification information is transmitted to the log collection server.
　本発明の第１のログ収集方法は、
　複数の端末からログを収集するログ収集サーバによるログ収集方法であって、
　アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて、第１データベースに格納し、
　前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知する。 The first log collection method of the present invention is:
A log collection method by a log collection server that collects logs from multiple terminals,
Application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed are associated with each other and stored in the first database,
When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database Then, the terminal in which the application is installed is identified, and the identified terminal is notified to increase the log level indicating the detail level of the log of the application.
　本発明の第２のログ収集方法は、
　複数の端末と、前記複数の端末からログを収集するログ収集サーバと、を有してなるログ収集システムによるログ収集方法であって、
　前記ログ収集サーバが、アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて、第１データベースに格納し、
　前記複数の端末の各々が、アプリケーションにエラーが発生した場合、該アプリケーションのエラーログを取得し、取得したエラーログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信し、
　前記ログ収集サーバが、前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知し、
　前記ログ収集サーバから前記通知を受信した特定の端末が、前記通知の対象となるアプリケーションのログのログレベルを上げ、以降に、該アプリケーションにエラーが発生した場合、該アプリケーションの詳細ログを取得し、取得した詳細ログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信する。 The second log collection method of the present invention is:
A log collection method by a log collection system comprising a plurality of terminals and a log collection server that collects logs from the plurality of terminals,
The log collection server associates application identification information for identifying an application with terminal identification information for identifying a terminal in which the application is installed, and stores the associated information in the first database.
When an error occurs in the application, each of the plurality of terminals acquires an error log of the application, the acquired error log, the terminal identification information of its own terminal, the application identification information of the application, To the log collection server,
When the log collection server receives the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application from any of the plurality of terminals, Referring to the first database, the terminal in which the application is installed is identified, and the identified terminal is notified to increase the log level indicating the detail level of the log of the application,
The specific terminal that has received the notification from the log collection server increases the log level of the log of the application that is the target of the notification, and subsequently acquires a detailed log of the application when an error occurs in the application. The acquired detailed log, the terminal identification information of its own terminal, and the application identification information of the application are transmitted to the log collection server.
　本発明によれば、ログ収集サーバは、複数の端末のいずれかからアプリのエラーログを収集した場合、そのアプリがインストールされている特定の端末に対し、そのアプリのログのログレベルを上げるよう通知する。 According to the present invention, when an error log of an application is collected from any of a plurality of terminals, the log collection server increases the log level of the log of the application for a specific terminal on which the application is installed. Notice.
　したがって、詳細ログを収集する対象は特定の端末のみとなるため、ネットワークの負荷や、特定の端末以外の端末のＣＰＵの負荷が増大することなくログを収集でき、また、特定の端末からは詳細ログを収集できるため、開発者がデバッグを効率良く行うことができるという効果が得られる。 Therefore, since detailed logs are collected only for specific terminals, logs can be collected without increasing the load on the network and the CPU load on terminals other than the specific terminals. Since logs can be collected, the developer can debug efficiently.
本発明の一実施形態のログ収集システムの構成を示すブロック図である。It is a block diagram which shows the structure of the log collection system of one Embodiment of this invention. 図１に示した不具合管理ＤＢの一例を示す図である。It is a figure which shows an example of defect management DB shown in FIG. 図１に示したポリシ管理ＤＢの一例を示す図である。It is a figure which shows an example of policy management DB shown in FIG. 図１に示したログ収集システムの概略動作を説明する図である。It is a figure explaining schematic operation | movement of the log collection system shown in FIG. 図１に示したログ収集システムの動作を説明するシーケンス図である。It is a sequence diagram explaining operation | movement of the log collection system shown in FIG.
　以下に、本発明を実施するための形態について図面を参照して説明する。 Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings.
　図１に示すように、本実施形態のログ収集システムは、ログ収集サーバ１０と、複数の端末２０と、を有している。なお、ログ収集サーバ１０と複数の端末２０とは、不図示のネットワークを介して互いに接続されているものとする。 As shown in FIG. 1, the log collection system of this embodiment includes a log collection server 10 and a plurality of terminals 20. Note that the log collection server 10 and the plurality of terminals 20 are connected to each other via a network (not shown).
　本実施形態においては、ログ収集サーバ１０は、複数の端末２０から、アプリのエラー発生時には、まずは、エラーログを収集する。そして、ログ収集サーバ１０は、ある端末２０からエラーログを収集したことをトリガとして、特定の端末２０からは、そのアプリのログについては、ログの詳細度を示すログレベルを上げて、詳細ログを収集する。 In this embodiment, the log collection server 10 first collects error logs from a plurality of terminals 20 when an application error occurs. Then, the log collection server 10 triggers the collection of the error log from a certain terminal 20, and for the log of the application from the specific terminal 20, the log level indicating the degree of detail of the log is raised, and the detailed log To collect.
　ここで、エラーログとは、単に端末２０にエラーが発生したことを示した、詳細度が低いログであり、詳細ログとは、エラーが発生しただけでなく、エラーが発生したときの端末２０の利用状況や通信状況等（例えば、エラーが発生したときの操作の内容や、通信していたデータの内容等）を示した、詳細度が高いログであるとする。そのため、開発者は、詳細ログを利用することで、デバックを効率良く行うことが可能となる。 Here, the error log is a log with a low level of detail that simply indicates that an error has occurred in the terminal 20, and the detailed log is not only an error that has occurred but also the terminal 20 when the error has occurred. It is assumed that the log has a high degree of detail indicating the usage status, communication status, etc. (for example, the content of the operation when an error occurs, the content of the data being communicated, etc.). Therefore, the developer can efficiently perform debugging by using the detailed log.
　ログ収集サーバ１０は、通信部１１と、不具合管理ＤＢ（Data　Base）１２と、不具合管理部１３と、ポリシ管理ＤＢ１４と、ログレベル変更決定部１５と、表示部１６と、を有している。 The log collection server 10 includes a communication unit 11, a defect management DB (Data Base) 12, a defect management unit 13, a policy management DB 14, a log level change determination unit 15, and a display unit 16. .
　通信部１１は、端末２０と通信を行う。 The communication unit 11 communicates with the terminal 20.
　不具合管理ＤＢ１２は、アプリを識別するアプリケーション識別情報であるアプリＩＤ（IDentification）、そのアプリがインストールされている端末２０を識別する端末識別情報である端末ＩＤ、その端末２０の仕様（機種、ＯＳ（Operating　System）等）を示す端末仕様情報、そのアプリで発生した不具合情報等を、対応付けて格納する第１データベースである。 The defect management DB 12 includes an application ID (IDentification) that is application identification information for identifying an application, a terminal ID that is terminal identification information for identifying the terminal 20 in which the application is installed, and the specification (model, OS ( This is a first database that stores terminal specification information indicating Operating System) and the like, defect information generated by the application, and the like in association with each other.
　より具体的には、不具合管理ＤＢ１２は、図２に示すように、開発者の開発者ＩＤ、その開発者が開発したアプリのアプリＩＤ、そのアプリがインストールされている端末２０の端末ＩＤ、その端末２０の仕様（機種、ＯＳ）を示す端末仕様情報、そのアプリに発生した不具合を示す不具合情報（詳細ログ）を、対応付けて格納する。 More specifically, as shown in FIG. 2, the defect management DB 12 includes the developer ID of the developer, the application ID of the application developed by the developer, the terminal ID of the terminal 20 in which the application is installed, Terminal specification information indicating the specifications (model, OS) of the terminal 20 and defect information (detailed log) indicating defects occurring in the application are stored in association with each other.
　不具合管理部１３は、ネットワーク上で、複数の端末２０のアプリのインストール状況や、複数の端末２０からの詳細ログの受信状況を監視し、その監視結果に基づいて、不具合管理ＤＢ１２の内容を動的に更新する。 The defect management unit 13 monitors the application installation status of the plurality of terminals 20 and the reception status of the detailed logs from the plurality of terminals 20 on the network, and moves the contents of the defect management DB 12 based on the monitoring result. Update automatically.
　例えば、不具合管理部１３は、ある端末２０にあるアプリがインストールされた場合には、そのアプリのアプリＩＤを取得すると共に、その端末２０の端末ＩＤ、端末仕様情報を取得し、そのアプリのアプリＩＤに対応付けて、その端末２０の情報を不具合管理ＤＢ１２に格納する。 For example, when an application in a certain terminal 20 is installed, the defect management unit 13 acquires the application ID of the application, acquires the terminal ID of the terminal 20 and terminal specification information, and then acquires the application of the application. The information of the terminal 20 is stored in the defect management DB 12 in association with the ID.
　また、不具合管理部１３は、ある端末２０から、あるアプリがアンインストールされた場合には、そのアプリのアプリＩＤを取得すると共に、その端末２０の端末ＩＤ、端末仕様情報を取得し、そのアプリのアプリＩＤに対応付けた、その端末２０の情報を不具合管理ＤＢ１２から削除する。 In addition, when a certain application is uninstalled from a certain terminal 20, the defect management unit 13 obtains the application ID of the application, obtains the terminal ID of the terminal 20, and terminal specification information. The information of the terminal 20 associated with the application ID is deleted from the defect management DB 12.
　また、不具合管理部１３は、ある端末２０から詳細ログを受信した場合には、その詳細ログを不具合情報として不具合管理ＤＢ１２に格納する。 In addition, when receiving a detailed log from a certain terminal 20, the defect management unit 13 stores the detailed log in the defect management DB 12 as defect information.
　ポリシ管理ＤＢ１４は、ログレベルを変更する場合のポリシを管理する第２データベースであり、図３に示すように、アプリのアプリＩＤ、そのアプリにエラーが発生した場合にログレベルの変更の要否を示す要否情報、ログレベル変更が必要な場合に、ログレベルの変更を通知する端末２０の仕様を示す通知先仕様情報を、対応付けて格納する。なお、ポリシ管理ＤＢ１４の内容は、各アプリの開発者の入力によって適宜更新される。 The policy management DB 14 is a second database for managing policies when changing the log level. As shown in FIG. 3, the app ID of the app, and whether or not the log level needs to be changed when an error occurs in the app. When the log level needs to be changed, notification destination specification information indicating the specification of the terminal 20 that notifies the change of the log level is stored in association with each other. Note that the contents of the policy management DB 14 are updated as appropriate by the input of the developer of each application.
　ログレベル変更の通知先となる端末２０の仕様は、例えば、アプリ＃Ａの場合は、エラーが発生した端末２０と同機種（ＯＳは問わない）となる。また、アプリ＃Ｂの場合は、全ての端末２０（機種、ＯＳは問わない）となる。また、アプリ＃Ｄの場合は、エラーが発生した端末２０と同機種でかつ同ＯＳとなる。また、アプリ＃Ｅの場合は、エラーが発生した端末２０と同ＯＳ（機種は問わない）となる。 For example, in the case of application #A, the specification of the terminal 20 that is the notification destination of the log level change is the same model as the terminal 20 in which an error has occurred (regardless of the OS). In the case of the application #B, all terminals 20 (regardless of model and OS) are used. In the case of the application #D, the same model and the same OS as the terminal 20 in which the error has occurred. Further, in the case of the application #E, the same OS as the terminal 20 in which the error has occurred (regardless of the model).
　ログレベル変更決定部１５は、複数の端末２０のいずれかから、その端末２０の端末ＩＤと、アプリにエラーが発生した旨のエラーログと、そのアプリのアプリＩＤと、を受信した場合、ポリシ管理ＤＢ１４を参照し、アプリＩＤに対応する要否情報が「要」を示していれば、対応する通知先仕様情報を抽出する。 When the log level change determination unit 15 receives the terminal ID of the terminal 20, the error log indicating that an error has occurred in the application, and the application ID of the application from any of the plurality of terminals 20, the policy level change determination unit 15 With reference to the management DB 14, if the necessity information corresponding to the application ID indicates “necessary”, the corresponding notification destination specification information is extracted.
　続いて、ログレベル変更決定部１５は、不具合管理ＤＢ１２を参照して、端末２０から通知されたアプリＩＤが示すアプリがインストールされており、かつ、上記で抽出した通知先仕様情報が示す仕様と一致する端末２０を特定し、特定した端末２０に対し、そのアプリのアプリＩＤと、そのアプリのログレベルを上げる旨の指示を通知する。なお、端末２０のアドレスは、その端末２０の端末ＩＤと対応付けて、不具合管理ＤＢ１２で管理しても良いし、別のＤＢで管理しても良い。上記の通知を受けた端末２０は、以降、そのアプリにエラーが発生した場合は、詳細ログをログ収集サーバ１０に送信する。 Subsequently, the log level change determination unit 15 refers to the defect management DB 12, and the application indicated by the application ID notified from the terminal 20 is installed, and the specification indicated by the notification destination specification information extracted above The matching terminal 20 is specified, and the application ID of the application and an instruction to increase the log level of the application are notified to the specified terminal 20. The address of the terminal 20 may be managed by the defect management DB 12 in association with the terminal ID of the terminal 20, or may be managed by another DB. After receiving the above notification, the terminal 20 transmits a detailed log to the log collection server 10 when an error occurs in the application.
　表示部１６は、不具合管理ＤＢ１２に不具合情報として格納されたアプリの詳細ログを表示する。開発者は、その詳細ログを利用して、そのアプリのデバッグを行い、そのアプリの不具合を修正することになる。 The display unit 16 displays a detailed log of an application stored as defect information in the defect management DB 12. The developer uses the detailed log to debug the application and correct the defect of the application.
　端末２０は、通信部２１と、不具合監視部２２と、ログ取得部２３と、ログレベル変更部２４と、を有している。 The terminal 20 includes a communication unit 21, a defect monitoring unit 22, a log acquisition unit 23, and a log level change unit 24.
　通信部２１は、ログ収集サーバ１０と通信を行う。 The communication unit 21 communicates with the log collection server 10.
　不具合監視部２２は、アプリのエラー等の不具合を監視する。 The defect monitoring unit 22 monitors defects such as application errors.
　ログ取得部２３は、アプリにエラーが発生した場合、そのアプリのログを取得し、そのログと、自己の端末２０の端末ＩＤと、そのアプリのアプリＩＤと、をログ収集サーバ１０に送信する。 When an error occurs in the application, the log acquisition unit 23 acquires the log of the application, and transmits the log, the terminal ID of the terminal 20 of itself, and the application ID of the application to the log collection server 10. .
　ここで、ログ取得部２３が取得するログのログレベルは、初期状態では、エラーログに設定されている。 Here, the log level of the log acquired by the log acquisition unit 23 is set to an error log in the initial state.
　ログレベル変更部２４は、ログ収集サーバ１０から、アプリＩＤと、そのアプリＩＤが示すアプリのログレベルを上げる旨の指示と、を受信すると、ログ取得部２３が取得するログのログレベルを上げて、詳細ログにする。以降、ログ取得部２３は、そのアプリにエラーが発生した場合、そのアプリの詳細ログを取得し、ログ収集サーバ１０に送信する。 When the log level changing unit 24 receives an application ID and an instruction to increase the log level of the application indicated by the application ID from the log collection server 10, the log level changing unit 24 increases the log level of the log acquired by the log acquisition unit 23. To a detailed log. Thereafter, when an error occurs in the application, the log acquisition unit 23 acquires a detailed log of the application and transmits it to the log collection server 10.
　以下、本実施形態のログ収集システムの動作について説明する。 Hereinafter, the operation of the log collection system of this embodiment will be described.
　まず、本実施形態のログ収集システムの動作の概要を、図４を参照して説明する。 First, an outline of the operation of the log collection system of this embodiment will be described with reference to FIG.
　図４に示すように、端末（＃１）２０において、あるアプリ（ここでは、アプリ＃Ａとする）のエラーが発生したとする（ステップＡ１）。 As shown in FIG. 4, it is assumed that an error of a certain application (here, application #A) occurs in the terminal (# 1) 20 (step A1).
　この場合、端末（＃１）２０のログ取得部２３は、アプリ＃Ａのエラーログを取得し、そのエラーログと、端末（＃１）２０の端末ＩＤと、アプリ＃ＡのアプリＩＤと、をログ収集サーバ１０に送信する（ステップＡ２）。 In this case, the log acquisition unit 23 of the terminal (# 1) 20 acquires the error log of the application #A, the error log, the terminal ID of the terminal (# 1) 20, the application ID of the application #A, Is transmitted to the log collection server 10 (step A2).
　これを受けて、ログ収集サーバ１０のログレベル変更決定部１５は、図３のポリシ管理ＤＢ１４を参照する。ここでは、アプリ＃Ａに対応する要否情報が「要」を示しているので、アプリ＃Ａに対応する通知先仕様情報を抽出する。ここでは、通知先仕様情報が示す通知先は、全ての仕様の端末２０であることを示している。 In response, the log level change determination unit 15 of the log collection server 10 refers to the policy management DB 14 of FIG. Here, since the necessity information corresponding to the application #A indicates “necessary”, the notification destination specification information corresponding to the application #A is extracted. Here, the notification destination indicated by the notification destination specification information indicates that the terminal 20 has all specifications.
　続いて、ログ収集サーバ１０のログレベル変更決定部１５は、不具合管理ＤＢ１２を参照して、アプリ＃Ａがインストールされている全ての端末２０を特定し、特定した端末２０をログレベル変更の通知先として決定する（ステップＡ３）。ここでは、エラーが発生した端末（＃１）２０と、端末（＃１）２０と同機種の端末（＃２）２０と、端末（＃１）２０とは異機種の端末（＃３）２０と、を通知先として決定したとする。 Subsequently, the log level change determination unit 15 of the log collection server 10 refers to the defect management DB 12 to identify all the terminals 20 in which the application #A is installed, and notifies the identified terminals 20 of the log level change. The destination is determined (step A3). Here, the terminal (# 1) 20 in which an error has occurred, the terminal (# 2) 20 of the same model as the terminal (# 1) 20, and the terminal (# 3) 20 of a different model from the terminal (# 1) 20 are used. Are determined as notification destinations.
　続いて、ログ収集サーバ１０のログレベル変更決定部１５は、上記で決定した端末（＃１）２０～端末（＃３）２０の各々に対し、アプリ＃ＡのアプリＩＤと、アプリ＃Ａのログレベルを上げる旨の指示と、を通知する（ステップＡ４～Ａ６）。 Subsequently, the log level change determination unit 15 of the log collection server 10 applies the application ID of the application #A and the application #A to each of the terminals (# 1) 20 to (# 3) 20 determined above. An instruction to increase the log level is notified (steps A4 to A6).
　これを受けて、端末（＃１）２０～端末（＃３）２０の各々のログレベル変更部２４は、ログ取得部２３が取得するログのログレベルを上げて、詳細ログにする（ステップＡ７～Ａ９）。 In response to this, the log level changing unit 24 of each of the terminal (# 1) 20 to the terminal (# 3) 20 raises the log level of the log acquired by the log acquiring unit 23 to make a detailed log (step A7). To A9).
　以降、例えば、端末（＃２）２０において、アプリ＃Ａのエラーが発生すると、端末（＃２）２０のログ取得部２３は、アプリ＃Ａの詳細ログを取得し、その詳細ログと、端末（＃２）２０の端末ＩＤと、アプリ＃ＡのアプリＩＤと、をログ収集サーバ１０に送信する（ステップＡ１０）。 Thereafter, for example, when an error of the application #A occurs in the terminal (# 2) 20, the log acquisition unit 23 of the terminal (# 2) 20 acquires the detailed log of the application #A, and the detailed log and the terminal (# 2) The terminal ID of 20 and the application ID of the application #A are transmitted to the log collection server 10 (step A10).
　続いて、本実施形態のログ収集システムの動作の詳細を、図５を参照して説明する。 Next, details of the operation of the log collection system of this embodiment will be described with reference to FIG.
　図５に示すように、端末（＃１）２０において、あるアプリ（ここでは、アプリ＃Ａとする）のエラーが発生したとする（ステップＢ１）。 As shown in FIG. 5, it is assumed that an error of a certain application (here, application #A) occurs in the terminal (# 1) 20 (step B1).
　この場合、端末（＃１）２０のログ取得部２３は、端末（＃１）２０のユーザに対し、エラーログ送信の可否を確認する（ステップＢ２）。この確認は、所定の確認画面を不図示の表示部に表示すること等で行う。 In this case, the log acquisition unit 23 of the terminal (# 1) 20 confirms whether or not the error log can be transmitted to the user of the terminal (# 1) 20 (step B2). This confirmation is performed by displaying a predetermined confirmation screen on a display unit (not shown).
　ここで、エラーログ送信が「可」の回答が得られると（ステップＢ３）、端末（＃１）２０のログ取得部２３は、アプリ＃Ａのエラーログを取得し、そのエラーログと、端末（＃１）２０の端末ＩＤと、アプリ＃ＡのアプリＩＤと、をログ収集サーバ１０に送信する（ステップＢ４）。 Here, when an answer indicating that the error log transmission is “permitted” is obtained (step B3), the log acquisition unit 23 of the terminal (# 1) 20 acquires the error log of the application #A, and the error log and the terminal (# 1) The terminal ID of 20 and the application ID of the application #A are transmitted to the log collection server 10 (step B4).
　これを受けて、ログ収集サーバ１０のログレベル変更決定部１５は、図３のポリシ管理ＤＢ１４を参照する。ここでは、アプリ＃Ａに対応する要否情報が「要」を示しているので、アプリ＃Ａに対応する通知先仕様情報を抽出する。ここでは、通知先仕様情報が示す通知先は、全ての仕様の端末２０であることを示している。 In response, the log level change determination unit 15 of the log collection server 10 refers to the policy management DB 14 of FIG. Here, since the necessity information corresponding to the application #A indicates “necessary”, the notification destination specification information corresponding to the application #A is extracted. Here, the notification destination indicated by the notification destination specification information indicates that the terminal 20 has all specifications.
　続いて、ログ収集サーバ１０のログレベル変更決定部１５は、不具合管理ＤＢ１２を参照して、アプリ＃Ａがインストールされている全ての端末２０を特定し、特定した端末２０をログレベル変更の通知先として決定する（ステップＢ５）。ここでは、エラーが発生した端末（＃１）２０と、端末（＃１）２０と同機種の端末（＃２）２０と、端末（＃１）２０とは異機種の端末（＃３）２０と、を通知先として決定したとする。 Subsequently, the log level change determination unit 15 of the log collection server 10 refers to the defect management DB 12 to identify all the terminals 20 in which the application #A is installed, and notifies the identified terminals 20 of the log level change. The destination is determined (step B5). Here, the terminal (# 1) 20 in which an error has occurred, the terminal (# 2) 20 of the same model as the terminal (# 1) 20, and the terminal (# 3) 20 of a different model from the terminal (# 1) 20 are used. Are determined as notification destinations.
　続いて、ログ収集サーバ１０のログレベル変更決定部１５は、上記で決定した端末（＃１）２０～端末（＃３）２０の各々に対し、アプリ＃ＡのアプリＩＤと、アプリ＃Ａのログレベルを上げる旨の指示と、を通知する（ステップＢ６～Ｂ８）。 Subsequently, the log level change determination unit 15 of the log collection server 10 applies the application ID of the application #A and the application #A to each of the terminals (# 1) 20 to (# 3) 20 determined above. An instruction to increase the log level is notified (steps B6 to B8).
　これを受けて、端末（＃１）２０～端末（＃３）２０の各々のログレベル変更部２４は、ログ取得部２３が取得するログのログレベルを上げて、詳細ログにする（ステップＢ９～Ｂ１１）。 In response to this, the log level changing unit 24 of each of the terminal (# 1) 20 to the terminal (# 3) 20 raises the log level of the log acquired by the log acquiring unit 23 to make a detailed log (step B9). To B11).
　以降、端末（＃１）２０～端末（＃３）２０の各々のログ取得部２３は、アプリ＃Ａのエラーが発生すると、アプリ＃Ａの詳細ログを取得し、その詳細ログと、自己の端末２０の端末ＩＤと、アプリ＃ＡのアプリＩＤと、をログ収集サーバ１０に送信する（ステップＢ１２～Ｂ１４）。ログ収集サーバ１０に送信された詳細ログは、不具合管理部１３により不具合情報として不具合管理ＤＢ１２に格納され、表示部１６により表示される。 Thereafter, the log acquisition unit 23 of each of the terminal (# 1) 20 to the terminal (# 3) 20 acquires the detailed log of the application #A when the error of the application #A occurs, The terminal ID of the terminal 20 and the application ID of the application #A are transmitted to the log collection server 10 (steps B12 to B14). The detailed log transmitted to the log collection server 10 is stored as defect information in the defect management DB 12 by the defect management unit 13 and displayed by the display unit 16.
　その後、アプリ＃Ａの開発者は、アプリ＃Ａの詳細ログを参照する（ステップＢ１５）。アプリ＃Ａの開発者は、その詳細ログを利用して、アプリ＃Ａのデバッグを行い、アプリ＃Ａの不具合を修正することになる。 Thereafter, the developer of application #A refers to the detailed log of application #A (step B15). The developer of the application #A uses the detailed log to debug the application #A and correct the defect of the application #A.
　上述したように本実施形態においては、ログ収集サーバ１０は、複数の端末２０のいずれかからアプリのエラーログを収集した場合、そのアプリがインストールされている特定の端末２０に対し、そのアプリのログのログレベルを上げるよう通知する。 As described above, in this embodiment, when the log collection server 10 collects an error log of an application from any of the plurality of terminals 20, the log collection server 10 stores the application's error log for the specific terminal 20 on which the application is installed. Notify you to increase the log level of the log.
　したがって、詳細ログを収集する対象は特定の端末２０のみとなるため、ネットワークの負荷や、特定の端末２０以外の端末２０のＣＰＵの負荷が増大することなくログを収集でき、また、特定の端末２０からは詳細ログを収集できるため、開発者がデバッグを効率良く行うことができるという効果が得られる。 Therefore, since the target for collecting the detailed log is only the specific terminal 20, the log can be collected without increasing the load on the network or the CPU of the terminal 20 other than the specific terminal 20. Since the detailed log can be collected from 20, the effect that the developer can debug efficiently can be obtained.
　また、本実施形態においては、ログ収集サーバ１０は、ログレベル変更の通知先を決定するに際し、通知先となる端末２０の仕様を定めたポリシ管理ＤＢ１４を参照する。 In the present embodiment, when determining the log level change notification destination, the log collection server 10 refers to the policy management DB 14 that defines the specification of the terminal 20 as the notification destination.
　このように、ログ収集サーバ１０側で、ログレベル変更の通知先となる端末２０に関するポリシを管理するため、ポリシを変更し易いという効果が得られる。 As described above, since the policy relating to the terminal 20 that is the notification destination of the log level change is managed on the log collection server 10 side, it is possible to easily change the policy.
　また、本実施形態においては、ログ収集サーバ１０は、複数の端末２０のいずれかにアプリがインストールされた場合には、不具合管理ＤＢ１２を更新する。 In this embodiment, the log collection server 10 updates the defect management DB 12 when an application is installed in any of the plurality of terminals 20.
　したがって、複数の端末２０のアプリのインストール状況の変化に対して、動的に追従することができるという効果が得られる。 Therefore, it is possible to dynamically follow the change in the application installation status of the plurality of terminals 20.
　以上、実施形態を参照して本発明を説明したが、本発明は上記実施形態に限定されるものではない。本発明の構成や詳細には、本発明の範囲内で当業者が理解し得る様々な変更をすることができる。 The present invention has been described above with reference to the embodiments, but the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the present invention.
　例えば、本実施形態においては、ログ収集サーバ１０は、不具合管理ＤＢ１２およびポリシ管理ＤＢ１４を参照して、ログレベル変更の通知先を決定しているが、これに限定されない。例えば、ログ収集サーバ１０は、不具合管理ＤＢ１２のみを参照し、エラーが発生したアプリがインストールされている全ての端末２０を通知先として決定しても良い。 For example, in this embodiment, the log collection server 10 refers to the defect management DB 12 and the policy management DB 14 to determine the log level change notification destination. However, the present invention is not limited to this. For example, the log collection server 10 may refer to only the defect management DB 12 and determine all the terminals 20 in which the application in which the error has occurred are installed as the notification destination.
　また、本実施形態においては、ログ収集サーバ１０は、エラーが発生した端末２０もログレベル変更の通知先の対象としているが、エラーが発生した端末２０については対象から外しても良い。 In the present embodiment, the log collection server 10 also targets the terminal 20 in which the error has occurred as the log level change notification destination, but the terminal 20 in which the error has occurred may be excluded from the target.
　また、本実施形態においては、ログ収集サーバ１０は、特定の端末２０に対し、エラーが発生したアプリのみのログレベルを上げるよう通知していたが、特定の端末２０にインストールされている全てのアプリのログレベルを上げるよう通知しても良い。 In the present embodiment, the log collection server 10 notifies the specific terminal 20 to increase only the log level of the application in which an error has occurred. You may notify it to increase the log level of the app.
　また、本実施形態においては、ログ収集サーバ１０は、特定の端末２０に対し、アプリのログレベルを上げるだけでなく、そのアプリにエラーが発生した場合にはエラー発生前後の詳細ログを送信するよう通知しても良い。 Further, in the present embodiment, the log collection server 10 not only increases the log level of the application to the specific terminal 20, but also transmits a detailed log before and after the error occurrence when an error occurs in the application. You may be notified.
　また、本実施形態においては、ログ収集サーバ１０において、ログレベルを元に戻す方法は特に限定されない。例えば、開発者がアプリの不具合を修正した（あるいは、不具合修正のために必要な情報を収集した）タイミングにて指示を行い、その指示を基に、ログ収集サーバ１０が、ログレベルを元に戻すよう通知を行う方法などが考えられる。 In the present embodiment, the method for restoring the log level in the log collection server 10 is not particularly limited. For example, an instruction is given at the timing when the developer corrects a defect in the application (or information necessary for correcting the defect is collected), and the log collection server 10 based on the instruction causes the log level to be based on the log level. A method of notifying it to return can be considered.
　また、本実施形態においては、ログ収集サーバ１０は、詳細ログの提供の促進を図るため、詳細ログを提供してくれたユーザに対し、ポイントを付与する等のインセンティブを与えても良い。 In the present embodiment, the log collection server 10 may give an incentive such as giving points to the user who provided the detailed log in order to promote the provision of the detailed log.
　また、本実施形態においては、ログ収集サーバ１０は、端末２０の仕様として、機種およびＯＳを管理しているが、これに限定されず、端末２０のベンダー、端末２０の使用言語、端末２０の主な使用国等を追加で管理しても良い。 In the present embodiment, the log collection server 10 manages the model and OS as the specifications of the terminal 20, but is not limited to this. The vendor of the terminal 20, the language used in the terminal 20, and the terminal 20 You may additionally manage the main countries of use.
　また、本実施形態においては、ログ収集サーバ１０は、アプリの詳細ログを表示部１６に表示する際に、端末２０の仕様別に詳細ログを表示しても良い。例えば、あるアプリの詳細ログを、端末２０の機種別、ＯＳ別、ベンダー別、使用言語別、使用国別等で表示することにより、開発者はさらに効率良くデバッグを行うことができる。 In the present embodiment, the log collection server 10 may display the detailed log for each specification of the terminal 20 when displaying the detailed log of the application on the display unit 16. For example, by displaying the detailed log of a certain application by the type of the terminal 20, the OS, the vendor, the language used, the country of use, etc., the developer can debug more efficiently.
　また、本実施形態においては、端末２０は、アプリのエラー発生時に、ユーザにエラーログ送信の可否を確認しているが、ユーザにエラーログ送信の可否を確認するタイミングは、アプリのインストール時などでも良い。 In the present embodiment, the terminal 20 confirms whether or not the error log can be transmitted to the user when an error of the application occurs. The timing for confirming whether or not the error log can be transmitted to the user is determined when the application is installed. But it ’s okay.
　また、本実施形態においては、端末２０は、ユーザにエラーログ送信の可否を確認しているが、詳細ログの送信時にも、ユーザに詳細ログ送信の可否を確認しても良い。 In the present embodiment, the terminal 20 confirms whether or not the error log can be transmitted to the user. However, the terminal 20 may confirm whether or not the detailed log can be transmitted even when the detailed log is transmitted.
　また、本実施形態においては、端末２０は、アプリにエラーが発生する度に、エラーログを送信しているが、エラーログを送信するタイミングは、エラーログが一定数溜まったタイミングでも良い。 In the present embodiment, the terminal 20 transmits an error log every time an error occurs in the application. However, the timing at which the error log is transmitted may be a timing when a certain number of error logs are accumulated.
　本出願は、２０１２年４月２４日に出願された日本出願特願２０１２－９８６７１を基礎とする優先権を主張し、その開示の全てをここに取り込む。 This application claims priority based on Japanese Patent Application No. 2012-98671 filed on April 24, 2012, the entire disclosure of which is incorporated herein.

Claims (9)

  1. 　複数の端末からログを収集するログ収集サーバであって、
    　アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて格納する第１データベースと、
    　前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知するログレベル変更決定部と、を有するログ収集サーバ。     A log collection server that collects logs from multiple terminals,
    A first database that stores application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed;
    When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database And a log level change determining unit that identifies a terminal in which the application is installed and notifies the identified terminal to increase the log level indicating the detail level of the log of the application.
  2. 　前記アプリケーション識別情報と、該アプリケーション識別情報が示すアプリケーションにエラーが発生した場合にログレベルの変更の要否を示す要否情報と、ログレベルの変更を通知する端末の仕様を示す通知先仕様情報と、を対応付けて格納する第２データベースをさらに有し、
    　前記第１データベースは、
    　前記アプリケーション識別情報と、前記端末識別情報と、該端末識別情報が示す端末の仕様を示す端末仕様情報と、を対応付けて格納し、
    　前記ログレベル変更決定部は、
    　前記複数の端末のいずれかから、前記端末識別情報と、前記アプリケーション識別情報と、前記エラーログと、を受信した場合、前記第２データベースを参照して、該アプリケーション識別情報に対応する前記要否情報が要を示していれば、該アプリケーション識別情報に対応する前記通知先仕様情報を抽出し、
    　続いて前記第１データベースを参照し、該アプリケーション識別情報が示すアプリケーションがインストールされており、かつ、前記通知先仕様情報が示す仕様と一致する端末を特定し、特定した端末に対し、該アプリケーションのログのログレベルを上げるよう通知する、請求項１に記載のログ収集サーバ。     The application identification information, the necessity information indicating whether or not the log level needs to be changed when an error occurs in the application indicated by the application identification information, and the notification destination specification information indicating the specification of the terminal that notifies the log level change And a second database for storing them in association with each other,
    The first database is
    Storing the application identification information, the terminal identification information, and the terminal specification information indicating the specification of the terminal indicated by the terminal identification information in association with each other;
    The log level change determination unit
    When the terminal identification information, the application identification information, and the error log are received from any of the plurality of terminals, the necessity information corresponding to the application identification information is referred to the second database. If the information indicates the key, extract the notification destination specification information corresponding to the application identification information,
    Subsequently, referring to the first database, a terminal that has the application indicated by the application identification information installed and matches the specification indicated by the notification destination specification information is identified, and the application is identified with respect to the identified terminal. The log collection server according to claim 1, wherein notification is made to increase the log level of the log.
  3. 　前記ログレベル変更決定部は、
    　前記特定した端末に対し、該端末にインストールされている全てのアプリケーションのログのログレベルを上げるよう通知する、請求項１または２に記載のログ収集サーバ。     The log level change determination unit
    The log collection server according to claim 1 or 2, wherein the specified terminal is notified to increase the log level of logs of all applications installed in the terminal.
  4. 　前記ログレベル変更決定部は、
    　前記特定した端末に対し、前記アプリケーションにエラーが発生した場合には、エラー発生前後のログのログレベルを上げた詳細ログを送信するよう通知する、請求項１から３のいずれか１項に記載のログ収集サーバ。     The log level change determination unit
    4. The notification according to claim 1, wherein, when an error occurs in the application, the specified terminal is notified to transmit a detailed log in which a log level of a log before and after the occurrence of the error is increased. Log collection server.
  5. 　表示部をさらに有し、
    　前記第１データベースは、
    　前記アプリケーション識別情報と、前記端末識別情報と、前記端末仕様情報と、前記アプリケーション識別情報が示すアプリケーションについて前記複数の端末から収集した、ログレベルを上げた詳細ログと、を対応付けて格納し、
    　前記表示部は、
    　前記第１データベースに格納された前記詳細ログを表示する、請求項１から４のいずれか１項に記載のログ収集サーバ。     A display unit;
    The first database is
    The application identification information, the terminal identification information, the terminal specification information, and the detailed log with the increased log level collected from the plurality of terminals for the application indicated by the application identification information are stored in association with each other,
    The display unit
    The log collection server according to any one of claims 1 to 4, wherein the detailed log stored in the first database is displayed.
  6. 　前記複数の端末のいずれかにて、アプリケーションがインストールされた場合、および、前記複数の端末のいずれかから、前記詳細ログを収集した場合、前記第１データベースを更新する管理部をさらに有する、請求項５に記載のログ収集サーバ。 A management unit that updates the first database when an application is installed on any of the plurality of terminals and when the detailed log is collected from any of the plurality of terminals; Item 6. The log collection server according to item 5.
  7. 　複数の端末と、前記複数の端末からログを収集するログ収集サーバと、を有してなるログ収集システムであって、
    　前記ログ収集サーバは、
    　アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて格納する第１データベースと、
    　前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知するログレベル変更決定部と、を有し、
    　前記複数の端末の各々は、
    　アプリケーションにエラーが発生した場合、該アプリケーションのエラーログを取得し、取得したエラーログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信するログ取得部と、
    　前記ログ収集サーバから前記通知を受信した場合、前記ログ取得部が取得するログのうち前記通知の対象となるアプリケーションのログのログレベルを上げるログレベル変更部と、を有し、
    　前記ログ取得部は、以降に、前記通知の対象となるアプリケーションにエラーが発生した場合、該アプリケーションの詳細ログを取得し、取得した詳細ログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信する、ログ収集システム。     A log collection system comprising a plurality of terminals and a log collection server that collects logs from the plurality of terminals,
    The log collection server
    A first database that stores application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed;
    When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database A log level change determination unit that identifies a terminal in which the application is installed and notifies the identified terminal to increase the log level indicating the detail level of the log of the application,
    Each of the plurality of terminals is
    When an error occurs in an application, the error log of the application is acquired, and the acquired error log, the terminal identification information of its own terminal, and the application identification information of the application are transmitted to the log collection server. A log acquisition unit;
    When the notification is received from the log collection server, a log level changing unit that raises a log level of an application log to be notified among logs acquired by the log acquisition unit,
    The log acquisition unit subsequently acquires a detailed log of the application when an error occurs in the application to be notified, the acquired detailed log, the terminal identification information of its own terminal, the application A log collection system for transmitting the application identification information to the log collection server.
  8. 　複数の端末からログを収集するログ収集サーバによるログ収集方法であって、
    　アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて、第１データベースに格納し、
    　前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知する、ログ収集方法。     A log collection method by a log collection server that collects logs from multiple terminals,
    Application identification information for identifying an application and terminal identification information for identifying a terminal in which the application is installed are associated with each other and stored in the first database,
    When the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application are received from any of the plurality of terminals, refer to the first database Then, a log collection method for identifying a terminal in which the application is installed and notifying the identified terminal to increase the log level indicating the detail level of the log of the application.
  9. 　複数の端末と、前記複数の端末からログを収集するログ収集サーバと、を有してなるログ収集システムによるログ収集方法であって、
    　前記ログ収集サーバが、アプリケーションを識別するアプリケーション識別情報と、該アプリケーションがインストールされている端末を識別する端末識別情報と、を対応付けて、第１データベースに格納し、
    　前記複数の端末の各々が、アプリケーションにエラーが発生した場合、該アプリケーションのエラーログを取得し、取得したエラーログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信し、
    　前記ログ収集サーバが、前記複数の端末のいずれかから、該端末の前記端末識別情報と、アプリケーションにエラーが発生した旨のエラーログと、該アプリケーションの前記アプリケーション識別情報と、を受信した場合、前記第１データベースを参照して、該アプリケーションがインストールされている端末を特定し、特定した端末に対し、該アプリケーションのログの詳細度を示すログレベルを上げるよう通知し、
    　前記ログ収集サーバから前記通知を受信した特定の端末が、前記通知の対象となるアプリケーションのログのログレベルを上げ、以降に、該アプリケーションにエラーが発生した場合、該アプリケーションの詳細ログを取得し、取得した詳細ログと、自己の端末の前記端末識別情報と、該アプリケーションの前記アプリケーション識別情報と、を前記ログ収集サーバに送信する、ログ収集方法。     A log collection method by a log collection system comprising a plurality of terminals and a log collection server that collects logs from the plurality of terminals,
    The log collection server associates application identification information for identifying an application with terminal identification information for identifying a terminal in which the application is installed, and stores the associated information in the first database.
    When an error occurs in the application, each of the plurality of terminals acquires an error log of the application, the acquired error log, the terminal identification information of its own terminal, the application identification information of the application, To the log collection server,
    When the log collection server receives the terminal identification information of the terminal, an error log indicating that an error has occurred in the application, and the application identification information of the application from any of the plurality of terminals, Referring to the first database, the terminal in which the application is installed is identified, and the identified terminal is notified to increase the log level indicating the detail level of the log of the application,
    The specific terminal that has received the notification from the log collection server increases the log level of the log of the application that is the target of the notification, and subsequently acquires a detailed log of the application when an error occurs in the application. A log collection method for transmitting the acquired detailed log, the terminal identification information of its own terminal, and the application identification information of the application to the log collection server.
PCT/JP2013/060047 2012-04-24 2013-04-02 Log collection server, log collection system, log collection method WO2013161522A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2014512443A JP6015750B2 (en) 2012-04-24 2013-04-02 Log collection server, log collection system, and log collection method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2012098671 2012-04-24
JP2012-098671 2012-04-24

Publications (1)

Publication Number Publication Date
WO2013161522A1 true WO2013161522A1 (en) 2013-10-31

Family

ID=49482854

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/060047 WO2013161522A1 (en) 2012-04-24 2013-04-02 Log collection server, log collection system, log collection method

Country Status (2)

Country Link
JP (1) JP6015750B2 (en)
WO (1) WO2013161522A1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201844A (en) * 2016-06-29 2016-12-07 北京智能管家科技有限公司 A kind of log collecting method and device
CN106484593A (en) * 2016-09-29 2017-03-08 北京小米移动软件有限公司 Log processing method, device and electronic equipment
JP2019207517A (en) * 2018-05-29 2019-12-05 株式会社リコー Information processing system, information processing device, and management server
JP2020149245A (en) * 2019-03-12 2020-09-17 株式会社リコー Network device, network communication system, and network control program

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000222247A (en) * 1999-02-04 2000-08-11 Oki Electric Ind Co Ltd Event fault monitoring device
JP2011100325A (en) * 2009-11-06 2011-05-19 Nec Corp Device and method for managing log
JP2011138461A (en) * 2010-01-04 2011-07-14 Nec Corp Failure information management system, portable terminal device, server and method for managing failure information, program and recording medium
JP2012198796A (en) * 2011-03-22 2012-10-18 Nec Corp Log collection system, device, method and program

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000222247A (en) * 1999-02-04 2000-08-11 Oki Electric Ind Co Ltd Event fault monitoring device
JP2011100325A (en) * 2009-11-06 2011-05-19 Nec Corp Device and method for managing log
JP2011138461A (en) * 2010-01-04 2011-07-14 Nec Corp Failure information management system, portable terminal device, server and method for managing failure information, program and recording medium
JP2012198796A (en) * 2011-03-22 2012-10-18 Nec Corp Log collection system, device, method and program

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201844A (en) * 2016-06-29 2016-12-07 北京智能管家科技有限公司 A kind of log collecting method and device
CN106201844B (en) * 2016-06-29 2019-01-01 北京智能管家科技有限公司 A kind of log collecting method and device
CN106484593A (en) * 2016-09-29 2017-03-08 北京小米移动软件有限公司 Log processing method, device and electronic equipment
JP2019207517A (en) * 2018-05-29 2019-12-05 株式会社リコー Information processing system, information processing device, and management server
JP7119582B2 (en) 2018-05-29 2022-08-17 株式会社リコー Information processing system and management server
JP2020149245A (en) * 2019-03-12 2020-09-17 株式会社リコー Network device, network communication system, and network control program

Also Published As

Publication number Publication date
JP6015750B2 (en) 2016-10-26
JPWO2013161522A1 (en) 2015-12-24

Similar Documents

Publication Publication Date Title
US11960388B2 (en) System and method for data collection and analysis of information relating to mobile applications
EP2994828B1 (en) Apps store with integrated test support
US10180893B2 (en) System and method for providing additional functionality to developer side application in an integrated development environment
US10516748B2 (en) IoT device identification
US20140289719A1 (en) Automatic version management
EP3671512A1 (en) Automated software vulnerability determination
US20150058679A1 (en) Application resource utilizaton management
CN105323269A (en) Method for updating APP in Android system, terminal and storage medium
JP6015750B2 (en) Log collection server, log collection system, and log collection method
CN109254914A (en) Software development kit test method, system, computer installation and readable storage medium storing program for executing
US10176069B2 (en) Quorum based aggregator detection and repair
US8381205B2 (en) Co-resident software performance tracking
US20160125330A1 (en) Rolling upgrade of metric collection and aggregation system
CN114401187A (en) Gray scale distribution method and device, computer equipment and storage medium
JP2012230451A (en) Network terminal failure handling system, terminal device, server device, network terminal failure handling method and program
US20140324891A1 (en) Apparatus and method for managing application error
CN108304321A (en) A kind of method, system and device creating front and back end exploitation joint debugging environment
CN115080834A (en) Failure detection method and device for push link, electronic equipment and storage medium
JP2011170458A (en) Monitoring system and monitoring method
JP2010066840A (en) Remote maintenance system, method, and program
US20240193254A1 (en) Systems, devices, and methods for tracking remote equipment location and utilization of computing devices
JP2017054318A (en) Management device, management method, and management program
CN116795544A (en) Hadoop resource sensing method and device, electronic equipment and storage medium
CN114816346A (en) Business project development method and device, electronic equipment and storage medium
CN117827624A (en) Function test method, device and storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13780559

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2014512443

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: 13780559

Country of ref document: EP

Kind code of ref document: A1