G06F2201/83

SMART ALERT CORRELATION FOR CLOUD SERVICES

Methods and systems described herein correlate an incoming alert, regarding events that affect service performance, availability, and security in a cloud services platform, with an existing incident record, stored in remote storage, to enable improved incident handling. Alert information is applied to machine-learning models to correlate the incoming alert to a parent incident record. In rule-based correlation, a local cache stores query signatures (keys) and information related to respective incident records (values). A correlation rule is retrieved for the alert, and a correlation query is constructed based on the alert and the rule. A query signature is generated and used as a cache key to access information about a respective parent incident in storage. If the parent information is not found in the cache, the remote storage is searched for the parent incident record using the correlation query. The alert and correlated parent incident record are associated in remote storage.

Backing up a Load Control System

Systems and methods are disclosed for generating a backup of configuration information files at a system controller and storing this backup at a server via the use of a network device.

METHOD FOR MONITORING AN ENGINE CONTROL UNIT

Methods are provided for supervising a motor control unit with at least two separate channels, each of the two channels including at least: means for executing a given application task AS, the application task AS including a plurality of successively executed computations between which latency periods elapse; a first component capable of performing the computations; a second component capable of storing data; the application tasks AS of the channels being capable of communicating. The method comprising includes the following steps: a) detecting a latency period; b) performing, during this latency period, an operating state test of at least one of the components; and c) determining a state of the component corresponding to a failure state or a healthy state.

Detection of Data Discrepancy After XOR Recovery
20220342752 · 2022-10-27 ·

A data storage device includes a memory device and a controller coupled to the memory device. The controller comprises an XOR module, an ECC module, a scrambler, an encoder, and comparison logic. The controller is configured to retrieve data from the memory device, decode the retrieved data, execute XOR protection logic on the decoded data, encode the decoded data, and compare the encoded data to the retrieved data stored in the memory device.

Gateway device, in-vehicle network system, and firmware update method

A gateway device is connected via one or more networks to electronic controllers on-board a vehicle. The gateway device includes one or more memories, and circuitry that acquires firmware update information. The circuitry determines whether or not a first electronic controller satisfies a second condition based on second information about the first electronic controller, where the second information is whether the first electronic controller includes a firmware cache for performing a pre-update firmware cache operation. The circuitry also causes, when the second condition is not satisfied, the gateway device to execute a proxy process, where the gateway device requests the first electronic controller to transmit boot ROM data to the gateway device, creates updated boot ROM data with the updated firmware, and transmits the updated boot ROM data to the first electronic controller that updates the boot ROM and resets the first electronic controller with the updated firmware.

Service issue prioritisation based on impact using software telemetry

A system is provided herein that can correlate service issues with system telemetry associated with the software session associated with those service issues. Using a statistical approach, the system can evaluate data across numerous software sessions to rank the importance of the reported service issues. To accomplish the ranking, the system can parse the reports of service issues on a periodic basis, can extract telemetry identifiers (IDs) from the logs, can query the telemetry, may compute the relative importance of detected issues (in the context of calls going on for that day), and then can report this impact hack to the service issue database.

Event Prioritization for an Ordered Event Stream
20220326985 · 2022-10-13 ·

Event prioritization for an ordered event stream (OES) is disclosed. Unlike conventional prioritization techniques, the disclosed subject matter can be performed by an OES data storage system to provide direct, rather than indirect, control of prioritization. In an embodiment, a prioritized hashed key (PHK) can be determined from an event characteristic and an indicated event priority value based on a selectable priority-sensitive hashing function. As such, events with a same key characteristic but different indicated priorities can have different PHKs, events with different key characteristics but the same indicated priority can have different PHKs, and events with the same key characteristic and the same priority can have a same PHK. An event priority can be inherently comprised in the PHK without needing to explicitly store the priority value with a written event in the OES. Moreover, the disclosed prioritization for the OES can be compatible with OES scaling techniques.

Backing up a load control system

Systems and methods are disclosed for generating a backup of configuration information files at a system controller and storing this backup at a server via the use of a network device.

Volume or virtual machine level backup and generating placeholders for virtual machine files

According to certain aspects, a method can include creating a backup copy of data associated with a virtual machine (VM) on one or more secondary storage devices, wherein the backup copy includes corresponding secondary copies of a plurality of files associated with the VM; analyzing metadata associated with the secondary copies to determine which of the plurality files are eligible to be removed from the primary storage device; in response determining that one or more files are eligible to be removed from the primary storage device, for respective file of the one or more files: determining whether the respective file has been changed since a first time at which the backup copy of the data associated with the VM was created; in response to determining that the respective file has not changed since the first time, removing the respective file; and adding a file placeholder for the removed file.

Automated Incident Detection and Root Cause Analysis
20220334904 · 2022-10-20 ·

A system includes a computing platform communicatively coupled to multiple network nodes, the computing platform having processing hardware and a memory storing a software code. The processing hardware is configured to execute the software code to detect multiple anomalous performance indicators originating from one or more of the network nodes, determine, using the anomalous performance indicators in an automated process, the occurrence of an incident, and determine the signature of the incident. The processing hardware is further configured to execute the software code to compare the signature to one or more entries in an incident signature database, perform, when the comparison determines that the signature corresponds to one or more of the entries, a root cause analysis of the incident using the corresponding one or more entries, and generate an incident alert including one or both of a result of the root cause analysis and a description of the incident.