Service-Aware Mapping Logic for IT Infrastructure Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed computing environments, managing and tracking the configuration of geographically dispersed IT devices becomes increasingly complex due to rapid infrastructure changes and the inter-dependencies between resources, making manual approaches insufficient for maintaining an up-to-date service-aware view of the system infrastructure.
Innovation Solution
Implementing service mapping logic that generates a real-time, accurate service-aware view of the IT system infrastructure by discovering and mapping relationships between IT components, including host-less components like Platform as a Service (PaaS) services, and providing guidance for creating new discovery patterns based on traffic-based connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If manual approaches are used to track infrastructure changes, then simplicity of operation is maintained, but the service mapping becomes out-of-date and unreliable
Solution Approach 1:
The system performs self-service by automatically discovering infrastructure changes and updating service mappings without manual intervention. The service mapping logic continuously monitors the IT infrastructure, detects changes, and refreshes mappings autonomously, eliminating the need for manual tracking while maintaining current and accurate service maps.
Solution Approach 2:
The system implements feedback mechanisms by continuously monitoring the IT infrastructure for changes and using this information to update service mappings in real-time. The service mapping logic receives feedback from infrastructure monitoring and automatically adjusts mappings to reflect current system state, ensuring reliability without manual intervention.
2Reliability
If frequent updates of service mappings are performed, then the service-aware view remains current and reliable, but the system complexity and resource consumption increase
Solution Approach 1:
The service mapping system is designed to be dynamic, automatically adapting its update frequency and depth based on detected infrastructure changes. Rather than performing rigid frequent updates, the system dynamically responds to actual changes in the IT infrastructure, refreshing mappings only when necessary to maintain currency while minimizing unnecessary complexity and resource consumption.
Solution Approach 2:
The system performs preliminary actions by proactively discovering and monitoring infrastructure changes before they impact service mappings. The service mapping logic continuously scans for changes and prepares updates in advance, ensuring mappings remain current without requiring complex real-time processing of every infrastructure event.
3Loss of information
If comprehensive monitoring of all IT components is implemented, then complete service-aware understanding is achieved, but the data collection and processing overhead increases
Solution Approach 1:
The system extracts only the essential information needed for service-aware mapping from the comprehensive IT infrastructure data. Rather than collecting and processing all possible data about every component, the service mapping logic selectively extracts relationships and changes that directly impact service mappings, reducing data collection overhead while maintaining complete visibility of service relationships.
Solution Approach 2:
The monitoring system applies local quality by focusing detailed monitoring efforts on components and relationships that are locally relevant to service mappings. Rather than uniformly monitoring all IT components with equal intensity, the system concentrates monitoring resources on areas that directly affect service-aware understanding, reducing overall resource consumption while maintaining necessary visibility.
Data Source
AI summary
Systems, methods, and media for finding configuration files are presented. Traffic-based connections may provide search parameter insight for searching a component for configuration data. The search parameters derived from the traffic-based connections may be used to facilitate discovery of configuration files in non-conventional locations. Further, Platform as a Service (PaaS) components may be discovered using specialized pattern operations.