Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 160.1
edited by Carlijn Kokkeler
on 2023/10/11 09:25
Change comment: There is no comment for this version
To version 92.1
edited by Erik Bakker
on 2023/03/14 08:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +194 - Big Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,81 +2,73 @@
2 2  {{container layoutStyle="columns"}}(((
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.
5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
6 6  
7 -== **Deployment Plan** ==
7 +== **3rd generation improvements** ==
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.
9 +//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
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.
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
17 17  
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
20 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.
21 +//__Improved process of deploy preparation__//
22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
23 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.
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
26 26  
27 -== **Store Improvements** ==
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
28 28  
29 -//__Message definition elements order__//
30 -We fixed an issue that the orders of message definition’s elements were changed after imported.
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
31 31  
32 -== **Feedback Items** ==
33 +//__Improved help text for network volumes__//
34 +With this release we have improved the help text that explains network volumes and how to use them within our solution.
33 33  
34 -//__Alerting manual pause__//
35 -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.
36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
36 36  
37 -//__Ordering of graphs in Manage__//
38 -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).
38 +== **Feedback items ** ==
39 39  
40 -//__UTC times in Grafana panels__//
41 -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.
40 +//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 +With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
42 42  
43 -//__Update flow designer version__//
44 -The framework used in the flow designer has been updated to the latest version.
43 +//__User Roles are sorted alphabetically__//
44 +All user roles under User Management are now also sorted alphabetically.
45 45  
46 -//__Carwash track TLS versions in logging__//
47 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
46 +//__Name of keystore for user management now includes the environment__//
47 +To improve the naming of downloaded keystore that need to be distributed to external parties we have added the name of the environment to the filename. This way you can make a distinction between the various environments by looking at the filename.
48 48  
49 -//__Moving channels in the flow designer__//
50 -Moving already attached channels in the flow designer has been made sligthly easier.
49 +== **Bug fixes ** ==
51 51  
52 -//__Topic sizes description change__//
53 -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.
51 +//__Consolidated upgrade process cloud template__//
52 +With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was actually happening in the cloud.
54 54  
55 -//__Password change notification__//
56 -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.
54 +//__Ensure users can deploy release on environments they have edit rights on__//
55 +As of now users with only limited rights in Deploy, for example, only edit rights in Test can now activate and deploy releases that are ready for other environments but need to be deployed on the environment for which they have the rights to do so.
57 57  
58 -//__Password comparison__//
59 -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.
60 -
61 -
62 -== **Bug Fixes** ==
63 -
64 -//__Flow designer styling__//
65 -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.
66 -
67 67  == **Fancy Forum Answers** ==
68 68  
69 69  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:
70 70  
71 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
61 +* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
62 +* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
63 +* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
72 72  
73 73  == **Key takeaways** ==
74 74  
75 -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:
67 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
76 76  
77 77  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 78  * If you have feedback or ideas for us, talk to the Platypus
79 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
71 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 80  * Clear your browser cache (Ctrl + Shift + Del)
81 81  * Check out the release notes [here]
82 82  * Start thinking about how the license tracker can aid your development
... ... @@ -89,6 +89,6 @@
89 89  {{info}}
90 90  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 91  
92 -~*~* Indicates a next-generation-architecture only feature.
84 +~*~* Indicates a GEN3-only feature.
93 93  {{/info}})))((({{toc/}}))){{/container}}
94 94  {{/container}}