Cloud Integration Monitoring via Historical Data Visualization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integration of applications often faces challenges in monitoring the status and identifying errors in integration flows, leading to delayed detection and increased complexity in troubleshooting, which can result in significant time and effort to resolve issues.

Innovation Solution

An integration cloud service system that creates and manages integration flows, collects data, and provides historical visualization and notifications to users, enabling real-time monitoring and quick identification of issues through message generation, data collection, and customizable notifications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If applications are integrated without monitoring mechanisms, then integration complexity is reduced, but the ability to detect and identify errors deteriorates

Engineering Contradiction:
Improveintegration complexityVSAvoiderror detection capability
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces an intermediary monitoring system that sits between integrated applications and captures integration flow data. This mediator collects status information, error logs, and performance metrics without requiring changes to the core application integration logic, thus maintaining simplicity while enabling comprehensive error detection and analysis.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements feedback mechanisms where integration status and error information are continuously collected and provided back to users through monitoring dashboards and alerts. This feedback loop enables real-time detection of integration issues without adding complexity to the integration flow itself, as the monitoring operates independently while providing valuable diagnostic information.

Inventive Principle:
Principle #23Feedback

2Difficulty of detecting and measuring

If comprehensive monitoring is implemented, then error identification capability is improved, but system complexity increases

Engineering Contradiction:
Improveerror identification capabilityVSAvoidsystem complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

The patent segments the monitoring system into distinct modular components: data collection modules that gather integration flow information, processing modules that analyze the collected data, and presentation modules that display results to users. This segmentation allows comprehensive monitoring capability while managing system complexity through modular design, where each component has a specific function and can be independently configured or removed.

Inventive Principle:
Principle #1Segmentation

3Loss of time

If real-time monitoring is implemented, then problem detection speed is improved, but resource consumption increases

Engineering Contradiction:
Improveproblem detection timeVSAvoidresource consumption
Core Design Contradiction:
Loss of timeVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic monitoring where integration status is checked at defined intervals rather than continuously in real-time. This periodic action reduces resource consumption compared to continuous monitoring while still providing timely problem detection. The system can adjust monitoring frequency based on integration criticality and historical performance patterns, optimizing the balance between detection speed and resource usage.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10817488B2Historical data representation in cloud service
Publication Date: 2020.10.27 ORACLE INT CORP
  • US10817488B2 patent drawing
  • US10817488B2 patent drawing
  • US10817488B2 patent drawing

AI summary

Techniques are disclosed for collecting and visualizing historical data. Messages can be generated in response to user requests to make changes to activities in an integration flow. Data associated with the message can be collected in order to generate historical data regarding the message. Depending on the integration flow, a predetermined time point for generating the historical data can be obtained, and the historical data can be generated when the predetermined time point occurs.