Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 643.1
edited by CarlijnKokkeler
on 2024/07/30 13:10
Change comment: There is no comment for this version
To version 284.1
edited by CarlijnKokkeler
on 2023/12/04 15:20
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +210 - Deployment Delights
Content
... ... @@ -3,57 +3,56 @@
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!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 +== **Alerts** ==
9 +
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
12 +
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 +
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 -
19 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
20 20  
21 -{{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}}
18 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
22 22  
23 -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 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
24 24  
25 -{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}}
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
26 26  
27 -//__Tenant technical name__//
28 -The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
29 29  
30 -//__Tenant transfer__//
31 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
29 +== **Bug Fixes** ==
32 32  
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.
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
35 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.
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
40 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'.
37 +//__Store message merging__//
38 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
48 48  
40 +//__View all store items__//
41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
42 +
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
45 +
46 +//__Max fetch size__//
47 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
48 +
49 49  == **Fancy Forum Answers** ==
50 50  
51 51  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:
52 52  
53 -* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]]
54 -* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
55 55  
56 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
57 57  
58 58  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
59 59  
... ... @@ -61,9 +61,10 @@
61 61  * If you have feedback or ideas for us, talk to the Platypus
62 62  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
63 63  * Clear your browser cache (Ctrl + Shift + Del)
64 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]]
63 +* Check out the release notes [here]
65 65  * Start thinking about how the license tracker can aid your development
66 66  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
67 67  * Keep making great integrations
68 68  
69 69  Let's stay in touch and till next time!
... ... @@ -71,6 +71,7 @@
71 71  {{info}}
72 72  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  
74 +~*~* Indicates a next-generation-architecture only feature.
74 74  {{/info}}
75 75  )))
76 76