Changes for page 240 - Spring Cleaning
Last modified by Erik Bakker on 2025/03/10 10:00
From version 680.1
edited by Carlijn Kokkeler
on 2024/08/26 13:09
on 2024/08/26 13:09
Change comment:
There is no comment for this version
To version 646.1
edited by Carlijn Kokkeler
on 2024/07/30 13:32
on 2024/07/30 13:32
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,51 +3,56 @@ 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. 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 -[[image:Main.Images.Release Blog.WebHome@release-22 8-eventsteamingstats.png]]19 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 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. 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]] 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}} 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. 24 +eMagiz will migrate your dynamic queue alerts on the **release day** when you are **fully** or **partially** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. When doing so, we will configure the new queue alert in a similar fashion to best match its current behaviour. Note that the queue alerting will only function for models that are **fully** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. Should you want to change or create new queue alerts, you can do so starting the day **after** the release to avoid conflicts with our migration. 30 30 31 -//__Edit mode flow testing__// 32 -Test messages can now be edited or removed while in the edit mode of the flow testing functionality. 26 +{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}} 33 33 34 -//__Edit mode flow testing__// 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]] 28 +//__Tenant technical name__// 29 +The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 37 37 38 - 39 -== **Bug Fixes** == 40 -//__Legacy properties__// 41 -We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. 31 +//__Tenant transfer__// 32 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 42 42 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. 43 43 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. 44 44 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 + 45 45 == **Fancy Forum Answers** == 46 46 47 47 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: 48 48 49 -* [[ Messages arenotbeing deliveredcorrectlyto theSFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]]50 -* [[ UploadingXSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]]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"]] 51 51 52 52 == **Key Takeaways** == 53 53 ... ... @@ -57,7 +57,7 @@ 57 57 * If you have feedback or ideas for us, talk to the Platypus 58 58 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 59 59 * Clear your browser cache (Ctrl + Shift + Del) 60 -* 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.226 - Alerting Alchemy.WebHome||target="blank"]] 61 61 * Start thinking about how the license tracker can aid your development 62 62 * Start thinking about major, minor, and patch 63 63 * Keep making great integrations