Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 335.1
edited by Carlijn Kokkeler
on 2024/01/15 14:14
Change comment: There is no comment for this version
To version 158.1
edited by Carlijn Kokkeler
on 2023/10/10 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -212 - Failover Fiesta
1 +206 - Situational Deployment
Content
... ... @@ -1,43 +1,62 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release...
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.
7 7  
8 -== **Feedback Items** ==
7 +== **Deployment Plan** ==
9 9  
10 -//__Failover setup__//
11 -New components have been created to support a failover setup. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.1.0/||target="blank"]]
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 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
14 14  
15 -//__External recipients emailaddress__//
16 -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.
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
17 17  
18 -//__Broker queue metrics dashboards__//
19 -It is now possible to select the MQTT broker in the queue metrics dashboards.
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 20  
21 -//__Runtime image version__//
22 -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.
24 +== **Store Improvements** ==
25 +
23 23  
27 +== **Feedback Items** ==
24 24  
25 -== **Bug Fixes** ==
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.
26 26  
27 -//__Message throughput__//
28 -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.
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).
29 29  
30 -//__Cloud template upgrade incorrect rollback__//
31 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
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.
32 32  
33 -//__Next generation block__//
34 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
38 +//__Update flow designer version__//
39 +The framework used in the flow designer has been updated to the latest version.
35 35  
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.
43 +
44 +//__Moving channels in the flow designer__//
45 +Moving already attached channels in the flow designer has been made sligthly easier.
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.
49 +
50 +//__Topic sizes description change__//
51 +
52 +== **Bug Fixes** ==
53 +
54 +
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
41 41  
42 42  == **Key takeaways** ==
43 43  
... ... @@ -50,6 +50,7 @@
50 50  * Check out the release notes [here]
51 51  * Start thinking about how the license tracker can aid your development
52 52  * Start thinking about major, minor, and patch
72 +* Upgrade to the latest build number
53 53  * Keep making great integrations
54 54  
55 55  Let's stay in touch and till next time!
... ... @@ -57,11 +57,6 @@
57 57  {{info}}
58 58  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
59 59  
60 -{{/info}}
61 -)))
62 -
63 -(((
64 -{{toc/}}
65 -)))
80 +~*~* Indicates a next-generation-architecture only feature.
81 +{{/info}})))((({{toc/}}))){{/container}}
66 66  {{/container}}
67 -{{/container}}