Changes for page 226 - Alerting Alchemy

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

From 370.1 to 371.1 From 646.1 to 647.1

From version 371.1

edited by CarlijnKokkeler
on 2024/01/31 12:09

Change comment: There is no comment for this version

To version 646.1

edited by CarlijnKokkeler
on 2024/07/30 13:32

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--213 - Joyful Journeys
++226 - Alerting Alchemy

Content

@@ -3,78 +3,56 @@
  (((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**Hi there, eMagiz developers!** In this release, several improvements for pop-ups have been made so that more user friendly messages are shown that reflect actual behaviour. Moreover, formatting and alignment improvements have been made to improve the user journey. Lastly, we have worked on some more feedback items and several more bug fixes have been done.
++**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!
--== **Pop-up Improvements** ==
++== **Feedback Items** ==
++//__Queue alerting__//
++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:
++* New UI that shows all queues and the alerting that is active on them.
++* Every queue in the model will be automatically added to the list of queues in Manage - Alerting.
++* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release.
++* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert.
++** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour.
++* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance.
++* 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.
--//__Property releases__//
--When a new property release is created, this property release can now not only be viewed but also release properties can be deleted.
++[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
--[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
--//__Runtime deletion__//
--When deleting a runtime, the error message is more descriptive. The error message will now include the names of the flows that run on the container.
++{{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}}
--//__Wiretap & debug error messages__//
--The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
++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.
--//__Action messages__//
--The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
++{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
--== **Formatting & Alignments** ==
++//__Tenant technical name__//
++The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
--//__Input fields__//
--Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
++//__Tenant transfer__//
++A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
--//__UI improvements__//
--UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
++//__Property placeholder__//
++A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
--//__Component changes reversion__//
--In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
++//__Machine pop-up__//
++* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
++* The machine health indicator has been improved visually.
++* Several progress bars have been improved visually.
--//__State generation statistics__//
--The state generation graphs will now show the correct number of cache hits and misses.
++[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
++
++//__Infinispan Cache Manager__//
++The Infinispan Cache Manager has been updated to:
++* Provide an additional 'transport type' to offer more means for creating a clustered setup;
++* Provide clearer helptexts explaining which of the options is needed and what its effect is;
++* Include validation on fields depending on the selected 'transport type'.
--//__Queue browser timestamps__//
--All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd  HH:mm:ss.SSS.
--
--//__Addition and deletion of internal recipients__//
--Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
--
--== **Feedback Items** ==
--
--//__Update flows__//
--In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used. This is particularly useful when changing a resouce used across multiple flows such as topic message definitions in event processors.
--
--//__Q&A forum search__//
--The option to search by pressing the Enter key has been added to the Q&A forum.
--
--//__Memory settings__//
--It is now possible to change the memory settings of a newly added container before pressing "Apply to environment".
--//__Runtime validation__//
--Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
--
--//__Runtime overview image versions__//
--Insight into intended and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
--
--== **Bug Fixes** ==
--
--//__Removal of onramp__//
--We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
--
--//__Runtime statistics details__//
--We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
--
--//__Deployment prechecks__//
--During deployments, prechecks can be executed on runtimes level for runtimes that still have to be deployed. These prechecks can be executed via Deploy > Architecture.
--
  == **Fancy Forum Answers** ==
  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:
--* [[Changing filename based on attribute>>https://my.emagiz.com/p/question/172825635703696968||target="blank"]]
--* [[Payload must be an instance of a Map>>https://my.emagiz.com/p/question/172825635703709401||target="blank"]]
--* [[Promoting a system to a split gateway>>https://my.emagiz.com/p/question/172825635703722185||target="blank"]]
++* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
++* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
  == **Key Takeaways** ==
@@ -84,7 +84,7 @@
  * If you have feedback or ideas for us, talk to the Platypus
  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
--* Check out the release notes [here]
++* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
  * Start thinking about how the license tracker can aid your development
  * Start thinking about major, minor, and patch
  * Keep making great integrations

Changes for page 226 - Alerting Alchemy

Summary

Details

Navigation