Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 158.1
edited by Carlijn Kokkeler
on 2023/10/10 14:19
Change comment: There is no comment for this version
To version 327.1
edited by Carlijn Kokkeler
on 2024/01/02 10:21
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,62 +1,70 @@
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!** 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.
6 6  
7 -== **Deployment Plan** ==
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 8  
9 -//__Improved deployment plan to make the process better and more predictable__//
10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by a container.
11 11  
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
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.
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
18 +== **Overviews** ==
17 17  
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
20 -
21 -//__Cleanup old images__//
22 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
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.
23 23  
24 -== **Store Improvements** ==
25 -
23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
26 26  
27 -== **Feedback Items** ==
25 +//__Missing properties overview__//
26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
28 28  
29 -//__Alerting manual pause__//
30 -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.
28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
31 31  
32 -//__Ordering of graphs in Manage__//
33 -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).
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.
34 34  
35 -//__UTC times in Grafana panels__//
36 -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.
33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
37 37  
38 -//__Update flow designer version__//
39 -The framework used in the flow designer has been updated to the latest version.
35 +== **Feedback Items** ==
40 40  
41 -//__Carwash track TLS versions in logging__//
42 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
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'.
43 43  
44 -//__Moving channels in the flow designer__//
45 -Moving already attached channels in the flow designer has been made sligthly easier.
40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
46 46  
47 -//__Topic sizes description change__//
48 -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.
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.
49 49  
50 -//__Topic sizes description change__//
51 -
45 +//__Broker queue metrics dashboards__//
46 +It is now possible to select the MQTT broker in the queue metrics dashboards.
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.
50 +
51 +
52 52  == **Bug Fixes** ==
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.
54 54  
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.
59 +
60 +//__Next generation block__//
61 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 +
55 55  == **Fancy Forum Answers** ==
56 56  
57 57  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:
58 58  
59 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
60 60  
61 61  == **Key takeaways** ==
62 62  
... ... @@ -78,5 +78,11 @@
78 78  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
79 79  
80 80  ~*~* Indicates a next-generation-architecture only feature.
81 -{{/info}})))((({{toc/}}))){{/container}}
89 +{{/info}}
90 +)))
91 +
92 +(((
93 +{{toc/}}
94 +)))
82 82  {{/container}}
96 +{{/container}}