[go: up one dir, main page]

WO2025008219A1 - Procédé mis en oeuvre par ordinateur pour réduire des fichiers journaux entachés d'erreur à partir d'un système - Google Patents

Procédé mis en oeuvre par ordinateur pour réduire des fichiers journaux entachés d'erreur à partir d'un système Download PDF

Info

Publication number
WO2025008219A1
WO2025008219A1 PCT/EP2024/067671 EP2024067671W WO2025008219A1 WO 2025008219 A1 WO2025008219 A1 WO 2025008219A1 EP 2024067671 W EP2024067671 W EP 2024067671W WO 2025008219 A1 WO2025008219 A1 WO 2025008219A1
Authority
WO
WIPO (PCT)
Prior art keywords
log files
error
computer
log
characters
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
PCT/EP2024/067671
Other languages
German (de)
English (en)
Inventor
Guillem Boada
Alexander Kaiser
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Trumpf Werkzeugmaschinen SE and Co KG
Original Assignee
Trumpf Werkzeugmaschinen SE and Co KG
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 Trumpf Werkzeugmaschinen SE and Co KG filed Critical Trumpf Werkzeugmaschinen SE and Co KG
Publication of WO2025008219A1 publication Critical patent/WO2025008219A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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/3072—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
    • G06F11/3082—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting the data filtering being achieved by aggregating or compressing the monitored data

