API Anomaly Detection via Dependency Service Notification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Computer services face challenges in detecting and notifying errors caused by dependency services in API calls, leading to inefficiencies in identifying and mitigating API anomalies, which can result in network errors and data corruption.
Innovation Solution
An API notification service is introduced to monitor service logs, apply configurable service level agreements (SLAs) to detect errors and corruption, and determine the responsible dependency service, enabling real-time notification and mitigation of API anomalies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If computer services call other computer services in a dependency chain, then service functionality and integration are improved, but error detection and notification capability deteriorate because the calling service cannot determine whether an error was caused by itself or by a dependency service
Solution Approach 1:
The patent implements feedback by having the dependency service send a notification back to the calling service when an error occurs. The notification includes error information and identifies the dependency service as the error source, enabling the calling service to understand whether the error originated from itself or from a service it depends on.
Solution Approach 2:
The notification mechanism acts as an intermediary between the dependency service and the calling service. Instead of the calling service directly determining the error source (which is difficult), the notification system mediates by transmitting error information from the dependency service to the calling service, making error source identification possible.
2Loss of time
If real-time error notification is implemented across dependency services, then error mitigation speed is improved, but system complexity increases due to the need for notification mechanisms and service level agreement validation
Solution Approach 1:
The patent applies preliminary action by establishing service level agreements (SLAs) before errors occur. The SLAs define error conditions and notification protocols in advance, so when an error occurs, the system can immediately apply the pre-defined notification logic without needing to complex decision-making at error time.
Solution Approach 2:
The system changes parameters by validating API calls against configurable service level agreements. When parameters (error conditions) match the SLA definitions, automated notifications are triggered. This parameter-based approach simplifies the notification system by using configurable rules rather than complex hard-coded logic.
Data Source
AI summary
Devices, systems, and methods are provided for detecting and mitigating application programming interface (API) anomalies. A method may include identifying, based on a first data log, first API data associated with a first API call and a first computer service, and identifying an agreement associated with the first computer service, the agreement including criteria associated with the first API data. The method may include determining that the first API data fails to satisfy the criteria. The method may include determining one or more service dependencies, the one or more service dependencies indicating that operation of the first service depends on operation of a second computer service. The method may include determining, based on the one or more service dependencies, one or more services to which to send notifications indicative of the criteria. The method may include sending the notifications to the one or more services.