Skip to Content

Changes for page 201 - Be Informed

Last modified by Carlijn Kokkeler on 2024/04/18 13:13
From version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version
To version 124.1
edited by Erik Bakker
on 2023/06/19 14:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +200 - Uncharted Territories
Content
... ... @@ -2,44 +2,52 @@
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 worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on a lot of things that are unfortanetly not quite ready to be released. As a result the ouput of this release is limited. Having said that we still bring some key improvements in the Deploy and Manage phase that would make life much easier.
6 6  
7 7  == **Next generation improvements and bug fixes** ==
8 8  
9 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
9 +//__Enhanced right-hand view within Deployment Plan context__//
10 +When executing your deployment plan we will show specific log entries of the info category that indicate that a container (i.e. runtime) has started up correctly. On top of that we show the warnings and errors in this overview.
11 11  
12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
12 +{{info}}Note that when the JMS container gets restarted connection errors in the logs are a normal thing to witness so keep your eyes peeled for the startup logging on JMS level to gain confidence in the deployment.{{/info}}
14 14  
14 +//__Improved timeout settings when deploying__//
15 +To avoid mismatches between various parts of the infrastructure we have improved the timeout configuration on certain deployment plan steps to reduce the chance that these mismatches occur.
16 +
17 +{{info}}Note that this fix is part of a new runtime image for the current-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
18 +
19 +//__Detailed HTTP Statistics now show user info in specific additional cases__//
20 +To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.
21 +
15 15  {{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
16 16  
17 -//__Forced congestion control__//
18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
24 +//__Improved loading speed of Manage Dashboard__//
25 +This release improves the loading speed with which all the dashboards in Manage are shown to the user. This will enhance the user experience within the Manage phase.
19 19  
27 +== **Store Improvements** ==
20 20  
21 -//__Improved validation errors on the invalid configuration of HTTP outbound components__//
22 -This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
29 +//__Importing in Design is improved__//
30 +We have solved a bug that could cause issues when importing something in Design while the accompanying integration was not yet in Create.
23 23  
24 -//__Improved migration behavior__//
25 -This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are:
26 -A smoother migration of your JMS (and backup JMS) process.
27 -Shortening of names that otherwise would be too long, additional feedback given to the user.
28 -Feedback when the migration process is finished.
32 +== **Bug Fixes** ==
29 29  
30 -//__Additional checks when deploying__//
31 -This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other.
34 +//__Deprecated reminder pop-up removed__//
35 +We have removed a reminder pop-up on a pending cloud template as it was deprecated and could cause issues when using it in communication with other systems.
32 32  
33 -== **Store Improvements** ==
37 +//__Improved selection area in Flow Designer__//
38 +When working on a large flow you can now select specific areas easily while you are scrolled down furhter down the flow.
34 34  
35 -== **Event Streaming - Certificate Management** ==
40 +//__Improved Kafka settings_//
41 +For all flows that use a Kafka related component within the flow designer we will run a migration to update every single one of them to the new best practices and create a new flow version for them.
36 36  
43 +{{info}}We stronly encourage all users that use these components to update to these new best practices as they increase stability of the cluster and throughput of the solution{{/info}}
44 +
37 37  == **Fancy Forum Answers** ==
38 38  
39 39  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:
40 40  
41 -* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]]
42 -* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]]
49 +* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
50 +* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
43 43  
44 44  == **Key takeaways** ==
45 45