Change Diagnostics: It Worked Yesterday, What’s Changed?
- by Shanthi Sivasubramaniam, Technical Director, Sustain Systems Limited
- November 16, 2009
The next time your system behaves differently, use Change Diagnostics to uncover and analyze what’s changed.
Change Diagnostics, which is part of Solution Manager Diagnostics, provides information about changes that were made to a system landscape and when these changes were made. It provides a change history and a comparison tool so you can compare the technical configurations between systems or time stamps. This helps you quickly identify what has changed in your system landscape from the moment a particular error starts occurring.
How many times have you logged on to a system that worked perfectly fine yesterday, but today the performance of the system is slow and the programs or processes are terminating with errors? Perhaps the program that you were executing is different today in terms of its function or interface, or perhaps an important program is no longer available. In a complex landscape, how do you quickly find out what changes have occurred over the last 24 hours or within a specific time frame? The answer is through Change Diagnostics, which is made up of two components: End-to-End Change Analysis and the Change Reporting application.
End-to-End Change Analysis helps you identify and analyze what changes have occurred in the systems across your landscape according to various change groups for a particular time frame. A related application is Change Reporting, which allows you to compare the technical configuration (e.g., changes to technical parameters between systems or between time stamps). This allows you to identify what has changed and revert to a previous value if necessary.
Would you like to see this full item?