Changes for page 206 - Situational Deployment
                  Last modified by Carlijn Kokkeler on 2024/05/22 13:38
              
      
      From version  124.1 
    
    
              edited by Carlijn Kokkeler
        
on 2023/10/12 12:27
     on 2023/10/12 12:27
      Change comment:
              There is no comment for this version
          
         
      To version  123.1 
    
    
              edited by Carlijn Kokkeler
        
on 2023/10/12 12:26
     on 2023/10/12 12:26
      Change comment:
              There is no comment for this version
          
         Summary
- 
          Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
- 
      - Content
-   ... ... @@ -17,7 +17,7 @@ 17 17 * Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well. 18 18 * Deploy - Release: Performance improvements have been implemented for loading releases in Deploy. 19 19 * Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024) 20 -* Manage - Alerting: Inactivated users should be removed from all alert settings (includ ing“disabled“ settings) to avoid undesirable notifications.20 +* Manage - Alerting: Inactivated users should be removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 21 21 * Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069) 22 22 * Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070) 23 23 * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063) 
 
