# US 2021/0334364 A1 · Evaluation of a performance parameter of a monitoring service

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

- Number: US 2021/0334364 A1
- Document ID: US20210334364A1
- Status: Published application
- Kind: A1
- Application number: 16/605,609
- Filed: 2018-08-22
- Published: 2021-10-28
- Earliest claimed: 2018-06-07
- Assignees: Hewlett-Packard Development Company, L.P.
- Applicants: Hewlett-Packard Development Company, L.P.
- Inventors: Adrian John Baldwin; Jonathan Griffin; Daniel Cameron Ellam
- Web page: https://patentgrep.com/patent/US20210334364A1

## CPC

- G06F 11/07: Responding to the occurrence of a fault, e.g. fault tolerance
- G06F 11/0748: {in a remote unit communicating with a single-box computer node experiencing an error/fault (remote testing G06F11/2294)}
- G06F 11/0754: {by exceeding limits}
- G06F 11/0793: {Remedial or corrective actions (recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40)}
- G06F 21/50: Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In an example, a method includes analysing data collected from a service. A value representative of the number of anomalies in the data is generated, this value then being compared with a threshold. Depending on whether the value is greater or less than the threshold, a performance parameter of the monitoring service may be evaluated.

## Claims

### Claim 1

A method comprising:
analysing, by a processor, data collected from a monitoring service of a computing system;
generating a value representative of the number of anomalies in the data;
comparing the value with a threshold; and
depending on whether the value is greater or less than the threshold, evaluating a performance parameter of the monitoring service.

### Claim 2 (depends on 1)

A method as claimed in claim 1 further comprising accepting or rejecting an output of the service based on the evaluation.

### Claim 3 (depends on 1)

A method as claimed in claim 1 wherein the data collected from the monitoring service comprises data relating to at least one of: CPU usage, memory usage, resource usage, privileges, network connectivity, and dynamic link libraries.

### Claim 4 (depends on 1)

A method as claimed in claim 1 wherein data is collected from the monitoring service at predetermined time intervals.

### Claim 5 (depends on 1)

A method as claimed in claim 1 wherein the value representative of the number of anomalies in the data comprises at least one of: the number of anomalies in the data, the percentage of the data determined to be anomalous, a value representing the rate of change in the number of anomalies in the data over time.

### Claim 6 (depends on 1)

A method as claimed in claim 1 wherein the threshold is a first threshold, further comprising a second threshold, and wherein, when the value is below the first and second thresholds, accepting an output of the monitoring service.

### Claim 7 (depends on 1)

A method as claimed in claim 1 wherein the threshold is a first threshold, further comprising a second threshold, and wherein, when the value is below one of the first and second thresholds, performing at least one of: further analysis on the data, checking part of the monitoring service for proper function, and checking the functioning of a management system, and creating a record of the data.

### Claim 8 (depends on 1)

A method as claimed in claim 1 wherein the service is carried out on a user device and the method is carried out remotely from the user device.

### Claim 9 (depends on 1)

A method as claimed in claim 1, when the value is below the threshold, further comprising at least one of: restarting the service, running an AV scan, reporting to a management system, checking for changes in the operation of the service, triggering a corrective operation.

### Claim 10 (depends on 1)

A method as claimed in claim 1 wherein the value representative of the number of anomalies in the data comprises a value representative of a type of anomaly, the method comprising:
assigning a risk parameter to the value representative of the number of anomalies in the data; and
when the risk parameter is below the threshold, accepting an output of the service and otherwise, rejecting an output of the service.

### Claim 11

Processing apparatus comprising:
an anomaly detection module to detect anomalies in data collected from a monitoring service of a computing system and to produce an output associated with anomalies in the data; and
an anomaly analysis module to analyse the output associated with the anomalies in the data and to produce a value representative of the number of anomalies in the data; and
an evaluation module to evaluate a performance parameter of the monitoring service.

### Claim 12 (depends on 11)

Processing apparatus as claimed in claim 11 further comprising a gateway module to allow or prevent receipt of an output of the monitoring service.

### Claim 13 (depends on 11)

Processing apparatus as claimed in claim 11 wherein the anomaly detection module is to collect data from the monitoring service at a determined sample rate.

### Claim 14

Processing apparatus as claimed 11 further comprising a corrective module to perform at least one of: restart the monitoring service, run an AV scan, report to a management system, check for changes in the operation of the service, trigger a corrective operation.

### Claim 15

A non-transitory machine-readable storage medium, encoded with instructions executable by a processor, the machine-readable storage medium comprising instructions to cause the processor to:
analyse data collected from a monitoring service of a computing system to produce an output associated with anomalies in the data;
analyse the output to produce a value representative of the number of anomalies in the data; and
receive an output of the service if this value is below a threshold.
