WO2013161522A1 - Serveur de collecte de journaux, système de collecte de journaux, procédé de collecte de journaux - Google Patents

Serveur de collecte de journaux, système de collecte de journaux, procédé de collecte de journaux 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
English (en)
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/ja
Publication of WO2013161522A1 publication Critical patent/WO2013161522A1/fr

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

L'invention concerne un serveur de collecte de journaux comprenant : une première base de données permettant d'enregistrer, en association les unes les autres, des informations d'identification d'applications permettant d'identifier des applications et des informations d'identification de terminaux permettant d'identifier des terminaux dans lesquels est installée une application ; et une unité de détermination de modification de niveau de journal qui, dès réception des informations d'identification de terminaux correspondant au terminal à partir d'un quelconque terminal d'une pluralité de terminaux, un journal d'erreurs représentant une erreur survenant dans une application, ainsi que des informations d'identification d'applications correspondant à l'application, fait référence à la première base de données, spécifie le terminal dans lequel est installée l'application, et indique au terminal spécifié d'augmenter le niveau de journal indiquant le niveau de détail du journal pour l'application.
PCT/JP2013/060047 2012-04-24 2013-04-02 Serveur de collecte de journaux, système de collecte de journaux, procédé de collecte de journaux WO2013161522A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2014512443A JP6015750B2 (ja) 2012-04-24 2013-04-02 ログ収集サーバ、ログ収集システム、ログ収集方法

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 (fr) 2013-10-31

Family

ID=49482854

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2013/060047 WO2013161522A1 (fr) 2012-04-24 2013-04-02 Serveur de collecte de journaux, système de collecte de journaux, procédé de collecte de journaux

Country Status (2)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201844A (zh) * 2016-06-29 2016-12-07 北京智能管家科技有限公司 一种日志收集方法及装置
CN106484593A (zh) * 2016-09-29 2017-03-08 北京小米移动软件有限公司 日志处理方法、装置及电子设备
JP2019207517A (ja) * 2018-05-29 2019-12-05 株式会社リコー 情報処理システム、情報処理装置、及び管理サーバ
JP2020149245A (ja) * 2019-03-12 2020-09-17 株式会社リコー ネットワーク機器、ネットワーク通信システム、及び、ネットワーク制御プログラム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000222247A (ja) * 1999-02-04 2000-08-11 Oki Electric Ind Co Ltd イベント障害監視装置
JP2011100325A (ja) * 2009-11-06 2011-05-19 Nec Corp ログ管理装置及びログ管理方法
JP2011138461A (ja) * 2010-01-04 2011-07-14 Nec Corp 障害情報管理システム、携帯端末装置、障害情報管理サーバ、障害情報管理方法、該プログラムおよび記録媒体
JP2012198796A (ja) * 2011-03-22 2012-10-18 Nec Corp ログ収集システム、装置、方法及びプログラム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000222247A (ja) * 1999-02-04 2000-08-11 Oki Electric Ind Co Ltd イベント障害監視装置
JP2011100325A (ja) * 2009-11-06 2011-05-19 Nec Corp ログ管理装置及びログ管理方法
JP2011138461A (ja) * 2010-01-04 2011-07-14 Nec Corp 障害情報管理システム、携帯端末装置、障害情報管理サーバ、障害情報管理方法、該プログラムおよび記録媒体
JP2012198796A (ja) * 2011-03-22 2012-10-18 Nec Corp ログ収集システム、装置、方法及びプログラム

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106201844A (zh) * 2016-06-29 2016-12-07 北京智能管家科技有限公司 一种日志收集方法及装置
CN106201844B (zh) * 2016-06-29 2019-01-01 北京智能管家科技有限公司 一种日志收集方法及装置
CN106484593A (zh) * 2016-09-29 2017-03-08 北京小米移动软件有限公司 日志处理方法、装置及电子设备
JP2019207517A (ja) * 2018-05-29 2019-12-05 株式会社リコー 情報処理システム、情報処理装置、及び管理サーバ
JP7119582B2 (ja) 2018-05-29 2022-08-17 株式会社リコー 情報処理システム、及び管理サーバ
JP2020149245A (ja) * 2019-03-12 2020-09-17 株式会社リコー ネットワーク機器、ネットワーク通信システム、及び、ネットワーク制御プログラム

Also Published As

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

Similar Documents

Publication Publication Date Title
US20210248062A1 (en) System and Method for Data Collection and Analysis of Information Relating to Mobile Applications
EP2994828B1 (fr) Magasin d'applications avec soutien d'essais intégré
US11070638B2 (en) IoT device identification
US10180893B2 (en) System and method for providing additional functionality to developer side application in an integrated development environment
JP2015505097A (ja) 修復送達システムのためのコンピュータ実装プロセス、コンピュータ・プログラム製品、および装置
US20140289719A1 (en) Automatic version management
US20150058679A1 (en) Application resource utilizaton management
JP6015750B2 (ja) ログ収集サーバ、ログ収集システム、ログ収集方法
WO2016197737A1 (fr) Procédé, appareil et système de traitement d'auto-vérification
CN109254914A (zh) 软件开发包测试方法、系统、计算机装置及可读存储介质
US10176069B2 (en) Quorum based aggregator detection and repair
US20100333066A1 (en) Method and system for managing software issues
EP3671512A1 (fr) Détermination automatique de vulnérabilité de logiciel
US8381205B2 (en) Co-resident software performance tracking
CN114401187A (zh) 灰度发布方法、装置、计算机设备和存储介质
JP2018060279A (ja) リコール対象機器判定システム
CN109391658B (zh) 一种账号数据同步方法及其设备、存储介质、终端
JP2012230451A (ja) ネットワーク端末故障対応システム、端末装置、サーバ装置、ネットワーク端末故障対応方法及びプログラム
US20140324891A1 (en) Apparatus and method for managing application error
US20160125330A1 (en) Rolling upgrade of metric collection and aggregation system
JP2011170458A (ja) 監視システムおよび監視方法
JP2017054318A (ja) 管理装置、管理方法および管理プログラム
CN116795544A (zh) Hadoop资源感知方法和装置、电子设备和存储介质
CN114816346A (zh) 一种业务项目开发方法、装置、电子设备及存储介质
CN115080834A (zh) 推送链路的故障检测方法、装置、电子设备及存储介质

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