Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 675.1
edited by Carlijn Kokkeler
on 2024/08/26 12:16
Change comment: There is no comment for this version
To version 643.1
edited by Carlijn Kokkeler
on 2024/07/30 13:10
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -228 - TBD
1 +226 - Alerting Alchemy
Content
... ... @@ -3,39 +3,55 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release
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 7  
8 8  == **Feedback Items** ==
9 -//__Grafana improvements__//
10 -* The throughput now shows the unit of measurement in the queue statistics.
11 -* The units of measurement have been improved in the following graphs:
12 -** Runtime detail: Log events are counted as a sum instead of a maximum per data point. Data measurements show if a runtime is on or off.
13 -** Queue detail: Data measurements show if a queue is on or off.
14 -** Event streaming: The Bytes in and out are not a rate per seconds but dynamic based on the time frame selected. The messages in are counted not based on per second but also dynamic based on the time frame selected.
15 -* The Memory and CPU usage table in the runtime statistics displays the maximum value in a given time period that is selected.
16 -* Pressing the 'show main dashboard' button returns back to the unfiltered master dashboard.
17 -* For detailed views the 'show main dashboard' button is on the left.
18 -* Graphs on a page share the same crosshair.
19 -* The styling on HTTP statistics when there are no (un)successful requests within a timeframe has been improved.
20 -* For selection dropdowns the selected variables are locked to the top for easy deselection.
21 -
22 -[Manage-Monitoring] Improved the units of measurement in the following graphs:
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 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
23 23  
21 +{{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}}
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@release-227-errorchannel-stacktrace.png]]
23 +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.
26 26  
25 +{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
27 27  
28 -
29 -== **Bug Fixes** ==
30 -//__Legacy properties__//
31 -We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production.
27 +//__Tenant technical name__//
28 +The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
32 32  
30 +//__Tenant transfer__//
31 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
32 +
33 +//__Property placeholder__//
34 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
35 +
36 +//__Machine pop-up__//
37 +* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
38 +* The machine health indicator has been improved visually.
39 +* Several progress bars have been improved visually.
40 +
41 +[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
42 +
43 +//__Infinispan Cache Manager__//
44 +The Infinispan Cache Manager has been updated to:
45 +* Provide an additional 'transport type' to offer more means for creating a clustered setup;
46 +* Provide clearer helptexts explaining which of the options is needed and what its effect is;
47 +* Include validation on fields depending on the selected 'transport type'.
48 +
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 -* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]]
38 -* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]]
53 +* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
54 +* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
39 39  
40 40  == **Key Takeaways** ==
41 41  
... ... @@ -45,7 +45,7 @@
45 45  * If you have feedback or ideas for us, talk to the Platypus
46 46  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
47 47  * Clear your browser cache (Ctrl + Shift + Del)
48 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]]
64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
49 49  * Start thinking about how the license tracker can aid your development
50 50  * Start thinking about major, minor, and patch
51 51  * Keep making great integrations