Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 461.1
edited by CarlijnKokkeler
on 2024/04/15 12:27
Change comment: There is no comment for this version
To version 636.1
edited by CarlijnKokkeler
on 2024/07/29 13:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +226 - Alerting Alchemy
Content
... ... @@ -3,43 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
6 +**Hi there, eMagiz developers!** In this release,
7 7  
8 -== **Spring 6 Migration** ==
9 -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 this release.
8 +== **Feedback Items** ==
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.
10 10  
11 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
12 -* JDBC BoneCP data source
13 -* SSL web service message sender
14 -* Web service outbound gateway
15 -* SFTP session factory
16 -* HTTP components message sender
17 -* Job manager
18 -* Credentials
19 -* Simple job launcher
20 -* Default SFTP session factory
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.
21 21  
22 -{{info}}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"]].
21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
23 23  
24 -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 [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] 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>>doc:Main.Release Information.Runtime Images.V300.WebHome||target="blank"]]. {{/info}}
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}}
25 25  
26 -{{info}}Please be aware that we will create autosaved versions for affected flows still running on the legacy runtime architecture. This way, we ensure consistency in what the user sees when working with flow components in the Create phase while at the same time prepare your model for a future migration to the current runtime architecture. Should you need to make a functional change in one of these affected flows, you can do so without a deployment and without using Spring 6 in your legacy runtime. {{/info}}
25 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
27 27  
28 -== **Feedback Items** ==
29 -//__Event streaming logging__//
30 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
27 +//__Tenant technical name__//
28 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
31 31  
32 -//__Root Cloud__//
33 -Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
30 +//__Tenant transfer__//
31 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
34 34  
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 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 37  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:
38 38  
39 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
40 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
41 -* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
42 -* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||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"]]
43 43  
44 44  == **Key Takeaways** ==
45 45  
... ... @@ -49,7 +49,7 @@
49 49  * If you have feedback or ideas for us, talk to the Platypus
50 50  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
51 51  * Clear your browser cache (Ctrl + Shift + Del)
52 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.218 - Sprightly Spring||target="blank"]]
65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
53 53  * Start thinking about how the license tracker can aid your development
54 54  * Start thinking about major, minor, and patch
55 55  * Keep making great integrations