Patent classifications
G06F11/0778
Classifying errors in a failure log
Techniques are disclosed relating to a method that includes accessing, by a failure management program, a failure log that includes a plurality of character strings corresponding to errors that are associated with execution of one or more batch processes. The failure management program may compare a particular character string of the plurality of character strings to a set of character strings that are associated with respective ones of a plurality of failure categories. This comparing may include determining whether particular keywords that are included in respective ones of the set of character strings are included in the particular character string. In response to the comparing, the failure management program may assign a particular error corresponding to the particular character string to a particular failure category, or may determine a new failure category if the particular character string does not match an existing failure category.
Fatal error logging in a memory device
Devices and techniques for fatal error logging in a memory device are described herein. For example, a read request can be received for a component of the memory device. A fatal error indication of an error that prevents correct execution of read request can be detected. Diagnostic information for the failure indication can be collected. A response to the read request can then be made with a portion of the diagnostic information as payload instead of the user data that would have occupied the payload had the read succeeded. Metadata in the response can be used to communicate an error code.
INFORMATION RECORDING METHOD, APPARATUS, AND DEVICE, AND READABLE STORAGE MEDIUM
An information recording method, apparatus, and device, and a readable storage medium are provided. The method includes: when a server is started, determining a ring buffer in a Double Data Rate (DDR) of a Field-Programmable Gate Array (FPGA) acceleration card based on an OpenPower platform; determining a start address and an end address of the ring buffer and configuring the start address and the end address to the FPGA acceleration card; and during a running process of the server, recording preset debugging information to the ring buffer in real time, so as to perform fault location according to data in the ring buffer after a fault occurs in the server. According to the present application, during a running process of a server, preset debugging information is recorded using a DDR of an FPGA acceleration card; therefore, when a down fault causes a Central Processing Unit (CPU) error of a server, recording of debugging information can also be ensured, thereby facilitating fault location.
Apparatus, method and computer program for cloud scraping using pre-scraped big data
A cloud scraping system using pre-scraped big data includes an information providing server which, when receiving a scraping request from a user terminal, provides the user terminal with response information to the received scraping request, and a big data storage which stores pre-scraped information, wherein when the scraping request is about static information, the information providing server acquires the response information using the pre-scraped information. According to the above cloud scraping system using pre-scraped big data, there is an advantage that it is possible to quickly respond to a scraping request from the user terminal afterwards by pre-scraping and storing static information in the big data storage. Additionally, it is possible to improve the scraping server operation efficiency by making a proper use of a single or multi-processing scraping server based on policy information of a scraping target external institution.
Hardware-management-console-initiated data protection
A method for protecting data in a storage system is disclosed. In one embodiment, such a method includes detecting, by a first hardware management console, first battery-on status associated with a first uninterruptible power supply. The method further detects, by a second hardware management console, second battery-on status associated with a second uninterruptible power supply. The method communicates, from the first hardware management console to the second hardware management console, the first battery-on status. The method then triggers, by the second hardware management console, a dump of modified data from memory to more persistent storage upon detecting both the first battery-on status and the second battery-on status. A corresponding system and computer program product are also disclosed.
Detecting execution hazards in offloaded operations
Detecting execution hazards in offloaded operations is disclosed. A second offload operation is compared to a first offload operation that precedes the second offload operation. It is determined whether the second offload operation creates an execution hazard on an offload target device based on the comparison of the second offload operation to the first offload operation. If the execution hazard is detected, an error handling operation may be performed. In some examples, the offload operations are processing-in-memory operations.
Error documentation assistance
An error documentation system including tools to collect and analyze application error data for individual development teams and tools to share documented defects and solutions across development teams during any stage of development cycle. The system may receive and analyze event logs for error events triggered by applications on end-user devices. The system may automatically generate defect tickets and/or ticket entries for defects identified in event logs. The system may train one or more machine learning (ML) models to correlate input with identified defects from a defects database. In response to identifying correlated identified defects, the system may generate ticket entries indicating the correlated identified defects and associated solutions for the defects. The system may provide an interface for users to query the data stored in the database.
TECHNOLOGY FOR LOGGING LEVELS AND TRANSACTION LOG FILES
Dynamic logging includes generating parsed event data by at least one natural language processor responsive to event data of a log for transactions of a target application. In response to the parsed event data, a first classifier classifies context states of the respective transactions of the target application. In response, a second classifier classifies trouble prone states of the respective transactions, wherein the trouble prone states are for respective hierarchical levels. When a logic module determines, for a current one of the trouble prone states for a current transaction, that the current trouble prone state is a higher trouble prone level than for a transaction immediately preceding the current transaction, the logic module sends an increased log detail selection to the target application, so that a greater amount of log detail is logged for at least a next transaction after the current transaction.
DATA COLLECTING IN ISSUE TRACKING SYSTEMS
A system and method for allowing an assignee to rapidly collect data about a bug/error that is associated with the execution of a software application on a computing device. The method includes including receiving, from a client device, a request to resolve an error associated with an execution of an application on a remote server. The request includes configuration information for connecting to the remote server and an identifier to a component of the application. The method includes determining one or more files associated with the component of the application. The method includes establishing a connection to the remote server using the configuration information. The method includes retrieving the one or more files from the remote server via the connection. The method includes granting, to an assignee device, access to the one or more files that were retrieved from the remote server.
IN-APP FAILURE INTELLIGENT DATA COLLECTION AND ANALYSIS
Intelligent collection and analysis of in-app failure data is disclosed herein. Upon an application failure in a client device, the client device may collect failure information uniquely identifying a specific failure and provide the failure information to an analysis system. The analysis system may identify a specific failure that identifies the application and a specific portion of the code in the application, based on the failure information and match an action correlated to the specific failure where the action is uniquely designed to resolve the specific failure in the application. The action may include instructions for the client device used to intelligently lead to a resolution of the specific failure. The analysis system may transmit the action to the client device to perform the action and provide any follow up information to the analysis server. The analysis server may use the information to further analyze the specific failure.