Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 623.1
edited by CarlijnKokkeler
on 2024/07/29 12:22
Change comment: There is no comment for this version
To version 280.1
edited by CarlijnKokkeler
on 2023/12/04 15:00
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,30 +3,56 @@
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 +== **Release Maintenance** ==
9 +
10 +
11 +
12 +
13 +
8 8  == **Feedback Items** ==
9 -//__Queue alerting__//
10 -Alerting for message queues has been improved, 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 -
15 +
16 +//__Container version overview__//
17 +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.
18 +
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-209-deployment-delights-container-overview.png]]
20 +
21 +//__Unchanged containers__//
22 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
23 +
24 +//__Rebuilding of images__//
25 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
26 +
27 +
19 19  == **Bug Fixes** ==
20 20  
30 +//__Runtime metrics processing__//
31 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
32 +
33 +//__Deployment plan__//
34 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
35 +
36 +//__Store message merging__//
37 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
38 +
39 +//__View all store items__//
40 +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.
41 +
42 +//__Out of memory behavior__//
43 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
44 +
45 +//__Max fetch size__//
46 +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.
47 +
48 +
21 21  == **Fancy Forum Answers** ==
22 22  
23 23  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:
24 24  
25 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
26 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
27 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
28 28  
29 -== **Key Takeaways** ==
55 +== **Key takeaways** ==
30 30  
31 31  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:
32 32  
... ... @@ -34,9 +34,10 @@
34 34  * If you have feedback or ideas for us, talk to the Platypus
35 35  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
36 36  * Clear your browser cache (Ctrl + Shift + Del)
37 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
63 +* Check out the release notes [here]
38 38  * Start thinking about how the license tracker can aid your development
39 39  * Start thinking about major, minor, and patch
66 +* Upgrade to the latest build number
40 40  * Keep making great integrations
41 41  
42 42  Let's stay in touch and till next time!
... ... @@ -44,6 +44,7 @@
44 44  {{info}}
45 45  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
46 46  
74 +~*~* Indicates a next-generation-architecture only feature.
47 47  {{/info}}
48 48  )))
49 49