Monitoring Agent Configuration Management via Unique Markers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing the configuration lifecycle of monitoring agents in computing environments is tedious and requires manual intervention, especially when multiple applications and instances are involved, with existing tools lacking tight integration and automation for updates and rogue agent management.

Innovation Solution

An application monitoring server with an agent monitoring unit that generates unique markers to identify applications, bundles configuration data within these markers, and manages the configuration lifecycle by appending them to monitoring agent configuration files, enabling automated monitoring, updating, and disabling processes without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If manual management methods are used for monitoring agent configuration, then flexibility and control are maintained, but the time consumption and operational complexity increase significantly

Engineering Contradiction:
Improvetime consumptionVSAvoidoperational complexity
Core Design Contradiction:
Loss of timeVSEase of operation

Solution Approach 1:

The system enables self-service through automated configuration management where the monitoring agent automatically receives, processes, and applies configuration updates from the server without requiring manual intervention. The agent autonomously manages its configuration lifecycle including updates, validations, and rollback operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary actions by pre-configuring and pre-validating configuration data on the server before deployment. Configuration templates and policies are prepared in advance, and the system performs preliminary checks to ensure configuration validity before applying changes to monitoring agents.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If automated management systems are implemented, then efficiency and productivity improve, but system complexity and integration requirements increase

Engineering Contradiction:
Improvemanagement efficiencyVSAvoidsystem integration complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The monitoring agent is designed as a universal component that can manage configurations for multiple applications and services across different endpoints. The agent monitoring unit on the server provides multi-functional capabilities including configuration distribution, update management, validation, and rogue agent detection through a single integrated system.

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

Solution Approach 2:

The system introduces an intermediary layer (the agent monitoring unit and marker mechanism) that mediates between the central server and distributed monitoring agents. This intermediary manages configuration data through standardized markers and protocols, simplifying integration while maintaining centralized control and automated management capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If configuration data is updated frequently, then system adaptability and responsiveness improve, but stability and reliability may be compromised

Engineering Contradiction:
Improveconfiguration responsivenessVSAvoidsystem stability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system implements feedback mechanisms where configuration changes are validated, tested, and monitored before full deployment. The agent monitoring unit tracks configuration updates and their effects, providing feedback to the server to determine whether further updates are appropriate or if rollback is necessary, thus maintaining stability while enabling adaptability.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system provides beforehand cushioning through configuration validation and backup mechanisms. Before applying configuration updates, the system validates the configuration data against predefined policies and maintains previous working configurations as backups, allowing safe rollback if updates cause instability.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Loss of information

If centralized management is implemented, then control and coordination improve, but loss of information and communication overhead increase

Engineering Contradiction:
Improveconfiguration data consistencyVSAvoidcommunication infrastructure
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The system segments configuration management into modular components: configuration templates on the server, configuration data transmitted through standardized markers, and local configuration storage on agents. This segmentation reduces information loss by ensuring structured, complete data transmission while simplifying the communication infrastructure through standardized interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system uses copying mechanisms where configuration data is replicated from the central server to monitoring agents through standardized markers. Configuration templates are copied and adapted locally, ensuring data consistency across the distributed system while reducing communication overhead through efficient data replication strategies.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11575763B2System and method for managing configuration data of monitoring agents
Publication Date: 2023.02.07 VMWARE INC
  • US11575763B2 patent drawing
  • US11575763B2 patent drawing
  • US11575763B2 patent drawing

AI summary

In one example, a computer implemented method may include determining an application to be monitored in an endpoint, generating a marker with a unique identifier corresponding to the application running in the endpoint, bundling configuration data within the marker. The configuration data may include configuration settings of a monitoring agent installed on the endpoint to monitor the application. Further, the method may include appending the marker bundled with the configuration data to a configuration file of the monitoring agent and enabling the monitoring agent to monitor the application based on the configuration data in the configuration file.