Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 624.1
edited by CarlijnKokkeler
on 2024/07/29 12:24
Change comment: There is no comment for this version
To version 281.1
edited by CarlijnKokkeler
on 2023/12/04 15:03
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +209 - Deployment Delights
Content
... ... @@ -3,32 +3,58 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release,
6 +**Hi there, eMagiz developers!** We have...
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"]] stack, 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 -If you model is running on the latest generation runtime, you will be migrated on the day of release.
20 20  
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.
20 +
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
22 +
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.
25 +
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
28 +
29 +
21 21  == **Bug Fixes** ==
22 22  
32 +//__Runtime metrics processing__//
33 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
34 +
35 +//__Deployment plan__//
36 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
37 +
38 +//__Store message merging__//
39 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
40 +
41 +//__View all store items__//
42 +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.
43 +
44 +//__Out of memory behavior__//
45 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46 +
47 +//__Max fetch size__//
48 +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.
49 +
50 +
23 23  == **Fancy Forum Answers** ==
24 24  
25 25  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:
26 26  
27 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
28 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
29 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
55 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
30 30  
31 -== **Key Takeaways** ==
57 +== **Key takeaways** ==
32 32  
33 33  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:
34 34  
... ... @@ -36,9 +36,10 @@
36 36  * If you have feedback or ideas for us, talk to the Platypus
37 37  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
38 38  * Clear your browser cache (Ctrl + Shift + Del)
39 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
65 +* Check out the release notes [here]
40 40  * Start thinking about how the license tracker can aid your development
41 41  * Start thinking about major, minor, and patch
68 +* Upgrade to the latest build number
42 42  * Keep making great integrations
43 43  
44 44  Let's stay in touch and till next time!
... ... @@ -46,6 +46,7 @@
46 46  {{info}}
47 47  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
48 48  
76 +~*~* Indicates a next-generation-architecture only feature.
49 49  {{/info}}
50 50  )))
51 51