Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 437.1
edited by CarlijnKokkeler
on 2024/04/08 11:20
Change comment: There is no comment for this version
To version 648.1
edited by CarlijnKokkeler
on 2024/07/30 16:37
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,65 +3,56 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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 -
9 -== **Spring 6 Migration** ==
10 -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.
11 -
12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
13 -* JDBC BoneCP data source
14 -* SSL web service message sender
15 -* Web service outbound gateway
16 -* SFTP session factory
17 -* HTTP components message sender
18 -* Job manager
19 -* Credentials
20 -* Simple job launcher
21 -* Default SFTP session factory
22 -
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
24 -
25 -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||target="blank"]].
26 -
27 27  == **Feedback Items** ==
28 -//__Dynamic trigger__//
29 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
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.
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
19 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
32 32  
33 -//__Copy to clipboard buttons__//
34 -Copy to clipboard buttons have been added to various pages:
35 35  
36 - * Deploy agent pop-up
37 - * Create - Flow designer: Properties
38 - * Deploy - Property releases: Property details
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}}
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
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.
41 41  
42 -//__Reset H2 database__//
43 -For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.
26 +{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
44 44  
45 -{{info}}Please note the following:
28 +//__Tenant technical name__//
29 +For multi-tenant system integrations, the technical name of a tenant cannot be changed once the tenant has been transferred to Create.
46 46  
47 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
48 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
49 -* For on-premise runtimes, only a reset of the runtime is needed.
31 +//__Tenant transfer__//
32 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
50 50  
51 -For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}}
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.
52 52  
53 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
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.
54 54  
55 -== **Bug Fixes** ==
56 -//__Runtime overview improvements__//
57 -The runtime overview has been improved regarding checks on the runtime version.
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'.
58 58  
59 59  == **Fancy Forum Answers** ==
60 60  
61 61  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:
62 62  
63 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
64 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||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"]]
65 65  
66 66  == **Key Takeaways** ==
67 67  
... ... @@ -71,7 +71,7 @@
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 72  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 -* Check out the release notes [here]
65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
75 75  * Start thinking about how the license tracker can aid your development
76 76  * Start thinking about major, minor, and patch
77 77  * Keep making great integrations