Changes for page 226 - Alerting Alchemy

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

From 441.1 to 440.1 From 647.1 to 646.1

From version 646.1

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

Change comment: There is no comment for this version

To version 441.1

edited by CarlijnKokkeler
on 2024/04/08 12:40

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 @@
--226 - Alerting Alchemy
++218 - Sprightly Spring

Content

@@ -3,56 +3,41 @@
  (((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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!
++**Hi there, eMagiz developers!**
--== **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.
--[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
++== **Spring 6 Migration** ==
++As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release.
++Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
++* JDBC BoneCP data source
++* SSL web service message sender
++* Web service outbound gateway
++* SFTP session factory
++* HTTP components message sender
++* Job manager
++* Credentials
++* Simple job launcher
++* Default SFTP session factory
--{{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}}
++Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
--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.
++In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
--{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
++This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new image will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].
--//__Tenant technical name__//
--The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
++== **Feedback Items** ==
--//__Tenant transfer__//
--A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
++== **Bug Fixes** ==
++//__Runtime overview improvements__//
++The runtime overview has been improved regarding checks on the runtime version.
--//__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.
--
--//__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.
--
--[[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'.
--
  == **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:
--* [[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"]]
++* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
++* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
  == **Key Takeaways** ==
@@ -62,7 +62,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>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
++* Check out the release notes [here]
  * 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