Skip to Content

Changes for page 236 - Another Agent

Last modified by Erik Bakker on 2025/01/13 09:32
From version 174.1
edited by Carlijn Kokkeler
on 2023/12/21 16:18
Change comment: There is no comment for this version
To version 11.1
edited by Erik Bakker
on 2022/10/24 11:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +186 - Daemon Switch
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,31 +1,25 @@
1 -In the last sprint cycle, we focused on improving several aspects related overviews and logging. It is now possible to see an overview of all runtimes on running machines, see runtimes and flow versions in the missing properties overview, and see which runtimes will be restarted or redeployed in a pop-up displayed when starting the deployment plan. Moreover, crash handling has been improved, as well as runtime logging and the display of the deployment execution error message. Lastly, several other minor changes and bug fixes have been done, mainly relating to the Deploy and Manage phase.
1 +Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities.
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.211 - Log Luminary||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.186 - Daemon Switch.WebHome||target="blank"]].
4 4  
5 5  =====New features=====
6 +* Deploy - User Management: Before and after applying to environment, keep track of user management changes. Export history as an excel file.
6 6  
7 -* Deploy - Runtime overview: We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
8 -* Deploy - Deployment plan: Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
9 -
10 -
11 -
12 -
13 -
14 14  =====Minor changes=====
15 15  
16 -* Deploy - Deployment: The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
17 -* Deploy - Architecture: Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
18 -* Manage - Monitoring: We improved crash handling so that log messages clearly show when and why a container failed to start.
10 +* Design System. Changed the look and feel across the portal altogether. Changes can be seen in:
11 + ** Datagids, where there is now on hover action for example.
12 + ** Pop ups
13 + ** Context menus, also have on hover action
14 + ** Styling of scrollbars
15 + ** Warning, info and error context labels.
16 +* Message Redelivery - admin logs improved to better analyze issues when they occur
17 +* Message Redelivery - improved feedback to the user when something goes wrong within the Message redelivery functionality
18 +* Create - Flow Designer: small bugs (copy/paste by keyboard, copy annotation, display interceptors and queue channels) are fixed
19 19  
20 -
21 -
22 -
23 -
24 24  ====Bug fixes====
25 -
26 -* Deploy - Deployment plan: We fixed an issue where an error was given when trying to display an error message regarding deployment plan execution errors. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history.
27 -* Manage - Monitoring: We fixed a bug where no new log messages were showing up, even though they were produced by the container.
28 -
29 -
30 -
31 -
21 +* Deploy - Deployment plan. Performance of page to deploy a release increased significantly
22 +* Store - Import resources was incorrectly done in specific cases, which is now fixed
23 +* Store - Target namespace will be imported when importing an XML Message Definition
24 +* Store - When exporting components, if property values contains model name, they will be updated automatically with new model name when importing into a new model.
25 +* Store - Importing items from the store sometimes resulted in invalid JMS connection factories.