Definitions

  • the invention relates to a computer-implemented method for reducing error-indicating log files from at least one system and an associated computer program product, reduction system and environmental system with the reduction system and a system.
  • Testing is the process of interacting with the product to check that it meets the requirements and is free from product defects that could affect its functionality. The goal is to decide whether the product can be released or not. For small products, testing can be successfully performed manually, but as the size and complexity of the product increases, especially with the aforementioned machine tools, this task becomes impossible to perform manually. In this case, it is convenient to perform automatic testing of the product using a computer-based testing system.
  • test procedures known from the state of the art can be used for troubleshooting and identification, they are not as suitable for preventing product defects as would be desirable.
  • the known test procedures require a very large amount of data to be analyzed in log files, which places a very heavy load on the processor and data storage.
  • log files can hardly be processed manually by service engineers when required, particularly if this is necessary in addition to computer-aided analysis. This means that defects can remain in the product which only appear later at the customer's site and lead to complications which can only be resolved with great effort through a new test phase.
  • the invention is therefore based on the object of increasing the reliability of the products, in particular to propose a particularly robust computer-implemented method for reducing error-indicating log files.
  • the object is achieved by a computer-implemented method for reducing error-indicating log files from at least one system.
  • the method comprises the following steps:
  • the reduction method according to the invention thus provides a reduced log file which has been cleaned of error-free characters or, in other words, tokens, so that the log file has a smaller amount of data and file size. It can therefore be processed more easily both on a computer basis, i.e. by means of a processor, and manually, e.g. by a test engineer, in order to carry out error detection, analysis and correction.
  • the reduction process according to the invention can comprise a plurality of further steps, as explained in more detail below.
  • the reduction process according to the invention Reduction process can also be in the form of a
  • the data can be stored in a memory using a grouping method, as will be explained in more detail later.
  • a grouping method a database is created from different log file groups of different situations, in particular error situations.
  • a robust database can be created by the inventive extraction of predefined, error-inconspicuous characters, which can be used for troubleshooting, analysis and correction.
  • the log files can be read in by a system, in particular a test system, which carries out one or more processes, for example system tests, service processes, etc., whereby several systems can also be used.
  • the log files are error-indicating, i.e. they indicate an error, in particular that the corresponding system test was interrupted by an error message, which is noted in the log file over one or more lines as an entry or entries.
  • the processes for example system tests, can be carried out in particular on the products with the computer programs to be tested, in particular machines, for example machine tools.
  • the system tests can be represented by a computer program that can be carried out by a corresponding processor, in particular on the product.
  • a corresponding test sequence or a test phase of the test system can be carried out by a computer, in particular a processor, of the respective machine.
  • the system in particular a test system, thus enables a process, in particular a test of the Functionality of the machine, in particular in its functionality or with regard to possible errors at least in relation to one or more computer programs that can be executed on the machine.
  • Such a test can in particular be designed as a UI (user interface) test, in particular GUI (graphical user interface) test, which can run on a corresponding system screen.
  • the result of the test sequence can be a test report, whereby the test report can include the log file and possibly other attachments as a test report appendix.
  • the method according to the invention can of course also comprise the step of the process, in particular testing or test sequence itself, in particular in the form of that described above.
  • the predefined, error-free characters can be, for example, N-grams, syllables, letters. Error-free means in particular that characters do not contain any information, at least no relevant information about errors, or, in other words, are inconspicuous with regard to possible errors. In particular, error-free can mean error-irrelevant. Such error-free characters can have been identified in log files that do not contain any errors.
  • the predefined, error-free characters can in particular come from a created database. This database or the characters contained therein, for example N-grams, can be compared with the content or the entries, in particular by transforming the entries in the log files into characters, in particular N-grams, as explained in more detail later.
  • the log file groups obtained from the grouping of the log files mentioned above can be used.
  • the N-grams can be, for example, monograms, bigrams, trigrams, etc. and can be written in any language, e.g. German or English.
  • the predefined, error-free characters can be removed from the log files if they match, in particular deleted, and/or the log files shortened by the error-free characters can be output, in particular for further use.
  • the method can further comprise the step of transforming the entries of the log files into characters, in particular n-grams. This enables a quick and accurate comparison of the predefined, error-free characters with the log files.
  • the method can also further comprise the step of generating sequences from the error-free characters of the shortened log files that remain after removal in order to obtain the reduced log files.
  • the log files transformed with characters are converted back into a character string of sequences.
  • this makes it possible to obtain the reduced log files, which can then be used for further purposes, for example in other methods of processors for error investigation or by service technicians.
  • the method can further comprise the step of merging the entries or sequences into blocks, wherein the blocks each comprise one or more lines. This is advantageous in order to carry out a subsequent similarity analysis between individual log files and thus to identify log files with similar error situations.
  • the merging step can be carried out by calculating the longest substring or the longest repeated substring.
  • the method may further comprise the step of calculating similarity values between the different log files.
  • the similarity value is a value relating to a similarity between two log files, which should in particular correspond to the human intuitive concept of similarity. This is in particular a real value, which can for example be restricted to an interval such as the unit interval, i.e. [0, 1], or a Boolean value.
  • the similarity value can in particular be symmetrical in order to ensure that the similarity between two log files is always the same, regardless of the order in which they are determined using a similarity operator. It has been shown that the similarity calculation with blocks is particularly robust against events that are broken into several lines and can contain many words. Otherwise, the robustness is increased by the prior extraction of the predefined, error-free characters.
  • Jaccard similarities are calculated for the calculation of the similarity values.
  • This metric quantifies the similarity between two sample sets. It is equal to the ratio between the number of elements in the intersection and the union of these sets. That is, the more elements they have in common, the greater the similarity.
  • the presence or number of matching elements, such as lines, blocks, words, etc., between the compared log files can be compared.
  • the method may further comprise the step of grouping the different reduced log files into at least two log file groups of different error situations based on the previously calculated similarity values.
  • An error situation is understood to mean at least one error or a combination of several errors that are the same or similar to one another. This refers in particular to the cause of the error, for example incorrect programming in a certain part of the computer program executed by the system, a certain category of hardware errors, etc.
  • the similarity values determined in each case are used, in particular by comparing the similarity values with one another.
  • Various grouping operations are possible here.
  • the similarity values can be compared with a grouping logic in order to group the different log files into at least two log file groups with different error situations.
  • the similarity values of the log files can be compared with individual grouping limits of the grouping logic and for each similarity value, the defined grouping limit can be used to determine whether there is sufficient similarity to assign the log files to the same error situation.
  • the grouping logic can also be designed as a maximum value or a maximum requirement in such a way that it requires the maximum of individual similarity values of a log file with its compared log files.
  • an artificial intelligence (AI) model particularly one based on machine learning, can be used to continuously improve the grouping. Through machine learning, the AI model can select ever more optimized grouping limits, in particular different grouping limits for different error situations.
  • the result of the log file groups can be used in a variety of ways, and this use can be a further component of the method.
  • the result can be transmitted to the test system(s) carrying out the system test to improve testing, in particular in the form of a machine learning algorithm, to the product(s) being tested, for example to output or display the specific error situation on a corresponding screen or a control element of the product, to a service technician for rectifying product errors, etc. and used by this or that technician.
  • At least one group-based metric is determined for each log file group, in particular a ratio of a number of log files of one of the error situations to a total number of log files.
  • This metric can be used to very easily determine the most frequent error situation.
  • This metric is preferably applied to the log files of a predetermined period of time, e.g. the log files of the last week.
  • An error situation can describe both a product error and a false alarm.
  • the metric can be used to Therefore, the most common product errors and false alarms can be determined. This allows the developers' work to be prioritized.
  • the method can also further comprise the step of combining the log files of at least one of the log file groups into a group error log file that is aggregated in particular with regard to the error situation.
  • the group error log file can then be used to resolve errors more quickly.
  • the method can further comprise the step of determining an error criticality of the log file groups and in particular a prioritization of the log file groups according to the determined error criticality.
  • an error severity of the log file groups is determined.
  • the error criticality can be determined, for example, on the basis of one or more of the previously mentioned metrics. This allows prioritization during error correction in order to make the product, for example the machine tool, as fully functional or error-free as possible as quickly as possible.
  • a corresponding Kl model can thus increase the robustness of the process, for example by better determining predefined, error-free characters, grouping limits, etc.
  • the object mentioned at the outset is further achieved by a computer program product according to claim 12.
  • the computer program product comprises instructions which, when the computer program product is executed by a computer, cause the computer to carry out the method according to the invention.
  • the computer program product may be a computer program as such or a computer-readable storage medium on which the computer program or its instructions are stored.
  • the storage medium may be a tangible device that can store and save instructions for use by an instruction execution device, i.e. a computer, in particular a processor.
  • the computer-readable storage medium may be, for example, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the aforementioned devices, but is not limited thereto.
  • a non-exhaustive list of more specific examples of a computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch cards or raised structures in a groove with recorded data commands, and any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or flash memory erasable programmable read-only memory
  • SRAM static random access memory
  • CD-ROM compact disc read-only memory
  • DVD digital versatile disk
  • memory stick a floppy disk
  • mechanically encoded device such as punch cards or raised structures in a groove with recorded data commands
  • a computer-readable storage medium should not be understood to mean transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., pulses of light traveling through a fiber optic cable), or electrical signals transmitted through a wire.
  • the computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to the respective computing/processing devices or to an external computer or storage device over a network, such as the Internet, a local area network, a wide area network, and/or a wireless network.
  • the network may include copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers.
  • a network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing/processing device.
  • the computer-readable program instructions for carrying out operations within the scope of the present invention may be assembler instructions, ISA instructions (instruction set architecture), machine instructions, machine-dependent instructions, microcode, firmware instructions, state data, configuration data for integrated circuits, or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or similar, and procedural programming languages such as the "C" programming language or similar programming languages.
  • the computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer, or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer over any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (e.g. over the Internet using an Internet service provider).
  • electronic circuits including, for example, programmable logic circuits, field programmable gate arrays (FPGA), or programmable logic arrays (PLA), may execute the computer readable program instructions by using state information of the computer readable program instructions to personalize the electronic circuits to perform aspects of the present invention.
  • the object mentioned at the outset is also achieved by a reduction system according to claim 13.
  • the reduction system according to the invention comprises a memory and a processor connected to the memory, wherein the computer program product according to the invention is stored on the memory and the processor is configured to execute the instructions of the computer program product.
  • the reduction system may have at least one interface to at least one system, wherein the at least one system is configured to generate log files.
  • Figure 1 is a schematic view of a method according to an embodiment of the invention.
  • FIG. 2 - 7 schematic views of the steps of the
  • Figure 8 is a schematic view of a system environment according to an embodiment of the invention, comprising a reduction system according to an embodiment of the invention and several systems.
  • Figure 1 shows purely schematically the steps 102 to 118 of a computer-implemented method 100 for reducing and grouping error-identifying log files 10 (see Figs. 2 to 7).
  • a step 102 that can be attributed to the method 100 or is separate from it is the testing or system test of a system 1, in particular a test system (see Fig. 8).
  • a test system see Fig. 8
  • other processes of the system are also possible, for example a service process, whereby only testing is discussed below as an example and the method 100 can be carried out and used analogously for such other processes.
  • a product is tested by such a system 1, in particular a computer program product on a machine, for example a machine tool.
  • Each of the systems 1 from Fig. 8 can be used on one or more products (not shown), e.g. computer programs for machine tools.
  • the testing in step 102 can otherwise be carried out according to known principles, in particular as an automated testing of the respective system 1. For example, GUI tests can be used.
  • the result of the test is in each case the output of a log file 10.
  • Log files 10 are machine-generated files that record all these operations. They can also be described as containers of extensive and varied information that can be valuable for troubleshooting. Although there are no standards for their format and size, they are typically structured in entries EI, where each entry EI comprises one or more lines ZE (see Figs. 2 to 6) and reports a specific event together with a timestamp indicating the exact time of the event and, if necessary, even identification numbers and paths (not shown here).
  • the length of the log files 10 in the dataset can vary greatly.
  • the log file length depends directly on the type of test. Some tests are very short and simply start and stop the test sequence, while others are longer and perform several consecutive subtests to test the endurance of the product.
  • client and server logs are preferred for analysis, as they have proven to be particularly informative for machines, especially machine tools.
  • These files are similar in format, but differ in the The client protocol is responsible for capturing the events on the user interface of the machine under test or its processor, while the server protocol collects the information about the process in the backend of the same processor.
  • the log files 10 generated during the system test(s) in step 102 are read in step 104.
  • only the log files 10 with errors can be read in, since only these contain an error message and are relevant for error analysis in order to increase the robustness of the products.
  • Protocol files 10 are a subformat of a text file that is attached to the test report. They can also be referred to as log files. In Figs. 2 to 6, the schematically illustrated protocol files 10 are also referred to as "Log 1" and “Log 2" and are thus distinguished from one another.
  • Figure 2 shows an example of two log files 10 placed side by side that are to be reduced and grouped. They each have a large number of entries EI that are distributed over different lines ZE.
  • step 106 of the method 100 the entries EI of the two log files 10 are now transformed into characters 20, in this case particularly N-grams, for example monograms.
  • characters 20 in this case particularly N-grams, for example monograms.
  • Fig. 3 The result of the transformation for the two log files 10 can be seen in Fig. 3.
  • N-grams a corresponding lexicon with various characters 20, in particular N-grams, e.g. in German and/or English, e.g. monograms, Bigrams, trigrams, etc.
  • N-grams are understood to mean at least monograms, bigrams and trigrams.
  • predefined characters 20 are now removed from the log files 10, in particular deleted, as illustrated in Fig. 4, so that shortened log files 10 are obtained.
  • the predefined characters 20 can, for example, come from a corresponding negative list.
  • the negative list can include characters 20 that are error-free or, in other words, not error-relevant or error-irrelevant.
  • the negative list can, for example, be generated by using the log file groups 40 explained in more detail later.
  • step 110 of the method 100 sequences are generated from the remaining characters 20 of the log files 10, as shown in Fig. 5.
  • the existing characters 20 of each line ZE are each concatenated to form a sequence.
  • Reduced log files 10 can now be output, which have been cleaned of error-irrelevant content and thus offer a better overview of the error pattern of the log file 10.
  • the file size of the log files 10 is significantly reduced, which is gentle on the processor and data memory and thus allows faster error detection.
  • step 112 of the method 100 the entries EI or sequences are combined into blocks BL, wherein the blocks BL each comprise one or more rows ZE, as illustrated in Fig. 6.
  • the combination in step 112 can for example by calculating the longest substring or the longest repeated substring.
  • step 114 of the method 100 the two log files 10 are compared with each other to calculate their similarity.
  • the similarity is carried out by using the blocks BL.
  • step 114 of the method 100 a similarity value 30 is calculated based on the blocks BL of each of two different log files 10. This is illustrated schematically in Fig. 7.
  • the two log files 10 read in and processed according to steps 104 to 112 are compared with each other by a similarity operator 20.
  • the log files 10 can also be compared with already grouped log files 10 from log file groups 40 with different error situations 41, 42 in order to enable the log files 10 to be grouped based on their error pattern, as illustrated in Figure 7 by the arrow reference of the log file groups 40 to the similarity operator 20.
  • the similarity operator 20 can be designed in particular as a Jaccard similarity operator of the presence of the blocks BL of the log files 10 compared with each other. In this case, the number of blocks of both log files 10 is compared with each other. This provides the respective similarity value 30 for each compared pair of log files 10.
  • the respective blocks BL can optionally be weighted, e.g. based on their time of occurrence in the log files 10 or by determining a Tf-idf measure (statistical measure with frequency of occurrence and inverse document frequency).
  • the similarity values 30 are compared using a grouping logic 35, which can in particular have one or more grouping limit values.
  • the grouping logic 35 can, for example, be a real value or a requirement, e.g. for the highest similarity value 30 from the comparisons with different log files 10. If the grouping limit value required by the grouping logic 35 is met by the respective similarity value 30, the grouping takes place in the corresponding log file group 40 of different error situations 41, 42.
  • the result of the log file groups 40 can now be used in a variety of ways, with the optional step 118 being shown as an example in the further course of the method 100 in order to increase the possible uses.
  • the result can be sent to the system(s) 1 to improve testing, in particular in the form of a machine learning algorithm, to the product(s) tested, for example to output or display the specific error situation on a corresponding screen or a control element of the product, to a service technician for rectifying product errors, etc. transmitted to and used by this or that person.
  • At least one group-based metric can be determined for each of the log file groups 40, in particular a ratio of a number of log files 10 of one of the error situations 41, 42 to a total number of log files 10.
  • Figure 8 schematically shows a system environment 200 which shows a reduction system 5 (and grouping system) according to an embodiment of the invention.
  • the reduction system 5 here comprises a processor 6 and a memory 7 on which a computer program product 8 is stored, which comprises instructions which, when the computer program product 8 is executed by the processor 6, cause the processor 6 to carry out the method 100 according to Figure 1.
  • the computer program product 8 requires the log files 10 of the system(s) 1.
  • the system(s) 1 are part of the comprehensive system environment 200 shown, which also includes the reduction system 5.
  • the reduction system 5 has an interface 9 through which it can receive the log files 10 from the systems 1.
  • the systems 1 can include a corresponding interface (not shown) for data communication.
  • the transmission can be wired or wireless in the case of physical interfaces, for example.
  • the systems 1 each have a Test processor 2 and a test memory 3 on which a test computer program 4 is stored for carrying out step 102 of the method 100.
  • the system or systems 1 can each be the products themselves, with the test computer program 4 being executed thereon in order to test the products or their computer programs.
  • system 1 and the reduction system 5 can also be implemented on one of the two systems 1, 5, for which only one memory 7 and one
  • Processor 6 can be present, whereby both computer programs 4, 8 can be stored in the memory 7.
  • the interface 9 can be implemented by computer program code.

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 procédé (100) mis en oeuvre par ordinateur pour réduire des fichiers journaux (10) entachés d'erreur à partir d'au moins un système (1) ainsi qu'un produit programme d'ordinateur (8) associé à celui-ci, un système de réduction (5) et un environnement système (200) comprenant le système de réduction (5) et au moins un système (1).
PCT/EP2024/067671 2023-07-03 2024-06-24 Procédé mis en oeuvre par ordinateur pour réduire des fichiers journaux entachés d'erreur à partir d'un système Pending WO2025008219A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE102023117506.8A DE102023117506A1 (de) 2023-07-03 2023-07-03 Computerimplementiertes Verfahren zum Reduzieren von fehlerausweisenden Protokolldateien aus einem System
DE102023117506.8 2023-07-03

