Skip to Content

Wiki source code of 226 - Alerting Alchemy

Version 647.1 by CarlijnKokkeler on 2024/07/30 16:24
Show last authors
1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
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!
7
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
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}}
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.
25
26 {{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
27
28 //__Tenant technical name__//
29 The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
30
31 //__Tenant transfer__//
32 A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
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.
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.
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
50 == **Fancy Forum Answers** ==
51
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
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"]]
56
57 == **Key Takeaways** ==
58
59 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:
60
61 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62 * If you have feedback or ideas for us, talk to the Platypus
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 * 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"]]
66 * Start thinking about how the license tracker can aid your development
67 * Start thinking about major, minor, and patch
68 * Keep making great integrations
69
70 Let's stay in touch and till next time!
71
72 {{info}}
73 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74
75 {{/info}}
76 )))
77
78 (((
79 {{toc/}}
80 )))
81 {{/container}}
82 {{/container}}