Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 646.1
edited by CarlijnKokkeler
on 2024/07/30 13:32
Change comment: There is no comment for this version
To version 362.1
edited by CarlijnKokkeler
on 2024/01/29 14:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +213 - Joyful Journeys
Content
... ... @@ -3,56 +3,83 @@
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 this release, several improvements for pop-ups have been achieved.
7 7  
8 +
9 +== **Pop-up Improvements** ==
10 +//__Property releases__//
11 +When a new property release is created, this property release can now be viewed and deleted.
12 +
13 +[[image:Main.Images.Release Blog.WebHome@release-blog-213-joyful-journeys-property-release.png]]
14 +
15 +//__Runtime deletion__//
16 +When deleting a runtime, the error message that is displayed is more descriptive. The error messages will now include the names of the flows that run on the container.
17 +
18 +//__Wiretap & debug error messages__//
19 +The error messages that may be displayed when using wiretaps and the debugger have been improved, these are now more user friendly.
20 +
21 +//__Action messages__//
22 +The formatting of action messages regarding changes in retention bytes/hours has been improved. The action message will now display the correct, actual behaviour.
23 +
24 +
25 +== **Formatting & Alignments** ==
26 +
27 +//__Input fields__//
28 +Multiple input fields have been updated such that they expand when the amount of characters exceeds the default size. These updates were done to cater to large expressions.
29 +
30 +//__UI improvements__//
31 +UI improvements for static input components have been done and the tooltip for optional/required toggles has been improved.
32 +
33 +//__Runtime overview image versions__//
34 +Insight into invented and actual deployments has been improved. If the release version number on runtimes is different compared with the release, this is shown in the runtime overview.
35 +
36 +//__Component changes reversion__//
37 +In the flow designer a bug could occur where the changes to a component would be reverted if the editing pop-up would be kept open for some minutes without having saved the changes yet. This has been fixed.
38 +
39 +//__State generation statistics__//
40 +The state generation graphs will now show the correct number of cache hits and misses.
41 +
42 +//__Queue browser timestamps__//
43 +All timestamp formatting in the queue browser is now aligned to yyyy-MM-dd HH:mm:ss.SSS.
44 +
45 +//__Addition and deletion of internal recipients__//
46 +Internal recipients are now added and deleted correctly. Before, an internal recipient could be added and thereafter deleted automatically when refreshing the page.
47 +
48 +
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]]
51 +//__Update flows__//
52 +In Create > Resources, a button "Update flows" has been added to update versions of all flows in which a resource is used.
20 20  
54 +//__Q&A forum search__//
55 +The option to search by pressing the Enter key has been added to the Q&A forum.
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}}
57 +//__Memory settings__//
58 +It is now possible to change the memory settings of a container before pressing "Apply to environment". Before, it was only possible to view the memory settings if a container was running on AWS or running on a docker machine.
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.
60 +//__Runtime validation__//
61 +Validation for runtimes that are moved from on premises to the cloud or vice versa has been improved.
25 25  
26 -{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
27 27  
28 -//__Tenant technical name__//
29 -The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
64 +== **Bug Fixes** ==
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.
66 +//__Removal of onramp__//
67 +We fixed an issue where it was not possible to remove the last onramp linked to a splitted entry (that was an all-entry before).
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.
69 +//__Runtime statistics details__//
70 +We fixed an issue where heap memory usage data was accumulating when zooming out in the runtime statistics details dashboards.
36 36  
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.
72 +//__Deployment prechecks__//
73 +During deployments prechecks will be done on runtimes that still have to be deployed from deploy architecture.
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'.
49 49  
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"]]
80 +* [[What is the eMagiz control tower?>>https://my.emagiz.com/p/question/172825635703696612||target="blank"]]
81 +* [[Deleting connector without flows gives error>>https://my.emagiz.com/p/question/172825635703696657]]
82 +* [[How to use a flowtest with path properties>>https://my.emagiz.com/p/question/172825635703696835||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"]]
92 +* Check out the release notes [here]
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