Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 17-TemplateTango1 +226 - Alerting Alchemy - Content
-
... ... @@ -3,42 +3,37 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** 6 +**Hi there, eMagiz developers!** In this release, 7 7 8 -== **Cloud Template R12 Docker - Single Lane** == 9 - 10 -== **Cloud Template R14 Docker - Double Lane** == 11 - 12 12 == **Feedback Items** == 13 -//__Improved event streaming graph__// 14 -The event streaming graph has been improved so that the offset difference of a topic is the sum of the offset differences of each partition in that topic. 9 +//__Queue alerting__// 10 +Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, which includes the following improvements: 11 +* New UI that shows all queues and the alerting that is active on them. 12 +* Every queue in the model will be automatically added to the list of queues in Manage - Alerting. 13 +* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release. 14 +* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert. 15 +** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour. 16 +* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance. 17 +* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert. 18 + 19 +If you model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished. 15 15 16 - [[image:Main.Images.ReleaseBlog.WebHome@release-215-tiny-tales-topics-2.png]]21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 17 17 18 -//__Flow versions auto deletion__// 19 -Previously, the latest ten versions of a flow were not always selectable for a release. This has been improved so that from now on, the latest ten committed versions of each flow are always available. 23 +//__Tenant technical name__// 24 + 25 +//__Tenant transfer__// 26 +//__Property placeholder__// 20 20 21 21 == **Bug Fixes** == 22 -//__Queue name validation__// 23 -The validation regarding undesired spaces for components that use a queue name has been improved. Specifically, users are now prevented from creating a queue name with a space in the queue name when editing this in the Create phase in the Flow Designer. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]] 26 - 27 -//__Removal of onramp__// 28 -An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase. 29 - 30 -//__eMagiz login__// 31 -In the login screen, users can now press "enter" to log in when the username field is selected. Previously, this was only the case for the password field. 32 - 33 33 == **Fancy Forum Answers** == 34 34 35 35 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: 36 36 37 -* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]] 38 -* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]] 39 -* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]] 40 -* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]] 41 -* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]] 34 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 35 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 36 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 42 42 43 43 == **Key Takeaways** == 44 44 ... ... @@ -48,7 +48,7 @@ 48 48 * If you have feedback or ideas for us, talk to the Platypus 49 49 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 50 * Clear your browser cache (Ctrl + Shift + Del) 51 -* Check out the release notes [here] 46 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]] 52 52 * Start thinking about how the license tracker can aid your development 53 53 * Start thinking about major, minor, and patch 54 54 * Keep making great integrations