Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40

From version 645.1
edited by CarlijnKokkeler
on 2024/07/30 13:10
Change comment: There is no comment for this version
To version 408.1
edited by CarlijnKokkeler
on 2024/02/28 09:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +215 - Tiny Tales
Content
... ... @@ -2,57 +2,39 @@
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 +
6 +**Hi there, eMagiz developers!** This release blog is small because we have been busy working on items that will be released later. For this release, the event streaming graph has been improved. Moreover, some bug fixes have been done. The validation for queue names with respect to spaces has been improved. Furthermore, it is now possible to remove an onramp that was previously linked to an all-entry. Lastly, it is now possible to log in to eMagiz by pressing enter when the username field is selected.
5 5  
6 -**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, as well as the Infinispan Cache Manager. Find out all below!
7 -
8 8  == **Feedback Items** ==
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.
9 +//__Improved event streaming graph__//
10 +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.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
12 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-topics-2.png]]
20 20  
14 +//__Flow versions auto deletion__//
15 +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.
21 21  
22 -{{info}}Please check out our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning for an elaborate explanation of our new queue alerting design. {{/info}}
17 +== **Bug Fixes** ==
18 +//__Queue name validation__//
19 +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.
23 23  
24 -If your 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.
21 +[[image:Main.Images.Release Blog.WebHome@release-215-tiny-tales-queue-name-validation.png]]
25 25  
26 -{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
23 +//__Removal of onramp__//
24 +An issue has been fixed where removing an onramp that was previously linked to a combined entry was impossible in the Create phase.
27 27  
28 -//__Tenant technical name__//
29 -The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
26 +//__eMagiz login__//
27 +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.
30 30  
31 -//__Tenant transfer__//
32 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
33 -
34 -//__Property placeholder__//
35 -A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
36 -
37 -//__Machine pop-up__//
38 -* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
39 -* The machine health indicator has been improved visually.
40 -* Several progress bars have been improved visually.
41 -
42 -[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
43 -
44 -//__Infinispan Cache Manager__//
45 -The Infinispan Cache Manager has been updated to:
46 -* Provide an additional 'transport type' to offer more means for creating a clustered setup;
47 -* Provide clearer helptexts explaining which of the options is needed and what its effect is;
48 -* Include validation on fields depending on the selected 'transport type'.
49 -
50 50  == **Fancy Forum Answers** ==
51 51  
52 52  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:
53 53  
54 -* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
55 -* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
33 +* [[eMagiz Mendix Kafka Module Issue (Mendix 10)>>https://my.emagiz.com/p/question/172825635703748180||target="blank"]]
34 +* [[SFTP + Privatekey not working>>https://my.emagiz.com/p/question/172825635703760538||target="blank"]]
35 +* [[Attribute name is not allowed to start with 'xml'>>https://my.emagiz.com/p/question/172825635703760662||target="blank"]]
36 +* [[How do I change the default content-type from ISO-8859-1 to utf-8>>https://my.emagiz.com/p/question/172825635703760803||target="blank"]]
37 +* [[Preparing Image for <runtime> failed>>https://my.emagiz.com/p/question/172825635703761022||target="blank"]]
56 56  
57 57  == **Key Takeaways** ==
58 58  
... ... @@ -62,7 +62,7 @@
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 63  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
47 +* Check out the release notes [here]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 68  * Keep making great integrations