Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 163.1
edited by Carlijn Kokkeler
on 2023/10/11 10:57
Change comment: There is no comment for this version
To version 290.1
edited by Carlijn Kokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +210 - Deployment Delights
Content
... ... @@ -1,92 +1,62 @@
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 invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
6 6  
7 -== **Deployment Plan** ==
8 +== **Alerts** ==
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.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
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.
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
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.
23 -
24 -//__Performance improvements for loading releases__//
25 -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.
26 -
27 -== **Store Improvements** ==
28 -
29 -//__Message definition elements order__//
30 -We fixed an issue that the order of message definition elements was changed after being imported.
31 -
32 -//__Improting a store item with synchronous message definitions__//
33 -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.
34 -
35 -//__Importing store items containing static copies__//
36 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
37 -
38 38  == **Feedback Items** ==
39 39  
40 -//__Alerting manual pause__//
41 -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.
18 +//__Improved release build process__//
19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
42 42  
43 -//__Ordering of graphs in Manage__//
44 -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).
21 +//__Container version overview__//
22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
45 45  
46 -//__UTC times in Grafana panels__//
47 -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.
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
48 48  
49 -//__Update flow designer version__//
50 -The framework used in the flow designer has been updated to the latest version.
26 +//_Improved deployment process_//
27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
51 51  
52 -//__Carwash track TLS versions in logging__//
53 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
29 +//__Rebuilding of images__//
30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
54 54  
55 -//__Moving channels in the flow designer__//
56 -Moving already attached channels in the flow designer has been made sligthly easier.
32 +== **Bug Fixes** ==
57 57  
58 -//__Topic sizes description change__//
59 -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.
34 +//__Runtime metrics processing__//
35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
60 60  
61 -//__Password change notification__//
62 -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.
37 +//__Deployment plan__//
38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
63 63  
64 -//__Password comparison__//
65 -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.
40 +//__View all store items__//
41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
66 66  
67 -//__Inactive user alerting__//
68 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
69 69  
70 -//__Alphabetical sorting on user level in HTTP statistics__//
71 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
46 +//__Max fetch size__//
47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
72 72  
73 -== **Bug Fixes** ==
74 -
75 -//__Flow designer styling__//
76 -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.
77 -
78 -//__Partial search for messages__//
79 -It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim".
80 -
81 -//__Disk usage after cloud template update__//
82 -Several accounts showed significantly more disk usage after the last cloud template update, this has been resolved.
83 -
84 84  == **Fancy Forum Answers** ==
85 85  
86 86  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:
87 87  
88 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
89 89  
59 +
90 90  == **Key takeaways** ==
91 91  
92 92  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:
... ... @@ -107,5 +107,11 @@
107 107  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
108 108  
109 109  ~*~* Indicates a next-generation-architecture only feature.
110 -{{/info}})))((({{toc/}}))){{/container}}
80 +{{/info}}
81 +)))
82 +
83 +(((
84 +{{toc/}}
85 +)))
111 111  {{/container}}
87 +{{/container}}