Skip to Content

Changes for page 203 - Fast Paced

Last modified by Carlijn Kokkeler on 2024/04/18 13:12
From version 116.1
edited by Erik Bakker
on 2023/05/10 08:46
Change comment: There is no comment for this version
To version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -197 - Pay Attention
1 +199 - Home Improvements
Content
... ... @@ -2,59 +2,44 @@
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 our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
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.
6 6  
7 -== **Event streaming alerting** ==
7 +== **Next generation improvements and bug fixes** ==
8 8  
9 -This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
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.
10 10  
11 -The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
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 12  
13 -The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
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}}
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
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.
16 16  
17 -The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
20 -
21 -The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
22 -
23 -For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
24 -
25 -== **3rd generation improvements** ==
26 -
27 -//__Increased grace period for shutdown__//
28 -In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
29 -
30 -//__Update at once or not__//
21 +//__Improved validation errors on the invalid configuration of HTTP outbound components__//
31 31  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.
32 32  
33 -//__Improved user feedback while executing a deployment plan__//
34 -This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
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.
35 35  
36 -//__Improved auto-healing when running in a hybrid situation__//
37 -In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
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.
38 38  
39 -//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40 -To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
33 +== **Store Improvements** ==
41 41  
42 -{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
35 +== **Event Streaming - Certificate Management** ==
43 43  
44 -== **Feedback items ** ==
45 -
46 -//__Make sure the message format can be viewed without "Start editing"__//
47 -With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
48 -
49 -//__Various styling improvements in the flow testing functionality__//
50 -Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
51 -
52 52  == **Fancy Forum Answers** ==
53 53  
54 54  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:
55 55  
56 -* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
57 -* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
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"]]
58 58  
59 59  == **Key takeaways** ==
60 60