Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 182.1
edited by Carlijn Kokkeler
on 2023/10/12 16:18
Change comment: There is no comment for this version
To version 319.1
edited by Carlijn Kokkeler
on 2023/12/21 14:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +211 - Log Luminary
Content
... ... @@ -1,112 +1,75 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Release Date Change** ==
8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
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.
9 9  
10 -== **Deployment Plan** ==
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
11 11  
12 -//__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is stopped last, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally, and all processes are stopped before being deployed again. This provides additional control over the deployment of your release(s) and reduces the likelihood of false-positive logging (and potentially alerting) during and shortly after the deployment.
15 +== **Overviews** ==
16 +//__Runtime overview__//
17 +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.
14 14  
15 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}}
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
16 16  
17 -//__Editing release properties__//
18 -With this release, it will be possible to change the description of a property by editing the property.
21 +//__Missing properties overview__//
22 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
19 19  
20 -//__Container memory settings__//
21 -A change in memory settings triggers redeployment of the container now.
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
22 22  
23 -//__Properties tab__//
24 -We have removed the deprecated tab Properties in the Deploy phase.
26 +//__Runtime restart or redeploy overview__//
27 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
25 25  
26 -//__Cleanup old images__//
27 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
29 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
28 28  
29 -//__Performance improvements for loading releases__//
30 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
31 31  
32 -== **Store Improvements** ==
33 -
34 -//__Message definition elements order__//
35 -We fixed an issue that the order of message definition elements was changed after being imported.
36 -
37 -//__Importing a store item with synchronous message definitions__//
38 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
39 -
40 -//__Importing store items containing static copies__//
41 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
42 -
43 -//__Importing store content__//
44 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
45 -
46 -//__Store disclaimer__//
47 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
48 -
49 49  == **Feedback Items** ==
50 50  
51 -//__Alerting manual pause__//
52 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
53 53  
54 -//__Ordering of graphs in Manage__//
55 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
35 +//__Breaking changes pop-up__//
36 +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'.
56 56  
57 -//__UTC times in Grafana panels__//
58 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
38 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
59 59  
60 -//__Update flow designer version__//
61 -The framework used in the flow designer has been updated to the latest version.
40 +//__External recipients emailaddress__//
41 +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.
62 62  
63 -//__Carwash track TLS versions in logging__//
64 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
43 +//__Broker queue metrics dashboards__//
44 +It is now possible to select the MQTT broker in the queue metrics dashboards.
65 65  
66 -//__Moving channels in the flow designer__//
67 -Moving already attached channels in the flow designer has been made sligthly easier.
46 +//__Runtime image version__//
47 +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.
68 68  
69 -//__Topic sizes description change__//
70 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
71 71  
72 -//__Password change notification__//
73 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
74 -
75 -//__Password comparison__//
76 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
77 -
78 -//__Inactive user alerting__//
79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
80 -
81 -//__Alphabetical sorting on user level in HTTP statistics__//
82 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
83 -
84 -//__SOAP Web services path__//
85 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
86 -
87 87  == **Bug Fixes** ==
88 88  
89 -//__Flow designer styling__//
90 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
52 +//__Message throughput__//
53 +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.
91 91  
92 -//__Partial search for messages__//
93 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
55 +//__Cloud template upgrade unjust rollback__//
56 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
94 94  
95 -//__Disk usage after cloud template update__//
96 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
58 +//__Next generation block__//
59 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
97 97  
98 -//__Error handling migration__//
99 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
61 +//__Deployment execution error message__//
62 +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.
100 100  
101 101  == **Fancy Forum Answers** ==
102 102  
103 103  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:
104 104  
105 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
106 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
107 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
108 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
109 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
68 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
69 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
70 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
71 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
72 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
110 110  
111 111  
112 112  == **Key takeaways** ==
... ... @@ -129,5 +129,11 @@
129 129  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
130 130  
131 131  ~*~* Indicates a next-generation-architecture only feature.
132 -{{/info}})))((({{toc/}}))){{/container}}
95 +{{/info}}
96 +)))
97 +
98 +(((
99 +{{toc/}}
100 +)))
133 133  {{/container}}
102 +{{/container}}