# US 2025/0094265 A1 · Atomic callhome classifier with instantaneous log collection and contextual log analysis

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2025/0094265 A1
- Document ID: US20250094265A1
- Status: Published application
- Kind: A1
- Application number: 18/467,872
- Filed: 2023-09-15
- Published: 2025-03-20
- Earliest claimed: 2023-09-15
- Assignees: Dell Products L.P.
- Applicants: Dell Products L.P.
- Inventors: Kumaravel Palanisamy; Rashmi Shashidhar; Kiran Kumar Grandhi; Vijay Srinivasan
- Web page: https://patentgrep.com/patent/US20250094265A1

## CPC

- G06F 11/0784: {Routing of error reports, e.g. with a specific transmission path or data flow}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method comprising: detecting an event that is indicative of an error that has occurred in a first computing system; identifying a subsystem and an object that are associated with the event; identifying one or more log files that are associated with the subsystem and object; generating a first event report that is associated with the event, the first event report including the one or more log files, the first event report identifying the subsystem and the object that are associated with the event; identifying a support team that is associated with the event based on the object and subsystem; and routing the first event report to the support team.

## Claims

### Claim 1

A method, comprising:
detecting an event that is indicative of an error that has occurred in a first computing system;
identifying a subsystem and an object that are associated with the event;
identifying one or more log files that are associated with the subsystem and object;
generating a first event report that is associated with the event, the first event report including the one or more log files, the first event report identifying the subsystem and the object that are associated with the event;
identifying a support team that is associated with the event based on the object and subsystem; and
routing the first event report to the support team.

### Claim 2 (depends on 1)

The method of claim 1, wherein the event includes a callhome event and the first event report includes a Holistic Log Analyzer module (HOLA) report.

### Claim 3 (depends on 1)

The method of claim 1, wherein routing the first event report to the support team includes storing, in a database, an indication that the event is required to be handled by the support team.

### Claim 4 (depends on 1)

The method of claim 1, wherein routing the first event report to the support team includes transmitting the first event report to a second computing system that is associated with the support team.

### Claim 5 (depends on 1)

The method of claim 1, wherein:
identifying the subsystem includes performing a search of a database based on contents of the event, and retrieving a first identifier of the subsystem; and
the database includes a plurality of entries, each of the entries including a respective a event signature and a respective subsystem identifier that corresponds to the respective event signature.

### Claim 6 (depends on 1)

The method of claim 1, further comprising classifying the event as being associated with either a configuration problem or a software bug, wherein the first event report is generated only when the event is classified as being associated with a software bug.

### Claim 7 (depends on 1)

The method of claim 1, wherein:
the first computing system includes a clustered computing system having a plurality of guest operating systems that are executed in a virtualized environment of the first computing system;
and the generating and routing steps are performed by an event processing engine that is executed in one of the plurality of guest operating systems.

### Claim 8

A system, comprising:
a memory; and
one or more processors that are coupled to the memory, the one or more processors being configured to perform the operations of:
detecting an event that is indicative of an error that has occurred in a first computing system;
identifying a subsystem and an object that are associated with the event;
identifying one or more log files that are associated with the subsystem and object;
generating a first event report that is associated with the event, the first event report including the one or more log files, the first event report identifying the subsystem and the object that are associated with the event;
identifying a support team that is associated with the event based on the object and subsystem; and
routing the first event report to the support team.

### Claim 9 (depends on 8)

The system of claim 8, wherein the event includes a callhome event and the first event report includes a Holistic Log Analyzer module (HOLA) report.

### Claim 10 (depends on 8)

The system of claim 8, wherein routing the first event report to the support team includes storing, in a database, an indication that the event is required to be handled by the support team.

### Claim 11 (depends on 8)

The system of claim 8, wherein routing the first event report to the support team includes transmitting the first event report to a second computing system that is associated with the support team.

### Claim 12 (depends on 8)

The system of claim 8, wherein:
identifying the subsystem includes performing a search of a database based on contents of the event, and retrieving a first identifier of the subsystem; and
the database includes a plurality of entries, each of the entries including a respective a event signature and a respective subsystem identifier that corresponds to the respective event signature.

### Claim 13 (depends on 8)

The system of claim 8, wherein the at least one processor is further configured to perform the operation of classifying the event as being associated with either a configuration problem or a software bug, wherein the first event report is generated only when the event is classified as being associated with a software bug.

### Claim 14 (depends on 8)

The system of claim 8, wherein:
the first computing system includes a clustered computing system having a plurality of guest operating systems that are executed in a virtualized environment of the first computing system;
and the generating and routing steps are performed by an event processing engine that is executed in one of the plurality of guest operating systems.

### Claim 15

A non-transitory computer-readable medium storing one or more processor-executable instructions, which, when executed by at least one processor, cause the at least one processor to perform the operations of:
detecting an event that is indicative of an error that has occurred in a first computing system;
identifying a subsystem and an object that are associated with the event;
identifying one or more log files that are associated with the subsystem and object;
generating a first event report that is associated with the event, the first event report including the one or more log files, the first event report identifying the subsystem and the object that are associated with the event;
identifying a support team that is associated with the event based on the object and subsystem; and
routing the first event report to the support team.

### Claim 16 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the event includes a callhome event and the first event report includes a Holistic Log Analyzer module (HOLA) report.

### Claim 17 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein routing the first event report to the support team includes storing, in a database, an indication that the event is required to be handled by the support team.

### Claim 18 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein routing the first event report to the support team includes transmitting the first event report to a second computing system that is associated with the support team.

### Claim 19 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein:
identifying the subsystem includes performing a search of a database based on contents of the event, and retrieving a first identifier of the subsystem; and
the database includes a plurality of entries, each of the entries including a respective a event signature and a respective subsystem identifier that corresponds to the respective event signature.

### Claim 20 (depends on 15)

The non-transitory computer-readable medium of claim 15, wherein the one or more processor-executable instructions, when executed by the at least one processor, further cause the at least one processor to perform the operation of classifying the event as being associated with either a configuration problem or a software bug, the first event report being generated only when the event is classified as being associated with a software bug.
