SYSTEM AND METHOD FOR INVESTIGATING ANOMALIES IN API PROCESSING SYSTEMS

• US 20150220376A1
• Filed: 02/03/2014
• Published: 08/06/2015
• Est. Priority Date: 02/03/2014
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Apigee Corporation (Alphabet Inc.)
• Inventors: SRIVASTAVA, Kumar
• Granted Patent: US 9,569,332 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/327 Alarm or error message display
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3452 Performance evaluation by statistical analysis
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring

Abstract

A method is provided for detecting irregularities of one or more application programmer interface (API) entities. The method includes receiving a request for data of one or more API entities. The method further includes monitoring said data from at least one server and detecting irregularities in the data. The method also includes displaying information pertaining to the irregularities to a user.

Claims

1. A method for detecting irregularities of one or more application programmer interface (API) entities comprising:

receiving a request for data of one or more API entities,

monitoring said data from at least one server,

detecting irregularities in the data, and

displaying information pertaining to the irregularities to a user.

2. The method of claim 1, wherein the displaying includes displaying information on a graphical user interface (GUI).

3. The method of claim 1, further comprising attributing the detected irregularities to at least one API entity.

4. The method of claim 1, further comprising automatic or user-controlled correction of the irregularities.

5. The method of claim 1, wherein the information comprises at least one of hypothesis, validation, and corrective action pertaining to the detected irregularities.

6. The method of claim 1, wherein the irregularities include traffic spikes or drops pertaining to a change in behavior of one or more API entity.

7. The method of claim 1, wherein detecting the irregularities includes analyzing historical data to determine a baseline and said baseline is compared with current API traffic.

8. The method of claim 7, wherein the baseline is determined from prior daily moving averages of traffic.

9. The method of claim 7, wherein at least one irregularity is found when current API traffic deviates from the baseline by a predetermined threshold.

10. The method of claim 1, wherein detecting the irregularities includes determining a duration of a spike or drop in data in order to establish a behavior of at least one API entity.

17. The system of claim 1, wherein the processor detects the irregularities by analyzing historical data to determine a baseline and said baseline is compared with current API traffic.

18. The system of claim 17, wherein the baseline is determined from prior daily moving averages of traffic.

19. The system of claim 17, wherein the processor finds at least one irregularity when current API traffic deviates from the baseline by a predetermined threshold.

11. An application program interface (API) analytics system for detecting irregularities of one or more application programmer interface (API) entities comprising:

an API gateway receiving a request for data of one or more API entities,

a processor monitoring said data from at least one server and detecting irregularities in the data, and

a display unit displaying information pertaining to the irregularities to a user.

12. The system of claim 11, wherein the display unit displays information on a graphical user interface (GUI).

13. The system of claim 11, wherein detecting irregularities includes attributing the detected irregularities to at least one API entity.

14. The system of claim 11, further comprising an interface for automatic or user-controlled correction of the irregularities.

15. The system of claim 11, wherein the information comprises at least one of hypothesis, validation, and corrective action pertaining to the detected irregularities.

16. The system of claim 11, wherein the irregularities include traffic spikes or drops pertaining to a change in behavior of one or more API entity.

20. The system of claim 11, wherein the processor detects the irregularities by determining a duration of a spike or drop in data in order to establish a behavior of at least one API entity.