Wiki source code of 197 - Pay Attention
Last modified by Carlijn Kokkeler on 2024/04/18 13:15
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| 2 | {{container layoutStyle="columns"}}((( | ||
| 3 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] | ||
| 4 | |||
| |
114.1 | 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. |
| |
1.1 | 6 | |
| |
111.1 | 7 | == **Event streaming alerting** == |
| |
97.1 | 8 | |
| |
114.1 | 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. |
| |
98.1 | 10 | |
| |
114.1 | 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. |
| |
101.1 | 12 | |
| |
114.1 | 13 | The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community. |
| |
102.1 | 14 | |
| |
111.1 | 15 | [[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]] |
| |
101.1 | 16 | |
| |
114.1 | 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. |
| |
56.1 | 18 | |
| |
115.1 | 19 | [[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]] |
| |
108.1 | 20 | |
| |
114.1 | 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. |
| |
111.1 | 22 | |
| |
114.1 | 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"]]. |
| |
111.1 | 24 | |
| |
95.1 | 25 | == **3rd generation improvements** == |
| |
58.1 | 26 | |
| |
113.1 | 27 | //__Increased grace period for shutdown__// |
| |
114.1 | 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. |
| |
87.1 | 29 | |
| |
113.1 | 30 | //__Update at once or not__// |
| |
114.1 | 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. |
| |
58.1 | 32 | |
| |
113.1 | 33 | //__Improved user feedback while executing a deployment plan__// |
| |
114.1 | 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. |
| |
58.1 | 35 | |
| |
113.1 | 36 | //__Improved auto-healing when running in a hybrid situation__// |
| |
114.1 | 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. |
| |
113.1 | 38 | |
| |
116.1 | 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. | ||
| 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}} | ||
| 43 | |||
| |
105.1 | 44 | == **Feedback items ** == |
| |
58.1 | 45 | |
| |
113.1 | 46 | //__Make sure the message format can be viewed without "Start editing"__// |
| |
114.1 | 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. |
| |
95.1 | 48 | |
| |
113.1 | 49 | //__Various styling improvements in the flow testing functionality__// |
| |
114.1 | 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. |
| |
84.1 | 51 | |
| |
1.1 | 52 | == **Fancy Forum Answers** == |
| 53 | |||
| |
30.1 | 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: |
| |
1.1 | 55 | |
| |
114.1 | 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"]] | ||
| |
1.1 | 58 | |
| |
119.1 | 59 | == **Key Takeaways** == |
| |
1.1 | 60 | |
| |
30.1 | 61 | 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: |
| |
1.1 | 62 | |
| |
30.1 | 63 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 64 | * If you have feedback or ideas for us, talk to the Platypus |
| 65 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. | ||
| 66 | * Clear your browser cache (Ctrl + Shift + Del) | ||
| |
120.1 | 67 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.197 - Pay Attention.WebHome||target="blank"]] |
| |
1.1 | 68 | * Start thinking about how the license tracker can aid your development |
| 69 | * Start thinking about major, minor, and patch | ||
| 70 | * Upgrade to the latest build number | ||
| 71 | * Keep making great integrations | ||
| 72 | |||
| 73 | Let's stay in touch and till next time! | ||
| 74 | |||
| 75 | {{info}} | ||
| |
30.1 | 76 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 77 | |
| 78 | ~*~* Indicates a GEN3-only feature. | ||
| 79 | {{/info}})))((({{toc/}}))){{/container}} | ||
| 80 | {{/container}} |