Publications (1)

Publication Number Publication Date
WO2025008219A1 true WO2025008219A1 (fr) 2025-01-09

Family

ID=91664771

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2024/067671 Pending WO2025008219A1 (fr) 2023-07-03 2024-06-24 Procédé mis en oeuvre par ordinateur pour réduire des fichiers journaux entachés d'erreur à partir d'un système

Country Status (2)

Country Link
DE (1) DE102023117506A1 (fr)
WO (1) WO2025008219A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190205197A1 (en) * 2018-01-02 2019-07-04 Carrier Corporation System and method for analyzing and responding to errors within a log file
US20190386819A1 (en) * 2018-06-15 2019-12-19 Dynatrace Llc Method And System For Log Data Analytics Based On SuperMinHash Signatures
WO2021109724A1 (fr) * 2019-12-02 2021-06-10 华为技术有限公司 Procédé et appareil de détection d'anomalie de journal
US20210287109A1 (en) 2020-03-11 2021-09-16 International Business Machines Corporation Analyzing test result failures using artificial intelligence models
CN116244437A (zh) * 2023-02-24 2023-06-09 浪潮电子信息产业股份有限公司 一种日志分类方法、装置、系统及计算机可读存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190205197A1 (en) * 2018-01-02 2019-07-04 Carrier Corporation System and method for analyzing and responding to errors within a log file
US20190386819A1 (en) * 2018-06-15 2019-12-19 Dynatrace Llc Method And System For Log Data Analytics Based On SuperMinHash Signatures
WO2021109724A1 (fr) * 2019-12-02 2021-06-10 华为技术有限公司 Procédé et appareil de détection d'anomalie de journal
US20210287109A1 (en) 2020-03-11 2021-09-16 International Business Machines Corporation Analyzing test result failures using artificial intelligence models
CN116244437A (zh) * 2023-02-24 2023-06-09 浪潮电子信息产业股份有限公司 一种日志分类方法、装置、系统及计算机可读存储介质

