API Gateway Request Tracking for Cloud SIT Accuracy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current cloud computing systems face challenges in accurately tracking API requests during system integration testing (SIT) to ensure the correct execution and impact analysis of API interactions within the system.
Innovation Solution
Implementing an API gateway with counters to track API requests, which validates and increments counts for each API endpoint, method, header, and parameter, allowing for detailed analysis of API usage patterns and impact assessment during SIT automation testing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If traditional SIT testing methods are used without API request tracking, then the testing process is simpler, but the ability to accurately track and analyze API interactions is insufficient
Solution Approach 1:
The patent introduces an API gateway as an intermediary component between the testing system and the target system. The gateway intercepts, validates, and tracks all API requests before they reach the target system, providing comprehensive tracking capabilities without modifying the target system itself. This mediator approach enables precise measurement of API interactions while keeping the core testing framework relatively simple.
Solution Approach 2:
The API gateway performs self-service by automatically validating, tracking, and counting API requests without requiring external intervention for each request. The gateway maintains its own counter data and automatically generates tracking information, reducing the complexity burden on the overall testing system while providing accurate measurement capabilities.
2Loss of information
If comprehensive API request tracking is implemented, then detailed API usage analysis is enabled, but the complexity of the testing system increases
Solution Approach 1:
The patent implements preliminary action by pre-configuring the API gateway with validation rules, counter configurations, and tracking parameters before testing begins. The gateway is pre-prepared to automatically track specific API endpoints, methods, headers, and parameters, eliminating the need for complex post-processing setup and reducing overall system complexity while ensuring complete information capture.
Solution Approach 2:
The tracking system is segmented into distinct functional components within the API gateway: request validation module, counter management module, and tracking data generation module. This segmentation allows each component to handle specific aspects of API tracking independently, making the overall system more manageable and less complex while maintaining comprehensive tracking capabilities.
3Measurement precision
If API counters track multiple parameters (endpoint, method, header, parameter), then tracking precision is improved, but the data processing complexity increases
Solution Approach 1:
The patent merges multiple tracking dimensions (API endpoint, method, header, and parameters) into a unified counter data structure within the API gateway. Instead of maintaining separate tracking systems for each parameter type, the gateway combines them into integrated counter records that capture all relevant API request details in a single coherent data model, simplifying data processing while maintaining high measurement precision.
Data Source
AI summary
Techniques are provided for tracking application programming interface (API) requests in a cloud computing environment. For example, a method for tracking API requests is implemented by an API gateway. The API gateway receives an API request which comprises a given API endpoint to access a target service of a computing system. The API gateway determines if the received API request is valid. In response to determining that the received API request is valid, the API gateway accesses at least one API counter associated with the given API endpoint of the received API request, wherein the at least one API counter is configured to count a number of times that the given API endpoint is accessed. The API gateway increments a count of the at least one API counter by one, and the API gateway routes the API request to the target service for execution.