With today’s complex distributed systems, even a small change in system architecture or virtual asset behavior can have significant impacts. CTP provides you a number of ways to identify and respond to changes that impact your test environments as well as other key indicators that an asset might not be operating as expected.
CTP automatically monitors asset health and modifications so that it can alert you to issues that might require your attention. For example:
When CTP automatically detects such issues, it flags the environment including that asset (in environment indexes and lists), as well as the specific asset (in the environment diagram).
Alerts are also shown at the system level—for both systems and environments. The system will show the icon for the highest severity health problem identified in its environments. For example, if a system has three environments—one with no health problems, one with a warning, and one with an alert—the system will show the red alert icon.
The following icons are used to indicate asset health:
Icon | Meaning |
---|---|
An asset requires immediate attention (e.g., because you’re about to route traffic to a real component whose specified endpoint currently offline, provision a virtual asset or proxy to a Virtualize Server that is currently offline, execute a provisioning action that was recently deleted, etc.) | |
The asset should be reviewed (e.g., a virtual asset has recently changed or is out-of-sync with the real endpoint, a JDBC controller shows no recent activity). | |
A component with a real endpoint specified is currently available at the specified location. | |
None | No health problems detected. |
If you try to provision an environment with health problems, you will receive a warning message in the lower right-hand corner of the page:
For additional details, click the + button to expand that error message.