WO2016038272A1 - Mecanisme haute performance pour generation d'informations de journalisation d'un processus informatique - Google Patents
Mecanisme haute performance pour generation d'informations de journalisation d'un processus informatique Download PDFInfo
- Publication number
- WO2016038272A1 WO2016038272A1 PCT/FR2015/052267 FR2015052267W WO2016038272A1 WO 2016038272 A1 WO2016038272 A1 WO 2016038272A1 FR 2015052267 W FR2015052267 W FR 2015052267W WO 2016038272 A1 WO2016038272 A1 WO 2016038272A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- logging
- thread
- information
- application
- log
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3612—Software analysis for verifying properties of programs by runtime analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3068—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data format conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3404—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for parallel or distributed programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/865—Monitoring of software
Definitions
- the invention relates to the field of process logging within a software application running on a set of information processing devices. More particularly, the invention relates to a method for process logging in the case of a software application operating with multiple processes and / or threads.
- English-language logging is a mechanism for exporting running information from a software application to the developer, tester, or other people on a technical team that is responsible for supporting the application. software application. This information makes it possible to reveal certain dysfunctions, or, these known, to facilitate the determination of the cause and the correction.
- the export of logging information can be done during software application development phases, or in the test phase within a community of testers, but also in the production phase. The logging information is then exported to the users of the application, but can be "uploaded” in one way or another to the technical team in charge of the software.
- the logging information can be exported to a display terminal, or to a memory, in particular a "hard disk” type mass memory.
- Some "critical" software applications require highly constrained response times but require a large amount of computation. To reconcile these two requirements, they are conventionally deployed on systems composed of a set of data processing devices. Parallel programming techniques are then used to take advantage of these processing devices.
- logging requires inputs / outputs, to a display terminal or a memory, for example.
- Input / output mechanisms are expensive in terms of processing time.
- logging impacts the performance of a software application.
- the object of the present invention is to improve the state of the art by providing mechanisms to enable efficient logging, including for critical software applications, including parallel software applications.
- the present invention provides a logging method comprising steps of: Execute a process with at least one application thread and at least one journal thread on a set of information processing devices;
- the invention comprises one or more of the following features which can be used separately or in partial combination with one another or in total combination with one another:
- said at least one processing element comprises an output wire belonging to said process.
- said at least one processing element comprises a thread of a logging process separate from said process, said application thread transmits said first information to said at least one log thread asynchronously through a communication interface.
- said communication interface and said publishing interface are of socket type and conform to the ZeroMQ library.
- said at least one application thread waits for the initialization of said at least one journaling thread prior to continuing execution, and wherein said logging son initializes by synchronizing with a subset of said at least one processing element, said first log information includes a name and a level.
- said at least one logging thread is completed and restarted within the initial parent process.
- said at least one logging son when said at least one logging son receives a signal, it publishes second logging information related to said signal and then triggers the processing code associated with said signal.
- said application son when said application son receives a signal, it transmits first logging information related to said signal to said at least one logging thread, waits for a given time and causes the termination of said process.
- FIG 1 shows schematically an example of implementation of the invention.
- FIG. 2 diagrammatically represents a finite state machine according to one embodiment of the invention.
- a software application consists of one or more processes.
- a process, or "process” in English, can be seen as a program running by an information processing system (or computer).
- a process can be defined as comprising:
- a set of instructions to execute which can be in the ROM, but most often loaded from the mass memory to the RAM;
- Resources such as network ports.
- the same process can have multiple threads or "threads" in English, or a light task or process. Unlike a process, a thread does not have its own virtual memory but shares it with all threads in the same process.
- an application has two processes P 1; P 2 .
- the process Pi comprises three execution threads F 1; F 2 , F 3 . Whatever it is not shown in the figure, the process P 2 may also include several threads.
- the threads can have a life different from that of the processes, and, a fortiori, the duration of execution of the application: the son can be executed dynamically during the execution of the processes and completed at any time, once the task for which they are planned completed.
- Figure 1 therefore illustrates a situation at a given time of the execution of the software application.
- the execution threads F 1; F 2 will be called “application son", to distinguish them from the log son or F j and the output wire F s which will be described later.
- the information processing system for executing the software application is typically a parallel system consisting of a set of information processing devices.
- Each information processing device may be for example a microprocessor with associated circuits (memory ...), and the system is then formed of a set of interconnected microprocessors.
- a microprocessor with associated circuits (memory 8)
- the system is then formed of a set of interconnected microprocessors.
- Another example is that of a single microprocessor forming a system, and composed of a set of physical cores.
- Such a microprocessor is generally called multi-core (or "multicore" in English).
- the logging thread when it starts, it creates:
- An I c communication interface enabling the reception of the first logging information of the application threads F 1; F 2 , that is to say the main application thread and any son he can then create;
- processing elements An I P publishing interface to publish second logging information to processing elements
- processing elements the threads and processes.
- the logging process Pj and the output thread Fs form such processing elements that are likely to receive the logging information.
- these interfaces are of the "socket” type.
- a “socket” is a communication mechanism well known to those skilled in the art, appeared on operating systems of "Unix” type but today present under most operating systems.
- ZeroMQ can be ZeroMQ compliant.
- ZeroMQ is a middleware platform that is inserted between the underlying operating system and applications to provide additional infrastructure services independent of the operating system.
- CORBA Common Object Request Broker Architecture
- ZeroMQ brings a great ease of use and very good performances: the code is very short for the threads application, generating little overload of treatment, and the processing within the ZeroMQ library is also very fast.
- ZeroMQ meets the requirements of the invention and allows to fulfill the desired services without adding a detrimental treatment.
- the communication interface is an asynchronous interface: it allows the application thread to send logging information and then continue processing, without having to wait for an acknowledgment from the logging thread Fj .
- this communication interface I c may be of the push / pull type.
- the logging thread creates a "pull" type socket.
- the application threads F 1; F 2 can then transmit the logging information through a "push" socket connected to the "pull" socket of the logging thread Fj.
- an inter-wire and intra-process transport protocol such as the "inproc" protocol can be implemented.
- This protocol allows the transmission of messages between wires within the same process: the information is transmitted directly by the memory belonging to the context associated with the process. This mechanism therefore does not generate inputs / outputs, and therefore contributes to the high performance of the method according to the invention.
- the publication interface I P may comprise a pub type socket created within the logging thread Fj.
- the processing elements (processes or threads) Pj, F s can create sub-type sockets in order to subscribe ("subscribe" in English) to the "pub" socket of the logging thread Pj.
- the "publish-subscribe" model managed by ZeroMQ thus makes it possible to transmit messages to all previously subscribed processing elements.
- the application thread waits for the initialization of this logging thread Fj before continuing its execution.
- the thread (main) of the process Pi may specify a number of processing elements that must receive logging information. He will receive a acknowledgment by the logging thread Fj only when this number of subscriber processing elements is reached. Once the acknowledgment is received, the thread can then continue execution. Likewise, the log thread Fj initializes by synchronizing with the number of processing elements that are to receive logging information.
- journal thread Fj can publish synchronization information. Upon receipt, the processing elements that received them will transmit an acknowledgment to the logging thread. This can count the acknowledgments received and easily determine when the specified number is reached.
- This synchronization phase makes it possible to ensure that no logging information is lost: in fact, establishing the connection between the logging thread Fj and the processing elements may take a certain amount of time. In addition, the processing elements themselves may be initializing as well. During this time, if the log thread Fj immediately started sending log information, the log information would be lost due to the lack of acknowledgment in the transmission of the published log information from the receiving processing elements. . This absence of acknowledgment makes it possible to reach good performances
- This number of elements determines a subset of all subscriber processing elements, because once the initialization phase is complete, it is quite possible that other processing elements subscribe to Fj journaling publications. However, these may miss the first publications of the journal thread Fj.
- the logging method according to the invention comprises a step of executing the process Pi. As previously described, this execution involves the execution of at least one application thread Fi and a log thread Fj. In the case of a process written in C language, this application thread Fi may correspond to the execution of the main () function.
- the application son (s) execute the code of the software application.
- the method then consists in detecting a log event in the one or more application threads and immediately transmitting first logging information el, e2 to the logging thread Fj.
- Detecting a log event is a known technique, which involves inserting milestones (or "loggers") into the code to trigger a log event when certain conditions are met. These conditions can be simply the passage through a specific point of the code (to allow to follow the progress of the code), or a situation of error, etc.
- This logging information generated by the application thread F 1; F 2 are here called “first logging information" to distinguish them from the second logging information that will be published by the journal thread Fj.
- This information may have only one name and one level. According to one embodiment, these first information only include this name and this level.
- the name can be a string identifying a milestone within the application code.
- the level is usually an integer, identifying a degree of criticality of the event. This level can belong to a previously defined list which can include: "Critical”: to indicate a critical error which, in general, causes the termination of the process.
- This first information may also include:
- timestamp a date of occurrence of the log event
- kernel thread identifier (“kernel")
- software application name the application name
- file name the application code line number
- the application wire immediately transmits these first logging information to the logging wire Fj through the communication interface I c .
- this interface is asynchronous and does not require acknowledgment. No lock is set up either, so that once the transmission is done (and without worrying about reception by the logging wire), the application thread F 1; F 2 can continue application processing immediately.
- no further processing is applied between detecting a logging event and sending the first logging information.
- only a formatting process is applied.
- the application thread implements input / output mechanisms: these mechanisms are implemented by the log thread Fj, and therefore off the application thread F 1; F 2 .
- the application code is divided into modules. Each module is associated with a name or identifier, which can be embedded in the name of the logging milestone.
- the journal thread Fj asynchronously receives the first logging information sent by the application son or F 1; F 2. Its role is then to develop second logging information from the first logging information received from the application son, and possibly additional information. This additional information may be information common to all the application threads of the process.
- the processing implemented by the log thread Fj can be limited to the development of these second logging information.
- the development can comprise on the one hand the addition of any additional information but also formatting, according to a predefined format allowing its operation by processing elements.
- This formatting can be very simple and only consist of formatting so that the second information is in a format independent of the computer language used.
- This second information is then published by the journal thread Fj through the publication interface I P. They can then be received by one or more processing elements F s , Pj previously registered with the logging wire, as previously described.
- These processing elements may comprise an output thread F s belonging to the process P1.
- This output wire may be provided for producing an output of the second logging information on a display terminal (screen %), in a file stored on a memory, especially a mass memory, etc.
- the processing elements may also include a logging process Pj distinct from said process Pi.
- This process can also implement output mechanisms in the same way as an output thread F s .
- the log thread Fj and the eventual output thread Fs are completed and then restarted within the initial parent process Pi.
- two wires are not restarted (they go into a "finalized” state, as will be described later).
- the child process will trigger the execution of an "exec ()” function that will replace and “overwrite” the content of the child process with a new program: it is therefore unnecessary to trigger an automatic restart of journaling and output threads, and even counterproductive.
- Forking or fork, in English, is the mechanism for creating a new process in a software application running under a "Unix" operating system, or compliant with the Posix standard.
- the mechanism implemented by the invention makes it possible to avoid them.
- management of a state machine can be implemented to better manage fork () duplication.
- FIG. 2 illustrates such a state machine of the log thread Fj. It is considered that the thread Fj can be in 5 main states. These states are classic:
- duplication may be permitted and not give rise to particular processing.
- the arrow “fork ()” loops back to the current state.
- the duplication causes the transition to the finalizing state to complete the logging thread.
- the son Fj and F s can be restarted.
- the threads are restarted in the state where they were before the duplication, that is, the "initialized” state.
- the threads start in a state "Unset”: the application thread of the child process must then initiate its initialization to make it change state.
- a process Pi operating under a system of the Posix or unix type can receive signals. These signals can be provided to terminate the process, such as SIGINT, SIGTERM, SIGQUIT, SIGSEGV, SIGBUS signals.
- the log thread Fj When such a signal is received by the log thread Fj, it may choose to treat or not according to their nature. For example, the signals
- SIGINT, SIGTERM and SIGQUIT can be considered as being to be processed by the application thread and therefore not considered by the journal thread. On the other hand, it can consider other types of signals such as SIGSEGV and SIGBUS signals.
- the log thread Fj may consider it to be a log event, and then publish logging information related to that signal.
- Normal The normal processing of a signal is provided by a processing code, typically called “handler”, and associated with this signal.
- the normal processing of this signal SIGSEGV or SIGBUS causes the termination of the process.
- the process adopts the expected behavior of being terminated, but it is also ensured that a logging takes place related to the reception of this event: also, if a processing element subscribes to the logging thread , it will be informed of the cause of the termination of the process Pi. If a signal is received by the application thread, it can determine that it is a log event. To do this, a specific code can be associated with the signal as "handler": on receipt of a given signal, it is this specific code that is triggered by the operating system.
- This specific code allows the immediate transmission of (first) logging information to the logging thread through the communication interface I c .
- This code can also provide a wait time for the journal thread to develop second log information from this first logging information and publish it through the publish interface.
- the subscriber process elements can be informed of the cause of termination of the process.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- Mathematical Physics (AREA)
- Multimedia (AREA)
- Debugging And Monitoring (AREA)
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP15763052.6A EP3191961A1 (fr) | 2014-09-10 | 2015-08-25 | Mecanisme haute performance pour generation d'informations de journalisation d'un processus informatique |
US15/510,638 US11874758B2 (en) | 2014-09-10 | 2015-08-25 | High-performance mechanism for generating logging information within application thread in respect of a logging event of a computer process |
JP2017534008A JP6498770B2 (ja) | 2014-09-10 | 2015-08-25 | コンピュータプロセスに関するロギング情報を生成するための高性能機構 |
CN201580060764.2A CN107003927A (zh) | 2014-09-10 | 2015-08-25 | 用于产生关于计算机进程的日志记录信息的高性能机制 |
IL251095A IL251095A0 (en) | 2014-09-10 | 2017-03-12 | A high-performance mechanism for generating input information about a computer process |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR1458511 | 2014-09-10 | ||
FR1458511A FR3025627B1 (fr) | 2014-09-10 | 2014-09-10 | Mecanisme haute performance pour generation d'informations de journalisation d'un processus informatique |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016038272A1 true WO2016038272A1 (fr) | 2016-03-17 |
Family
ID=52450276
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/FR2015/052267 WO2016038272A1 (fr) | 2014-09-10 | 2015-08-25 | Mecanisme haute performance pour generation d'informations de journalisation d'un processus informatique |
Country Status (7)
Country | Link |
---|---|
US (1) | US11874758B2 (fr) |
EP (1) | EP3191961A1 (fr) |
JP (1) | JP6498770B2 (fr) |
CN (1) | CN107003927A (fr) |
FR (1) | FR3025627B1 (fr) |
IL (1) | IL251095A0 (fr) |
WO (1) | WO2016038272A1 (fr) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106649071A (zh) * | 2016-12-30 | 2017-05-10 | 广州华多网络科技有限公司 | 进程内部日志上报的方法和装置 |
WO2019129957A1 (fr) | 2017-12-27 | 2019-07-04 | Bull Sas | Procede de controle de la gestion des traces d'evenements dans l'execution d'une application informatique sur une machine informatique |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113434362A (zh) * | 2021-06-24 | 2021-09-24 | 广州欢网科技有限责任公司 | Android程序发生异常时自动预警的方法及装置 |
CN113190418A (zh) * | 2021-07-01 | 2021-07-30 | 奇安信科技集团股份有限公司 | 日志接收方法、装置、电子设备及存储介质 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7086064B1 (en) * | 2000-05-27 | 2006-08-01 | International Business Machines Corporation | Performance profiling tool |
US20130036404A1 (en) * | 2011-08-01 | 2013-02-07 | Vmware, Inc. | Testing of a software system using instrumentation at a logging module |
US8499299B1 (en) * | 2010-06-29 | 2013-07-30 | Ca, Inc. | Ensuring deterministic thread context switching in virtual machine applications |
US8667472B1 (en) * | 2010-07-29 | 2014-03-04 | Disney Enterprises, Inc. | System and method of instrumenting code for in-production monitoring |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5870588A (en) * | 1995-10-23 | 1999-02-09 | Interuniversitair Micro-Elektronica Centrum(Imec Vzw) | Design environment and a design method for hardware/software co-design |
US6256775B1 (en) * | 1997-12-11 | 2001-07-03 | International Business Machines Corporation | Facilities for detailed software performance analysis in a multithreaded processor |
FI114663B (fi) * | 2001-12-20 | 2004-11-30 | Nokia Corp | Menetelmä ja järjestelmä käyttöjärjestelmätoimintojen suorittamiseksi sekä elektroniikkalaite |
JP4686226B2 (ja) * | 2005-03-22 | 2011-05-25 | 株式会社東芝 | 駅務中継機 |
US7661036B1 (en) * | 2005-11-08 | 2010-02-09 | Oakley Networks | Cache for collecting events on a monitored computer |
JP5050357B2 (ja) * | 2006-01-25 | 2012-10-17 | 富士通株式会社 | ロギング情報管理方法およびロギング情報管理システムおよびロギング情報管理手段 |
US20080250412A1 (en) * | 2007-04-06 | 2008-10-09 | Elizabeth An-Li Clark | Cooperative process-wide synchronization |
CN101414255A (zh) * | 2007-10-19 | 2009-04-22 | 国际商业机器公司 | 日志事件处理方法与设备 |
KR20100022171A (ko) * | 2008-08-19 | 2010-03-02 | 삼성전자주식회사 | 스레드 지향 로깅 시스템에서 로그 저장 방법 및 장치 |
CN101763593A (zh) * | 2009-12-17 | 2010-06-30 | 中国电力科学研究院 | 一种实现系统审计日志的方法及装置 |
US9384112B2 (en) * | 2010-07-01 | 2016-07-05 | Logrhythm, Inc. | Log collection, structuring and processing |
CN103154893B (zh) * | 2010-10-05 | 2016-05-04 | 富士通株式会社 | 多核处理器系统、监视控制方法以及监视控制程序 |
CN102455889B (zh) * | 2010-10-29 | 2014-03-26 | 金蝶软件(中国)有限公司 | 一种获取进程输出日志的方法、装置及企业系统 |
WO2013016299A1 (fr) * | 2011-07-22 | 2013-01-31 | Yilin Wang | Système d'événements et procédés d'utilisation |
JP5906883B2 (ja) * | 2012-03-28 | 2016-04-20 | 富士通株式会社 | ログ出力装置、ログ出力方法およびログ出力プログラム |
US9202047B2 (en) * | 2012-05-14 | 2015-12-01 | Qualcomm Incorporated | System, apparatus, and method for adaptive observation of mobile device behavior |
US10192261B2 (en) * | 2012-08-23 | 2019-01-29 | Openet Telecom Ltd. | System and method for performing offline revenue assurance of data usage |
US20140237474A1 (en) * | 2013-02-19 | 2014-08-21 | Appsense Limited | Systems and methods for organizing dependent and sequential software threads |
-
2014
- 2014-09-10 FR FR1458511A patent/FR3025627B1/fr not_active Expired - Fee Related
-
2015
- 2015-08-25 US US15/510,638 patent/US11874758B2/en active Active
- 2015-08-25 JP JP2017534008A patent/JP6498770B2/ja not_active Expired - Fee Related
- 2015-08-25 WO PCT/FR2015/052267 patent/WO2016038272A1/fr active Application Filing
- 2015-08-25 EP EP15763052.6A patent/EP3191961A1/fr not_active Ceased
- 2015-08-25 CN CN201580060764.2A patent/CN107003927A/zh active Pending
-
2017
- 2017-03-12 IL IL251095A patent/IL251095A0/en unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7086064B1 (en) * | 2000-05-27 | 2006-08-01 | International Business Machines Corporation | Performance profiling tool |
US8499299B1 (en) * | 2010-06-29 | 2013-07-30 | Ca, Inc. | Ensuring deterministic thread context switching in virtual machine applications |
US8667472B1 (en) * | 2010-07-29 | 2014-03-04 | Disney Enterprises, Inc. | System and method of instrumenting code for in-production monitoring |
US20130036404A1 (en) * | 2011-08-01 | 2013-02-07 | Vmware, Inc. | Testing of a software system using instrumentation at a logging module |
Non-Patent Citations (1)
Title |
---|
MONAJJEMI VALIALLAH ET AL: "Drums: A Middleware-Aware Distributed Robot Monitoring System", 2014 CANADIAN CONFERENCE ON COMPUTER AND ROBOT VISION, IEEE, 6 May 2014 (2014-05-06), pages 211 - 218, XP032596789, DOI: 10.1109/CRV.2014.36 * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106649071A (zh) * | 2016-12-30 | 2017-05-10 | 广州华多网络科技有限公司 | 进程内部日志上报的方法和装置 |
CN106649071B (zh) * | 2016-12-30 | 2019-12-20 | 广州华多网络科技有限公司 | 进程内部日志上报的方法和装置 |
WO2019129957A1 (fr) | 2017-12-27 | 2019-07-04 | Bull Sas | Procede de controle de la gestion des traces d'evenements dans l'execution d'une application informatique sur une machine informatique |
Also Published As
Publication number | Publication date |
---|---|
IL251095A0 (en) | 2017-04-30 |
FR3025627B1 (fr) | 2018-03-23 |
JP6498770B2 (ja) | 2019-04-10 |
JP2017532703A (ja) | 2017-11-02 |
US11874758B2 (en) | 2024-01-16 |
EP3191961A1 (fr) | 2017-07-19 |
CN107003927A (zh) | 2017-08-01 |
FR3025627A1 (fr) | 2016-03-11 |
US20170255540A1 (en) | 2017-09-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8205215B2 (en) | Automated event correlation | |
WO2016038272A1 (fr) | Mecanisme haute performance pour generation d'informations de journalisation d'un processus informatique | |
EP2257876B1 (fr) | Methode de prechargement dans une hierarchie de memoires des configurations d'un systeme heterogene reconfigurable de traitement de l'information | |
FR2969334A1 (fr) | Module materiel de securite et procede de debogage d'un tel module | |
FR2958059A1 (fr) | Procede, programme d'ordinateur et dispositif de validation d'execution de taches dans des systemes informatiques evolutifs | |
FR2780589A1 (fr) | Agent de communication entre un administrateur de systeme informatique et un systeme de ressources distribuees et outils de creation d'un tel agent | |
FR3031822A1 (fr) | Telechargement de donnees sur un equipement distant | |
EP2278466A1 (fr) | Dispositif et procédé pour l'exécution distribuée de traitements de données numériques | |
EP1907931A1 (fr) | Architecture a composants logiciels pour les applications a plate-forme d'execution donnant acces au niveau metaprogramme | |
EP2996036B1 (fr) | Procédé de surveillance d'une architecture applicative comportant une pluralité de services | |
EP3881515B1 (fr) | Système de supervision formelle de communications | |
FR3071630A1 (fr) | Procede de gestion de modules logiciels embarques pour un calculateur electronique d'un appareil electrique de coupure | |
EP3729273B1 (fr) | Systeme et procede d'elaboration et d'execution de tests fonctionnels pour grappe de serveurs | |
FR2990533A1 (fr) | Procede de suivi d'execution d'un logiciel et logiciel pour la mise en oeuvre du procede | |
EP3195113B1 (fr) | Procédé de vérification de traçabilité de premières instructions en un langage de programmation procédurale générées à partir de secondes instructions en un langage de modélisation | |
EP3144812A1 (fr) | Architecture client/serveur pour l administration d'un supercalculateur | |
FR2806498A1 (fr) | Systeme informatique de calcul et procede de calcul mis en oeuvre au moyen d'un tel systeme | |
WO2019129957A1 (fr) | Procede de controle de la gestion des traces d'evenements dans l'execution d'une application informatique sur une machine informatique | |
FR3118815A1 (fr) | Estimation de la progression de l'exécution d'une tâche logicielle | |
FR2938087A1 (fr) | Procede d'implementation d'une machine a etats finis via l'utilisation d'annotations java. | |
FR3031820A1 (fr) | Procede de determination de la validite d'un modele | |
FR2911971A1 (fr) | Procede et systeme de verification de proprietes d'un programme informatique. | |
FR3101973A1 (fr) | Dispositif de surveillance | |
FR3141301A1 (fr) | Procédé de traitement d’une requête d’exécution d’un service dans un réseau de communication, procédé de validation de la requête, entité intermédiaire, entité de validation, système et programme d’ordinateur correspondants | |
WO2024121266A1 (fr) | Systeme de deploiement et de test d' un composant d' un logiciel sur un ensemble de ressources materielles |
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: 15763052 Country of ref document: EP Kind code of ref document: A1 |
|
ENP | Entry into the national phase |
Ref document number: 2017534008 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 251095 Country of ref document: IL |
|
REEP | Request for entry into the european phase |
Ref document number: 2015763052 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2015763052 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15510638 Country of ref document: US |