Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 322.1
edited by Carlijn Kokkeler
on 2023/12/21 15:09
Change comment: There is no comment for this version
To version 286.1
edited by Carlijn Kokkeler
on 2023/12/04 15:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +210 - Deployment Delights
Content
... ... @@ -3,62 +3,45 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes.
6 +**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 -== **Logging** ==
9 -//__Missing log entries__//
10 -We improved crash handling so that log messages clearly show when and why a container failed to start.
8 +== **Alerts** ==
11 11  
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by the container.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
14 14  
15 -//__Deployment execution error message__//
16 -In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
17 17  
18 -== **Overviews** ==
19 -
20 -//__Runtime overview__//
21 -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.
22 -
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
24 -
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
27 -
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
29 -
30 -//__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
32 -
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
34 -
35 35  == **Feedback Items** ==
36 36  
37 -//__Breaking changes pop-up__//
38 -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 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
41 41  
42 -//__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
44 44  
45 -//__Broker queue metrics dashboards__//
46 -It is now possible to select the MQTT broker in the queue metrics dashboards.
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
47 47  
48 -//__Runtime image version__//
49 -The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
29 +== **Bug Fixes** ==
50 50  
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
51 51  
52 -== **Bug Fixes** ==
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
53 53  
54 -//__Message throughput__//
55 -The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
37 +//__View all store items__//
38 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
56 56  
57 -//__Cloud template upgrade unjust rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
40 +//__Out of memory behavior__//
41 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
59 59  
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
43 +//__Max fetch size__//
44 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
62 62  
63 63  == **Fancy Forum Answers** ==
64 64