Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 649.1
edited by CarlijnKokkeler
on 2024/07/30 16:40
Change comment: There is no comment for this version
To version 517.1
edited by CarlijnKokkeler
on 2024/05/06 14:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +220 - Patch Parade
Content
... ... @@ -3,56 +3,79 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
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!
6 +**Hi there, eMagiz developers!** In the last few weeks, we worked hard on solving several feedback items and bug fixes. On top of that, we have released a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] that ensures that Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. Without further ado, let us look at our improvements and bug fixes below.
7 7  
8 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.
18 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
20 20  
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
21 21  
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}}
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
23 23  
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.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
25 25  
26 -{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
27 27  
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.
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
30 30  
31 -//__Tenant transfer__//
32 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
33 33  
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.
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
36 36  
37 -//__Machine details pop-up__//
38 -* The machine details 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.
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
41 41  
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'.
33 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
49 49  
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
37 +
38 +== **Bug Fixes** ==
39 +//__Annotation styling__//
40 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
41 +
42 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
43 +
44 +//__Filter rejection warnings__//
45 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
46 +
47 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
48 +
49 +//__Manage Explore__//
50 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
51 +
52 +//__Page refreshing__//
53 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
54 +
55 +//__JMS header handling__//
56 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released.
57 +
58 +//__Message redelivery__//
59 +An issue has been fixed where large messages would be shown at the bottom of the Redelivery page instead of the right side of the page.
60 +
61 +//__Deployment plan__//
62 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
63 +
64 +//__Overview pages__//
65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
66 +
67 +//__Memory check__//
68 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
69 +
70 +//__Copy password__//
71 +The copy to clipboard button now copies the actual value of passwords instead of the masked value of them.
72 +
50 50  == **Fancy Forum Answers** ==
51 51  
52 52  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:
53 53  
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"]]
77 +* [[Swagger UI: 503 Service Unavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]
78 +* [[PATCH call without REST template>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]
56 56  
57 57  == **Key Takeaways** ==
58 58  
... ... @@ -62,7 +62,7 @@
62 62  * If you have feedback or ideas for us, talk to the Platypus
63 63  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 64  * Clear your browser cache (Ctrl + Shift + Del)
65 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
88 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.220 - Patch Parade.WebHome||target="blank"]]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
68 68  * Keep making great integrations