Also Published As

Publication number Publication date
DE102023117506A1 (de) 2025-01-09

Similar Documents

Publication Publication Date Title
DE69924296T2 (de) Ic-test programmiersystem zur zuordnung logischer funktionstestdaten von logischen integrierten schaltung zu einer physikalischen darstellung
DE60017457T2 (de) Verfahren zur isolierung eines fehlers in fehlernachrichten
WO2002013015A1 (fr) Systeme de determination d'origines d'erreur
DE112018004216T5 (de) Evaluierungssystem, Evaluierungsverfahren und Programm
EP3340250B1 (fr) L'identification des composants dans le traitement des erreurs des dispositifs médicaux
DE112021003403T5 (de) Benachrichtigungsverwaltung in datenverarbeitungssystemen
DE202023106044U1 (de) Ein System zur Durchführung der Leistungsverschlussbewertung von Wälzelementlager
DE112021003677T5 (de) Automatisierte unterstützte schaltkreisvalidierung
EP1917588B1 (fr) Procédé et dispositif pour supprimer les perturbations affectant un dispositif de traitement de données
DE112017007507T5 (de) Cloud-fähiges prüfen von steuersystemen
DE112011100168T5 (de) Erfassen von Diagnosedaten in einer Datenverarbeitungsumgebung
EP2492701B1 (fr) Procédé et dispositif destinés au test d'une éolienne
DE112015004557B4 (de) Anforderungsüberwachen
DE102010044039A1 (de) Verfahren und Vorrichtung zur Qualitätsanalyse von Systemmodellen
EP3921810B1 (fr) Procédé et dispositif d'identification automatisée d'un défaut d'un produit et/ou d'identification automatisée d'une cause du défaut du produit
WO2025008219A1 (fr) Procédé mis en oeuvre par ordinateur pour réduire des fichiers journaux entachés d'erreur à partir d'un système
DE10111831A1 (de) Verfahren zum automatischen Suchen und Sortieren von Fehlersignaturen von Wafern
DE112017006528T5 (de) Angriff/abnormalität-detektionsvorrichtung, angriff/abnormalität-detektionsverfahren und angriff/abnormalität-detektionsprogramm
DE112010005924T5 (de) Verfahren und System zum Weitergeben von Änderungen an einer Master-Einheit zu Duplikaten
EP3929554A1 (fr) Détection améliorée d'erreurs dans les machines au moyen de l'ia
DE102015225018A1 (de) Verfahren zur Prüfung einer Mehrzahl von in gleicher Weise mit Bauteilen bestückten Bauteilträgern, Computerprogrammprodukt zur Durchführung eines solchen Verfahrens, und Prüfsystem zur Durchführung eines solchen Verfahrens
EP4307121A1 (fr) Procédé mis en uvre par ordinateur pour configurer un système de test virtuel et procédé d'entraînement
DE102023117503A1 (de) Computerimplementiertes Verfahren zum Gruppieren von Fehlerberichten in zumindest zwei Fehlerbericht-Gruppen ähnlicher Fehlersituation
DE102009043286A1 (de) Verfahren und Vorrichtung zur Überprüfung der Konfigurierung eines Computersystems
EP3933600A1 (fr) Procédé de mise en oeuvre automatisée des essais logiciels sur des interfaces graphiques utilisateur ainsi que dispositif de mise en oeuvre d'un tel procédé

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

Country of ref document: EP

Kind code of ref document: A1