Automatic microgateway taxonomy tags
Disclosed herein are system, method, and computer program product embodiments for implementing automatic taxonomy tags in an API microgateway. The API microgateway may receive a plurality of API requests for an API managed by a customer in a period of time and route the plurality of API request to an instance of the API according to a policy of the API. The API microgateway may aggregate metrics information related to the plurality of API requests. The aggregated metrics information may include request features, response features, policy features, and performance features. In response to a cluster of the metrics information corresponding to a tag in a tag prediction system, the aggregated metrics information may be labeled with the tag. The tag and the aggregated metrics information may be added to an access log and sent to the customer.
1. A method, comprising:
receiving via an application programming interface (API) microgateway, a plurality of API requests for an API in a period of time, the API being monitored by a monitoring system,
routing the plurality of API requests to an instance of the API in response to a violation of a rate limiting policy of the API, wherein the rate limiting policy defines a triggering condition specified for the API and wherein the triggering condition includes a threshold number of API requests in the period of time for the instance of the API;
aggregating metrics information related to the plurality of API requests, wherein the metrics information includes statistics of the plurality of API requests, responses to the plurality of API requests, the violation of the rate limiting policy, and performance statistics to process the plurality of API requests;
fitting the metrics information to a cluster using a clustering model;
labelling, in response to the cluster corresponding to a tag in a tag prediction system, the metrics information with the tag, wherein the tag indicates a current status of the API and the API microgateway; and
sending the tag and the corresponding metrics information for the API and the API microgateway to the monitoring system.
2. The method of claim 1 , further comprising updating the rate limiting policy of the API according to feedback relating to the tag based on the metrics information.
3. The method of claim 1 , further comprising updating the tag for the cluster of the metrics information in the tag prediction system according to feedback relating to the tag based on the metrics information.
4. The method of claim 1 , further comprising adding an additional instance of the API to respond to the plurality of API requests.
5. The method of claim 1 , further comprising storing the tag and the metrics information in an access log.
6. The method of claim 1 , in response to the cluster of the metrics information corresponding to no tag in the tag prediction system, further comprising:
receiving a customer tag for the cluster of the metrics information;
training the tag prediction system with the customer tag and the cluster of the metrics information; and
associating the customer tag with the cluster of the metrics information.
7. The method of claim 1 , wherein the metrics information includes a satisfaction of the triggering condition, a memory usage, and a CPU usage for the instance of API in the period of time and wherein the tag for the cluster of the metrics information includes a denial-of-service attack.
8. A system, comprising:
a memory; and
at least one processor coupled to the memory and configured to:
receive, via an application programming interface (API) microgateway, a plurality of API requests for an API in a period of time, the API being monitored by a monitoring system;
route the plurality of API requests to an instance of the API in response to a violation of a rate limiting policy of the API, wherein the rate limiting policy defines a triggering condition specified for the API and wherein the triggering condition includes a threshold number of API requests in the period of time for the instance of the API;
aggregate metrics information related to the plurality of API requests, wherein the metrics information includes statistics of the plurality of API requests, responses to the plurality of API requests, the violation of the rate limiting policy, and performance statistics to process the plurality of API requests;
fit the metrics information to a cluster using a clustering model;
label, in response to the cluster corresponding to a tag in a tag prediction system, the metrics information with the tag, wherein the tag indicates a current status of the API and the API microgateway; and
send the tag and the corresponding metrics information for the API and the API microgateway to the monitoring system.
9. The system of claim 8 , the at least one processor further configured to update the rate limiting policy of the API according to feedback relating to the tag based on the metrics information.
10. The system of claim 8 , the at least one processor further configured to update the tag for the cluster of the metrics information in the tag prediction system according to feedback relating to the tag based on the metrics information.
11. The system of claim 8 , the at least one processor further configured to add an additional instance of the API to respond to the plurality of API requests.
12. The system of claim 8 , the at least one processor further configured to store the tag and the metrics information in an access log.
13. The system of claim 8 , in response to the cluster of the metrics information corresponding to no tag in the tag prediction system, the at least one processor further configured to:
receive a customer tag for the cluster of the metrics information;
train the tag prediction system with the customer tag and the cluster of the metrics information; and
associate the customer tag with the cluster of the metrics information.
14. The system of claim 8 , wherein the metrics information includes a satisfaction of the triggering condition, a memory usage, and a CPU usage for the instance of the API in the period of time and wherein the tag for the cluster of the metrics information includes a denial-of-service attack.
15. A non-transitory computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:
receiving, via an application programming interface (API) microgateway, a plurality of API requests for an API in a period of time, the API being monitored by a monitoring system;
routing the plurality of API requests to an instance of the API in response to a violation of a rate limiting policy of the API, wherein the rate limiting policy defines a triggering condition specified for the API and wherein the triggering condition includes a threshold number of API requests in the period of time for the instance of the API;
aggregating metrics information related to the plurality of API requests, wherein the metrics information includes statistics of the plurality of API requests, responses to the plurality of API requests, the violation of the rate limiting policy, and performance statistics to process the plurality of API requests;
fitting the metrics information to a cluster using a clustering model;
labelling, in response to the cluster corresponding to a tag in a tag prediction system, the metrics information with the tag, wherein the tag indicates a current status of the API and the API microgateway; and
sending the tag and the corresponding metrics information for the API and the API microgateway to the monitoring system.
16. The non-transitory computer-readable device of claim 15 , the operations further comprising updating the rate limiting policy of the API according to feedback relating to the tag based on the metrics information.
17. The non-transitory computer-readable device of claim 15 , the operations further comprising updating the tag for the cluster of the metrics information in the tag prediction system according to feedback relating to the tag based on the metrics information.
18. The non-transitory computer-readable device of claim 15 , wherein the metrics information includes a satisfaction of the triggering condition, a memory usage, and a CPU usage for the instance of the API in the period of time and wherein the tag for the cluster of the metrics information includes a denial-of-service attack.
19. The non-transitory computer-readable device of claim 15 , the operations further comprising storing the tag and the metrics information in an access log.
20. The non-transitory computer-readable device of claim 15 , in response to the cluster of the metrics information corresponding to no tag in the tag prediction system, the operations further comprising:
receiving a customer tag for the cluster of the metrics information;
training the tag prediction system with the customer tag and the cluster of the metrics information; and
associating the customer tag with the cluster of the metrics information.