Dynamic Event Log Management for SaaS Tenants

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenant Software-as-a-Service (SaaS) environments, the varying event log rates from different tenants lead to inefficient use of computing resources, as existing systems often require frequent generation and deletion of data structures, causing performance delays in log queries and reporting.

Innovation Solution

A system that determines the event rate for each tenant and generates data structures based on a calculated rotation interval, allowing for dynamic storage of event logs within a time window, thereby optimizing resource utilization and reducing the need for frequent data structure changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single-sized data structure is used for storing event logs, then device complexity is reduced, but productivity decreases due to frequent generation and deletion of data structures

Engineering Contradiction:
Improvedata structure management complexityVSAvoidlog query and reporting performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent implements dynamic data structures that automatically adjust their size and retention period based on the event rate of each tenant. The system monitors event rates and modifies data structure parameters (such as time window duration and storage capacity) in real-time, allowing the data structure to adapt to varying log volumes without manual intervention or frequent recreation.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system changes key parameters of the data structure based on event rate measurements. When event rates increase, the system extends the time window and increases storage capacity; when event rates decrease, it reduces these parameters. This dynamic parameter adjustment optimizes both storage efficiency and query performance without requiring system recreation.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If data structures are frequently generated and deleted to accommodate varying event rates, then adaptability improves, but loss of time increases due to performance delays

Engineering Contradiction:
Improveadaptation to varying event ratesVSAvoidtime delay in log queries and reporting
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by proactively adjusting data structure parameters based on predicted event rates. Instead of waiting for event rates to change and then reacting, the system monitors trends and pre-adjusts storage capacity and time windows before peak event rates occur, preventing performance delays during high-volume periods.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent ensures continuous operation of data structures by maintaining them throughout their lifecycle without deletion and recreation. The system continuously monitors event rates and makes incremental adjustments to data structure parameters, ensuring uninterrupted log storage and query capabilities while adapting to changing conditions.

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If storage capacity is increased to accommodate high event rates, then reliability improves, but use of energy increases

Engineering Contradiction:
Improvestorage capacity adequacyVSAvoidcomputing resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system applies local quality by customizing data structure parameters for each tenant based on their specific event rates. Instead of allocating maximum storage capacity to all tenants uniformly, the system assigns storage resources proportional to each tenant's actual needs, optimizing the balance between reliability and energy consumption on a per-tenant basis.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system implements periodic monitoring and adjustment of data structure parameters. Rather than continuously allocating maximum resources, the system periodically evaluates event rates and adjusts storage capacity accordingly, reducing energy consumption during low-event periods while maintaining adequate storage during high-event periods.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS11960943B2Event log management
Publication Date: 2024.04.16 JUNIPER NETWORKS INC
  • US11960943B2 patent drawing
  • US11960943B2 patent drawing
  • US11960943B2 patent drawing

AI summary

Some implementations described herein relate to a system that is configured to obtain one or more event logs associated with a tenant of the system. The system may be configured to determine, based on the one or more event logs, an event rate associated with the tenant and thereby determine, based on the event rate, a rotation interval. The system may be configured to cause, based on the rotation interval, a data structure to be generated for storing event logs associated with the tenant that are obtained during a time window. The system may be configured to obtain, within the time window, one or more additional event logs associated with the tenant and to cause, based on obtaining the one or more additional event logs within the time window, the one or more additional event logs to be stored in the data structure.