Network Client Log Collection via Dynamic Collector Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional log collection systems struggle to efficiently switch log collection for newly added services, as they are typically managed on a per-module basis, which limits flexibility and scalability, particularly in handling different event types and triggers.
Innovation Solution
A network client with multiple collectors that manage correspondence relationships between collection types and event types, allowing for dynamic selection and instruction of appropriate collectors based on received event collection requests, enabling flexible log collection based on designated types and triggers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If log collection is managed on a per-module basis using separate event collection modules for each legacy module, then each module can be independently configured, but the system cannot efficiently switch log collection for newly added services and lacks flexibility and scalability
Solution Approach 1:
The system segments log collection functionality into independent collector components, each responsible for specific event types. The first table segments event information by type, while the second table segments collectors by their correspondence to collection types, enabling granular control without monolithic complexity
Solution Approach 2:
The patent creates a universal log collection framework where multiple collectors can handle different event types through standardized table-based correspondence relationships. This universal structure allows new services to be added without creating dedicated module-specific collectors, providing multi-functionality across diverse service types
2Adaptability or versatility
If different event collection modules are prepared for respective legacy modules with logs output after being shaped, then module-specific log formatting is achieved, but switching log collection on a unit basis different from module operating units cannot be dealt with
Solution Approach 1:
The system performs preliminary action by pre-establishing the two-table correspondence structure before new services are added. The first table pre-defines event type classifications, and the second table pre-maps collectors to collection types, enabling rapid log collection switching without time-consuming reconfiguration when new services are introduced
Solution Approach 2:
The patent introduces intermediary table structures that mediate between legacy modules and the log collection system. The first table acts as an intermediary layer for event type standardization, and the second table serves as an intermediary mapping layer between collection types and collectors, enabling flexible switching without direct module-specific configuration
Data Source
AI summary
A network client includes a correspondence table between collection types set by a management server and event collection modules in the client, and a correspondence table between the collection types set by the management server and event types in the client, and switches output of an event log in units of a collection type requested by the management server.