Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 684.1
edited by Carlijn Kokkeler
on 2024/08/26 13:35
on 2024/08/26 13:35
Change comment:
There is no comment for this version
To version 636.1
edited by Carlijn Kokkeler
on 2024/07/29 13:15
on 2024/07/29 13:15
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -22 8-MonitoringMania1 +226 - Alerting Alchemy - Content
-
... ... @@ -3,75 +3,56 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** This release6 +**Hi there, eMagiz developers!** In this release, 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. 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. 15 15 16 -[[im age:Main.Images.ReleaseBlog.WebHome@release-228-eventsteamingstats.png]]19 +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. 17 17 18 -* The Memory and CPU usage table in the Runtime statistics displays the maximum value in a given time period that is selected. 19 -* Pressing the 'show main dashboard' button returns back to the unfiltered master dashboard. 20 -* For detailed views the 'show main dashboard' button is on the left. 21 -* Graphs on a page share the same crosshair. 22 -* The styling on HTTP statistics when there are no (un)successful requests within a timeframe has been improved. 23 -* For selection dropdowns the selected variables are locked to the top for easy deselection. 21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-228-runtime statistics.png]] 26 -[[image:Main.Images.Release Blog.WebHome@release-228-maindashboard.png]] 23 +{{info}}Please check out our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] for an elaborate explanation of our new alerting design. {{/info}} 27 27 28 -//__Failover deployment plan__// 29 -The deployment plan steps with type 'Failover' is now deprecated, meaning they can no longer be added to a deployment plan. 25 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 30 30 31 -//__ Editmode flowtesting__//32 -Te st messagescanwbe editedor removedwhileineedit modeoftheflow testingfunctionality.27 +//__Tenant technical name__// 28 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 33 33 34 -//__Missing properties overview__// 35 -Setting the value of a missing property will now automatically remove it from the missing properties overview. Besides that, search and sort functionality have been added to the missing properties overview. 36 -[[image:Main.Images.Release Blog.WebHome@release-228-missing-properties.png]] 30 +//__Tenant transfer__// 31 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 37 37 38 -//__ Legacyreleasenotes__//39 - The legacy releasenotes tabhasbeen removed.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. 40 40 41 -//__SSL helptext__// 42 -The SSL section in runtime settings has more elaborate helptext. 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. 43 43 44 -[[image:Main.Images.Release Blog.WebHome@release-228-ssl-enabled.png]] 45 - 46 -//__Memory warning__// 47 -A pop-up with a warning will be shown when containers are configured with less memory than recommended. 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 48 49 -[[image:Main.Images.Release Blog.WebHome@release-228-memory-settings.png]] 50 - 51 -//__Reuse test messages__// 52 -It is now possible to reuse the test messages from the onramp in the routing and vice versa in flow testing 53 - 54 -== **Bug Fixes** == 55 -//__Legacy properties__// 56 -We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. 57 - 58 -//__Exceeding memory__// 59 -We fixed a bug where new machines could be deployed with exceeding memory. 60 - 61 -//__Copy paste__// 62 -The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. 63 - 64 -//__Unused properties__// 65 -We added logging for when properties are deleted from the unused properties screen. 66 - 67 -[[image:Main.Images.Release Blog.WebHome@release-228-unused-properties.png]] 68 - 69 69 == **Fancy Forum Answers** == 70 70 71 71 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: 72 72 73 -* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]] 74 -* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]] 53 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 54 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 55 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 75 75 76 76 == **Key Takeaways** == 77 77 ... ... @@ -81,7 +81,7 @@ 81 81 * If you have feedback or ideas for us, talk to the Platypus 82 82 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 83 83 * Clear your browser cache (Ctrl + Shift + Del) 84 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 7-FixFrenzy.WebHome||target="blank"]]65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]] 85 85 * Start thinking about how the license tracker can aid your development 86 86 * Start thinking about major, minor, and patch 87 87 * Keep making great integrations