Workflow Efficiency via Client-Server Log Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Remote network management platforms face challenges in determining the root cause of performance inefficiencies, such as completion delays and incorrect outcomes, due to the complexity of workflows involving multiple states and transitions across various systems and roles.

Innovation Solution

Deploying client-side collectors on endpoint devices to collect interaction data with applications, combined with server-side logs, allows for a comprehensive view of workflow efficiency by correlating workflow identifiers and applying rules to suggest performance improvements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If server-side logs alone are used to analyze workflow performance, then the analysis system remains simple, but the ability to determine root cause of performance inefficiencies is insufficient

Engineering Contradiction:
Improveroot cause determination accuracyVSAvoidclient-side interaction data
Core Design Contradiction:
Measurement precisionVSLoss of information

Solution Approach 1:

The patent combines server-side logs with client-side logs to create a comprehensive data set for workflow analysis. The server-side log contains workflow identifier and server activities, while the client-side log contains client device operational data and user interactions. By merging these two data sources and correlating them through workflow identifiers, the system achieves complete visibility into workflow performance and can accurately determine root causes of inefficiencies.

Inventive Principle:
Principle #5Merging (Combining)

2Measurement precision

If client-side collectors are deployed to gather detailed interaction data, then workflow analysis precision improves, but system complexity increases

Engineering Contradiction:
Improveworkflow efficiency measurement accuracyVSAvoiddata collection infrastructure
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent introduces a workflow identifier as an intermediary element that links server-side and client-side data. Instead of creating a complex direct integration between server and client systems, the workflow identifier acts as a common key that both sides use to tag their log entries. This intermediary approach simplifies the data collection infrastructure while maintaining high measurement precision.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Loss of information

If comprehensive client-side and server-side data are integrated, then workflow performance understanding improves, but data processing complexity increases

Engineering Contradiction:
Improvecomprehensive workflow visibilityVSAvoiddata correlation and processing system
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the data processing into distinct components: server-side log collection, client-side log collection, and correlated analysis. Each component handles a specific portion of the data independently, then the results are combined through workflow identifier matching. This segmentation reduces the complexity of data processing by avoiding the need to handle all data simultaneously in a monolithic system.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12095842B2Server-side workflow improvement based on client-side data mining
Publication Date: 2024.09.17 SERVICENOW INC
  • US12095842B2 patent drawing
  • US12095842B2 patent drawing
  • US12095842B2 patent drawing

AI summary

An embodiment may involve a server-side log collected by a server device, where the server-side log includes a set of entries indicating a unique identifier, and wherein the unique identifier is assigned to a work item of a server-based application executed by the server device. The embodiment may further involve one or more processors configured to: receive, from a client device disposed upon a network, a client-side log, wherein the client-side log includes operational data related to usage of a client-based application executed by the client device; identify, from the operational data, the client-based application and one or more activities performed by the client-based application; determine that the one or more activities are related to the unique identifier; based on the one or more activities, determine an action that can be taken to improve efficacy of the server-based application; and write, to the persistent storage, a representation of the action.