Skip to Content

Changes for page 224 - Summer Sonata

Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 425.1
edited by Carlijn Kokkeler
on 2024/03/25 14:45
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 -217 - Template Tango
1 +211 - Log Luminary
Content
... ... @@ -3,50 +3,70 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, new cloud templates for docker single and docker double lane are introduced. These templates enable the ability to clean H2 databases from the portal. Next to this, it is now possible to edit the trigger "More than 100 messages on queue over 10 minutes". Moroever, serveral copy to clipboard buttons have been added. Lastly, the runtime overview has been improved with respect to checks on the runtime version.
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 -== **Cloud Template R12 Docker - Single Lane** ==
9 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R12 Docker - Single Lane.WebHome||target="blank"]].
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.
10 10  
11 -== **Cloud Template R14 Docker - Double Lane** ==
12 -This release introduces a new non-service affecting cloud template for all our customers running in a single-lane setup. This cloud template introduces the ability to clean H2 databases from the portal. The complete release notes on the cloud template can be found [[here>>doc:Main.Release Information.Cloud Templates.R14 Docker - Double Lane.WebHome||target="blank"]].
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  
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.
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.
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 +
14 14  == **Feedback Items** ==
15 -//__Dynamic trigger__//
16 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
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.
19 19  
20 -//__Copy to clipboard buttons__//
21 -Copy to clipboard buttons have been added to various pages:
40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
22 22  
23 - * Deploy agent pop-up
24 - * Create - Flow designer: Properties
25 - * Deploy - Property releases: Property details
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.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
45 +//__Broker queue metrics dashboards__//
46 +It is now possible to select the MQTT broker in the queue metrics dashboards.
28 28  
29 -//__Reset H2 database__//
30 -For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines. Please note the following:
31 -{{info}}
32 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
33 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
34 -* For on-premise runtimes, only a reset of the runtime is needed.{{\info}}
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.
35 35  
36 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
37 37  
38 38  == **Bug Fixes** ==
39 -//__Runtime overview improvements__//
40 -The runtime overview has been improved regarding checks on the runtime version.
41 41  
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.
56 +
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.
59 +
60 +//__Next generation block__//
61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 +
42 42  == **Fancy Forum Answers** ==
43 43  
44 44  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:
45 45  
46 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
47 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
48 48  
49 -== **Key Takeaways** ==
69 +== **Key takeaways** ==
50 50  
51 51  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:
52 52