Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 526.1
edited by CarlijnKokkeler
on 2024/05/21 11:44
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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -221 - Swift Shift
1 +226 - Alerting Alchemy
Content
... ... @@ -3,52 +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 8  == **Feedback Items** ==
9 -//__Q&A search__//
10 -Search results are now persisted when pressing the back button after opening a question in the community Q & A.
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.
11 11  
12 -//__Event catalog__//
13 -For Catalog users, we have significantly improved the Event Catalog overview by introducing a much simpler layout for easier navigation.
19 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
14 14  
15 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-catalog-2.png]]
16 16  
17 -//__Attribute placements__//
18 -Some improvements regarding the placement of attributes have been done:
19 -* A new attribute will be placed right below the attribute that users right-clicked on to open context menu to add new attribute.
20 -* Moving an attribute in the datamodel is now directly shown in the tree structure as well.
21 -* The pop-up that appears when rearranging attributes of an entity will result in a pop-up which text is conditional with respect to the messagetype.
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}}
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-rearrange-attribute.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.
24 24  
25 -//__Failover & grouping__//
26 -Some improvements regarding the widgets for failover and grouping have been done:
27 -* When executing a start/stop action on a group, the description of the step now contains the name of the group.
28 -* When stopping a group with the follower status, the description of the popup now correctly describes the purpose of button "Disable failover and stop group".
26 +{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
29 29  
30 -[[image:Main.Images.Release Blog.WebHome@release-221-start-stop-flows.png]]
28 +//__Tenant technical name__//
29 +The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
31 31  
32 -[[image:Main.Images.Release Blog.WebHome@release-221-stop-groups.png]]
31 +//__Tenant transfer__//
32 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
33 33  
34 -== **Bug Fixes** ==
35 -//__XSD import__//
36 -When importing an xsd to a new response or request message, you will not receive a warning message anymore to avoid confusion.
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.
37 37  
38 -[[image:Main.Images.Release Blog.WebHome@release-221-swift-shift-xsd.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.
39 39  
40 -//__Container deletion__//
41 -The delete behaviour of containers in the container overview has been improved to allow deletion of unused containers with broken flows.
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'.
42 42  
43 -//__Scope properties__//
44 -We fixed an issue where the generation of scope properties was incorrect for the legacy API gateway runtimes using OAuth 2.0 security scheme.
45 -
46 46  == **Fancy Forum Answers** ==
47 47  
48 48  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:
49 49  
50 -* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
51 -* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||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"]]
52 52  
53 53  == **Key Takeaways** ==
54 54  
... ... @@ -58,7 +58,7 @@
58 58  * If you have feedback or ideas for us, talk to the Platypus
59 59  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
60 60  * Clear your browser cache (Ctrl + Shift + Del)
61 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
62 62  * Start thinking about how the license tracker can aid your development
63 63  * Start thinking about major, minor, and patch
64 64  * Keep making great integrations