Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 360.1
edited by Carlijn Kokkeler
on 2024/01/29 14:41
Change comment: There is no comment for this version
To version 333.1
edited by Carlijn Kokkeler
on 2024/01/03 10:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -213 - Joyful Journeys
1 +211 - Log Luminary
Content
... ... @@ -3,79 +3,70 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release ....
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, mainly relating to the Deploy and Manage phase.
7 7  
8 -== **Pop-up Improvements** ==
9 -//__Property releases__//
10 -When a new property release is created, this property release can now be viewed and deleted.
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.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by a container.
13 13  
14 -//__Runtime deletion__//
15 -When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
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.
16 16  
17 -//__Wiretap & debug error messages__//
18 -The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
18 +== **Overviews** ==
19 19  
20 -//__Action messages__//
21 -The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
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.
22 22  
23 -== **User Journey** ==
24 -//__Update flows__//
25 -In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
26 26  
27 -//__Input fields__//
28 -Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
25 +//__Missing properties overview__//
26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
29 29  
30 -//__UI improvements__//
31 -UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
32 32  
33 -//__Q&A forum search__//
34 -The option to search by pressing the Enter key has been added to the Q&A forum.
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.
35 35  
33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
34 +
36 36  == **Feedback Items** ==
37 37  
38 -//__Memory settings__//
39 -It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
37 +//__Breaking changes pop-up__//
38 +The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
40 40  
41 -//__Runtime validation__//
42 -Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
43 43  
44 -//__Runtime overview image versions__//
45 -Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
42 +//__External recipients emailaddress__//
43 +The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
46 46  
47 -== **Bug Fixes** ==
45 +//__Broker queue metrics dashboards__//
46 +It is now possible to select the MQTT broker in the queue metrics dashboards.
48 48  
49 -//__Removal of onramp__//
50 -We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
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.
51 51  
52 -//__Component changes reversion__//
53 -In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
54 54  
55 -//__State generation statistics__//
56 -The state generation graphs will now show the correct number of cache hits and misses.
52 +== **Bug Fixes** ==
57 57  
58 -//__Runtime statistics details__//
59 -We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
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.
60 60  
61 -//__Queue browser timestamps__//
62 -All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
57 +//__Cloud template upgrade incorrect rollback__//
58 +An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
63 63  
64 -//__Deployment prechecks__//
65 -During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
60 +//__Next generation block__//
61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
66 66  
67 -//__Addition and deletion of internal recipients__//
68 -Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
69 -
70 70  == **Fancy Forum Answers** ==
71 71  
72 72  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
73 73  
74 -* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
75 -* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
76 -* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||target="blank"]]
67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
77 77  
78 -== **Key Takeaways** ==
69 +== **Key takeaways** ==
79 79  
80 80  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
81 81