# US 2021/0232446 A1 · Application program interface manager log verbosities

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

- Number: US 2021/0232446 A1
- Document ID: US20210232446A1
- Status: Published application
- Kind: A1
- Application number: 17/051,012
- Filed: 2019-08-06
- Published: 2021-07-29
- Earliest claimed: 2018-08-23
- Assignees: Hewlett-Packard Development Company, L.P.
- Applicants: Hewlett-Packard Development Company, L.P.
- Inventors: Mauricio Coutinho MorAES; Daniele Antunes Pinheiro; Francois Connetable
- Web page: https://patentgrep.com/patent/US20210232446A1

## CPC

- G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- G06F 11/3476: {Data logging (G06F11/14, G06F11/2205 take precedence)}
- G06F 17/40: Data acquisition and logging (for input to computer G06F3/00)
- G06F 21/44: Program or device authentication
- G06F 11/0778: {Dumping, i.e. gathering error/state information after a fault for later diagnosis}
- G06F 11/3072: {where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A server that includes an application programming interface (API) manager; a request evaluation module to, when executed by a processor, evaluate a request received from a client device at the API manager; a log rules registry to maintain a number of log verbosity rules; and a log verbosity adjustment module to, when executed by the processor, apply the log verbosity rules to the request and adjust the verbosity of a generated log to be written by the API.

## Claims

### Claim 1

A server, comprising:
an application programming interface (API) manager;
a request evaluation module to, when executed by a processor, evaluate a request received from a client device at the API manager;
a log rules registry to maintain log verbosity rules; and
a log verbosity adjustment module to, when executed by the processor, apply the log verbosity rules to the request and adjust the verbosity of a generated log to be written by the API.

### Claim 2 (depends on 1)

The server of claim 1, wherein the generated log is written by the API to a tog library.

### Claim 3 (depends on 1)

The server of claim 1, the verbosity of the log is defined by a verbosity level based on the log rules.

### Claim 4 (depends on 3)

The server of claim 3, wherein the rule setting the verbosity level is based on the client device sending the request.

### Claim 5 (depends on 3)

The server of claim 3, wherein the rule setting the verbosity level is based on the time of day the request is received by the API manager.

### Claim 6 (depends on 3)

The server of claim 3, wherein the rule setting the verbosity level is based on the type of request sent to the API manager.

### Claim 7 (depends on 1)

The sealer of claim 1, wherein the log verbosity rules are executed in real time.

### Claim 8

A method of generating togs, comprising:
receiving, at an application program interface (API) manager, a request from a client device;
evaluating content of the request;
executing a log rule received from a dynamic log rule registry; and
setting a log verbosity according to the log rule.

### Claim 9 (depends on 8)

The method of claim 8, wherein setting the log verbosity includes setting the log verbosity via a hypertext transfer protocol (HTTP) header.

### Claim 10 (depends on 8)

The method of claim 8, comprising, with the log rule, creating log verbosity levels.

### Claim 11 (depends on 10)

The method of claim 10, wherein the log rule comprises criteria that for the log verbosity levels, the criteria comprising an IP address associated with the request, details regarding a header of the request, content of the request, a timestamp of the request, a sender of the request (authentication), a size of the request, and access permissions of a sender (authorization) of the request.

### Claim 12 (depends on 10)

The method of claim 10, comprising receiving at an administrator's endpoint device, dynamic rules to be stored in the dynamic log rule registry, the dynamic rules being updated independent of a redeployment of an application.

### Claim 13

A log generation system, comprising:
an administrator device; and
an application programming interface (API) manager communicatively coupled to the administrator device, the application programming interface (API) manager comprising:
a request evaluation module to, when executed by a processor,
evaluate a request received from a client device at the API manager;
a log rules registry to maintain a plurality of dynamic log verbosity rules;
a log verbosity adjustment module to, when executed by the processor, apply the dynamic log verbosity rules to the request and adjust the verbosity of a generated log to be written by the API.

### Claim 14 (depends on 13)

The log generation system of claim 13, wherein the log rule registry comprises rules setting criteria that create log verbosity levels, the criteria comprising an IP address associated with the request, details regarding a header of the request, content of the request, a timestamp of the request, a sender of the request (authentication), a size of the request, and access permissions of a sender (authorization) of the request.

### Claim 15 (depends on 14)

The log generation system of claim 14, wherein the log verbosity levels define the verbosity of log saved by the API to a log repository.
