Log File Parsing for Multi-Tenant Data Privacy

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-tenant database systems, existing technologies face challenges in providing tailored log file data to tenants while maintaining data privacy and security, as log files contain data from multiple tenants, requiring parsing to exclude sensitive information and generate customer-facing logs.

Innovation Solution

A system and method for parsing log files to generate customer-facing logs by selecting specific log entries and data fields, using map reduce logic and XML data files to determine approved entries and fields, ensuring that only relevant data is provided to tenants, thereby reducing the amount of data and enhancing its meaningfulness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If log files from multi-tenant database systems are provided to tenants, then tenants can access their operational data, but sensitive information from other tenants and internal system metrics are exposed

Engineering Contradiction:
Improvedata privacyVSAvoidlog processing complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the log file processing into distinct components: log collection from multiple sources, log parsing to extract relevant fields, log enrichment to add contextual information, and log delivery to appropriate tenants. This segmentation allows each component to be optimized independently and resolves the contradiction by making the complex processing manageable through modular architecture

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary log service layer between the multi-tenant database system and tenants. This intermediary service collects logs, parses them to remove sensitive information, enriches them with relevant context, and delivers only appropriate information to each tenant. This mediator resolves the privacy issue while managing complexity through a centralized processing layer

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If all log file data is provided to tenants, then complete operational information is available, but data volume becomes unmanageable and processing overhead increases

Engineering Contradiction:
Improveinformation completenessVSAvoiddata volume
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The patent applies local quality by customizing log content for each tenant based on their specific needs and characteristics. Each tenant receives log data with fields and levels tailored to their operational context, rather than a uniform approach. This resolves the contradiction by providing information completeness where needed while reducing data volume through tenant-specific customization

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent implements partial action by selectively including only the necessary log fields and levels for each tenant rather than providing all available log data. The system determines the optimal subset of log information for each tenant, providing sufficient detail for operational monitoring while avoiding the overhead of processing and transmitting excessive data

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If log parsing is implemented to exclude sensitive information, then data privacy is improved, but processing time and computational resources increase

Engineering Contradiction:
Improvedata securityVSAvoidlog processing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-defining log field configurations and sensitivity classifications before log processing begins. The system pre-configures which log fields are sensitive and require masking, and pre-establishes the parsing rules for different log types. This resolves the contradiction by preparing the filtering framework in advance, reducing the computational burden during actual log processing while maintaining data security

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent applies parameter changes by dynamically adjusting log processing parameters such as log levels, field inclusion/exclusion criteria, and parsing depth based on tenant preferences and system conditions. This allows the system to optimize processing time by adjusting parameters like only parsing critical fields during high-load periods while maintaining security through consistent application of sensitivity rules

Inventive Principle:
Principle #35Parameter changes

4Loss of information

If custom log field selections are provided to tenants, then data relevance is improved, but system complexity and configuration overhead increase

Engineering Contradiction:
Improvedata relevanceVSAvoidsystem configuration complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent implements universality by creating a standardized log field configuration framework that serves all tenants while allowing individual customization. The system provides a universal set of log field templates and selection mechanisms that can be applied across different tenants with varying needs. This resolves the contradiction by providing data relevance through customizable configurations while reducing system complexity through a unified, multi-functional configuration system

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10332129B2Methods and systems for processing a log file
Publication Date: 2019.06.25 SALESFORCE INC
  • US10332129B2 patent drawing
  • US10332129B2 patent drawing
  • US10332129B2 patent drawing

AI summary

Disclosed are methods, apparatus, systems, and computer program products for provisioning log file data. To provision the log file data, a server can parse through log files by identifying particular log entries and data fields. Customer-facing log files can be generated based on the identified log entries and data fields. A customer-facing log file has log file data specific to a particular customer, which can be a tenant of a multi-tenant database system. A security mechanism can be configured to prevent one tenant from accessing the customer-facing log file of another tenant of the multi-tenant database system.