Api dependency error and latency injection
Abstract
Described embodiments provide systems and methods for validating a microservice. A device intermediary to a plurality of microservices may identify a synthetic error and a first criteria for implementing the synthetic error to validate a first microservice of the plurality of microservices. The device may determine that the first criteria for implementing the synthetic error has been met. The device may receive a request from the first microservice to access a second microservice of the plurality of microservices. Responsive to the determination, the device may transmit, to the first microservice, a response on behalf of the second microservice, the response implementing the synthetic error. The device may validate that the first microservice one of handled or did not handle the synthetic error.
Claims
exact text as granted — not AI-modifiedWe claim:
1 . A method comprising:
identifying, by a device, a synthetic error and a threshold for a usage of a service to trigger injecting the synthetic error; comparing, by the device, the usage of the service to the threshold; determining, by the device, to inject the synthetic error based on the usage of the service being within the threshold; injecting, by the device responsive to the determination, the synthetic error as a response to a request from the service; and determining, by the device, whether the service handled the synthetic error.
2 . The method of claim 1 , wherein the usage of the service comprises one of a number of users or a number of connections being less than the threshold.
3 . The method of claim 1 , wherein the usage of the service comprises one of a processor or a memory usage being less than the threshold.
4 . The method of claim 1 , wherein the usage of the service comprises an uptime greater than the threshold.
5 . The method of claim 1 , further comprising determining, by the device, that the service handled the synthetic error properly responsive to one of the service resuming normal operations within a time period or reporting an error or logging an error.
6 . The method of claim 1 , further comprising determining, by the device, that the service did not handle the synthetic error properly responsive to one of the following: the service is unable to recover, the service is unable to resume normal operations, the services fails to log or report an error, communications with the service are impaired or delayed, a user of the service experiences dropouts, delays or errors.
7 . The method of claim 1 , wherein the request from the service comprises an application programming interface (API) call to another service.
8 . The method of claim 1 , wherein the service comprises a microservice.
9 . A system comprising:
one or more processors, coupled to memory, and configured to:
identify a synthetic error and a threshold for a usage of a service to trigger injecting the synthetic error;
compare the usage of the service to the threshold;
determine to inject the synthetic error based on the usage of the service being within the threshold;
inject, responsive to the determination, the synthetic error as a response to a request from the service; and
determine whether the service handled the synthetic error.
10 . The system of claim 9 , wherein the usage of the service comprises one of a number of users or a number of connections being less than the threshold.
11 . The system of claim 9 , wherein the usage of the service comprises one of a processor or a memory usage being less than the threshold.
12 . The system of claim 9 , wherein the usage of the service comprises an uptime greater than the threshold.
13 . The system of claim 9 , wherein the one or more processors are further configured to determine that the service handled the synthetic error properly responsive to one of the service resuming normal operations within a time period or reporting an error or logging an error.
14 . The system of claim 9 , wherein the one or more processors are further configured to determine that the service did not handle the synthetic error properly responsive to one of the following: the service is unable to recover, the service is unable to resume normal operations, the services fails to log or report an error, communications with the service are impaired or delayed, a user of the service experiences dropouts, delays or errors.
15 . The system of claim 9 , wherein the request from the service comprises an application programming interface (API) call to another service.
16 . The system of claim 9 , wherein the service comprises a microservice
17 . A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
identify a synthetic error and a threshold for a usage of a service to trigger injecting the synthetic error; compare the usage of the service to the threshold; determine to inject the synthetic error based on the usage of the service being within the threshold; inject, responsive to the determination, the synthetic error as a response to a request from the service; and determine whether the service handled the synthetic error.
18 . The non-transitory computer-readable medium of claim 15 , wherein the usage of the service comprises one of a number of users or a number of connections being less than the threshold.
19 . The non-transitory computer-readable medium of claim 15 , wherein the usage of the service comprises one of a processor or a memory usage being less than the threshold.
20 . The non-transitory computer-readable medium of claim 15 , wherein the usage of the service comprises an uptime greater than the threshold.Join the waitlist — get patent alerts
Track US2022224619A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.