An Environment is a combination of your assembly (base design) with operational attributes to match the associated business requirements, such as a new dev, qa, or prod Environments.
Environment name that is unique to the Assembly
Configuration section is used to configure the Environment with an option to edit the Environment.
A notification relay allows notification filtering and routing configuration for a given Environment. All notification for a given Environment will be matched against existing Environment relays for filtering based on source, severity, subject/text and ns path to specified list destination addresses.
There is a default relay available to all Environments, which route alerts to assembly owner. Users have the privilege to delete default relay.
We can see the release history timeline which deployment are in effect and which are still open. The release activities can be
- Closed: Displays the releases deployed on the Environment
- Open: Displays the open releases
- Cancelled: Deployment is cancelled inbetween
Change Management made easier with LiveCompare. Comparing two running Environments side by side to see how your production system is affected by upcoming changes from development or test or pre-prod Environments.
Optimize your cloud spend by knowing your entire application cost “live” across multiple Environments separated by applications in different cloud accounts using LiveCosting.
Clicking this will toggle between configure and operate mode.