System Interaction Monitoring And Component Scaling
US-2017289307-A1 · Oct 5, 2017 · US
US12164416B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12164416-B2 |
| Application number | US-202318135803-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 18, 2023 |
| Priority date | Jun 27, 2019 |
| Publication date | Dec 10, 2024 |
| Grant date | Dec 10, 2024 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Techniques for monitoring operating statuses of an application and its dependencies are provided. A monitoring application may collect and report the operating status of the monitored application and each dependency. Through use of existing monitoring interfaces, the monitoring application can collect operating status without requiring modification of the underlying monitored application or dependencies. The monitoring application may determine a problem service that is a root cause of an unhealthy state of the monitored application. Dependency analyzer and discovery crawler techniques may automatically configure and update the monitoring application. Machine learning techniques may be used to determine patterns of performance based on system state information associated with performance events and provide health reports relative to a baseline status of the monitored application. Also provided are techniques for testing a response of the monitored application through modifications to API calls. Such tests may be used to train the machine learning model.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: collecting, by one or more data collecting agents and at a first time, first system state information corresponding to a first application; detecting, by a testing agent, a first call in a computing system from the first application to a first Application Programming Interface (API) during a testing period and at a second time; modifying, by the testing agent, a response to the first call, wherein the modified response simulates an artificial unhealthy operating status of the first API; returning the modified response to the first application in response to the first call; collecting, by the one or more data collecting agents and after returning the modified response, second system state information corresponding to the first application; training a machine learning model based on the first system state information and the second system state information, wherein the trained machine learning model is configured to determine a pattern of performance associated with the first application and the first API that indicates a potential correlation between performance of the first API and performance of the first application; collecting, by the one or more data collecting agents, third system state information corresponding to the first application and the first API; and generating, using the trained machine learning model and based on the pattern of performance, a report associated with the performance of the first application based on the third system state information. 2. The method of claim 1 , wherein a second call to the first API is unaffected by modifying the response to the first call. 3. The method of claim 1 , wherein the modified response simulates the artificial unhealthy operating status of the first API by simulating an artificially high latency associated with the first API. 4. The method of claim 1 , wherein the modified response simulates the artificial unhealthy operating status of the first API by simulating an error result associated with the first API. 5. The method of claim 1 , further comprising: caching, by the testing agent, the unmodified response; determining, by a monitoring application, whether the first application was able to recover from the modified response returning a failed result; and based on determining that the first application was not able to recover, causing the computing system to return the cached unmodified response to the first application. 6. The method of claim 5 , wherein the first application is determined to have been able to recover when the monitoring application determines that the first application was able to retrieve information associated with the first API from another source. 7. The method of claim 1 , wherein detecting the first call to the first API is based on determining that the first API is a dependency of the first application. 8. The method of claim 1 , wherein the testing agent is part of a monitoring application configured to monitor the first application using a plurality of monitoring interfaces, wherein detecting the first call to the first API is based on determining that the monitoring application is configured to monitor the first API. 9. The method of claim 1 , wherein the first system state information comprises information indicating one or more of: whether a resource associated with the first API is accessible; a response latency associated with requests to the first API; an error rate associated with requests to the first API; or an error state or error message provided by the first API. 10. The method of claim 1 , wherein the pattern of performance is a pattern of failure and indicates a potential correlation between a first attribute of system state information corresponding to the first API and the first application entering an unhealthy operating status. 11. The method of claim 1 , wherein the pattern of performance is a pattern of risk and indicates a potential correlation between a first attribute of system state information corresponding to the first API and a level of security risk to the first application. 12. The method of claim 1 , wherein the pattern of performance is a pattern of latency and indicates a potential correlation between a first attribute of system state information corresponding to the first API and a latency associated with requests to the first application. 13. A monitoring system comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the monitoring system to: collect, by one or more data collecting agents and at a first time, first system state information corresponding to a first application; detect, by a testing agent, a first call in a computing system from the first application to a first Application Programming Interface (API) during a testing period and at a second time; modify, by the testing agent, a response to the first call, wherein the modified response simulates an artificial unhealthy operating status of the first API; return the modified response to the first application in response to the first call; collect, by the one or more data collecting agents and after returning the modified response, second system state information corresponding to the first application; train a machine learning model based on the first system state information and the second system state information, wherein the trained machine learning model is configured to determine a pattern of performance associated with the first application and the first API that indicates a potential correlation between performance of the first API and performance of the first application; collect, by the one or more data collecting agents, third system state information corresponding to the first application and the first API; and generate, using the trained machine learning model and based on the pattern of performance, a report associated with the performance of the first application based on the third system state information. 14. The monitoring system of claim 13 , wherein the modified response simulates the artificial unhealthy operating status of the first API by simulating an artificially high latency associated with the first API or an error result associated with the first API. 15. The monitoring system of claim 13 , wherein the instructions further cause the monitoring system to: cache, by the testing agent, the unmodified response; determine, by a monitoring application, whether the first application was able to recover from the modified response returning a failed result; and based on determining that the first application was not able to recover, cause the computing system to return the cached unmodified response to the first application. 16. The monitoring system of claim 13 , wherein the pattern of performance is a pattern of failure and indicates a potential correlation between a first attribute of system state information corresponding to the first API and the first application entering an unhealthy operating status. 17. A non-transitory computer readable medium comprising instructions that, when executed by one or more processors of a monitoring system, cause the monitoring system to: collect, by one or more data collecting agents and at a first time, first system state information corresponding to a first application; detect, by a testing agent, a first call in a computing system from the first application to a first Application Programming Interface (API) during a testing period and at a second time; modify, by the
Environments for analysis, debugging or testing of software · CPC title
Machine learning · CPC title
using formal methods, e.g. model checking, abstract interpretation (theorem proving G06N5/013) · CPC title
for test results analysis · CPC title
for test execution, e.g. scheduling of test suites · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.