Structured Session Identifiers for Cloud Change Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Change management systems face challenges in determining the scope and impact of changes in complex systems with geographically diverse data centers, due to the complexity and variability of resources, and the use of randomly generated session identifiers complicates logging and data correlation.
Innovation Solution
A closed-loop change management system generates a session identifier based on a service identifier and an execution identifier, which is used to track and log changes across multiple resources, facilitating the determination of the scope and impact of changes by correlating actions and results through a unified identifier.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If randomly generated session identifiers are used to track changes across multiple resources, then resource identification is achieved, but logging and data correlation become complicated and less accurate
Solution Approach 1:
The patent changes the parameters of session identifiers from completely random values to structured identifiers that include meaningful components (resource identifiers, change request identifiers, timestamps). This transformation maintains the uniqueness and adaptability of session identifiers while significantly improving their utility for logging and data correlation, as the structured format enables direct correlation between changes and affected resources without complex random mapping.
2Ease of operation
If traditional change management tools are used in complex systems with geographically diverse data centers, then basic change implementation is facilitated, but determining the scope and impact of changes becomes challenging
Solution Approach 1:
The patent implements a feedback mechanism where structured session identifiers are propagated through the entire change management workflow, from initiation to execution to logging. This feedback loop continuously provides information about which resources are affected by which changes, enabling comprehensive tracking of change scope across geographically diverse data centers without losing information about the relationships between changes and resources.
Solution Approach 2:
The patent performs preliminary action by generating structured session identifiers before changes are executed, incorporating resource identifiers and change request information in advance. This preliminary structuring of identification data enables subsequent easy determination of change scope and impact, as the correlation information is already embedded in the identifiers rather than requiring post-hoc analysis.
3Measurement precision
If structured session identifiers are used instead of random identifiers, then data correlation accuracy improves, but processing and memory resources required are reduced
Solution Approach 1:
The structured session identifiers are designed to be self-descriptive, containing embedded resource identifiers and change request information that enable systems to correlate data without requiring extensive external processing or lookup operations. The identifiers essentially service their own correlation needs, reducing the computational energy required for data matching and analysis compared to random identifiers that would require additional indexing and searching infrastructure.
Data Source
AI summary
Systems and techniques are disclosed for generating a session identifier to be used when implementing changes in a complex system that facilitates identification and retrieval of data indicating the scope and impact of the changes. An execution identifier for a set of operations and a service identifier for a service performing the operations may be used as a basis for the session identifier. The session identifier may be provided to computing resources on which operations are performed and logged by the computing resources along with the results of the operations. This activity data associated with the particular set of operations can be retrieved using the session identifier to determine the scope and impact of the operations on the system.