Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 1.1
edited by eMagiz
on 2022/10/12 10:29
Change comment: There is no comment for this version
To version 641.1
edited by CarlijnKokkeler
on 2024/07/29 14:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - To determine
1 +226 - Alerting Alchemy
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,78 +1,81 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** We have been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that big development, we have finished our work on the Flow Designer which is the major part of this release. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
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 6  
7 -==**Flow Designer V3**==
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.
8 8  
9 -The new Flow Designer used in Create is released! This is a significant improvement in our iPaaS Portal that implements feedback of our users and helps to improve the overall experience. After several iterations of internal validations and testing sessions with end-users, we are releasing this feature to all users. Below are some key notes that are important to know and to consider.
10 -
11 -=== **Improvements** ===
12 -The new Flow Designer implements an approach whereby components can be dragged into the canvas without any configuration setting changed. The right hand panel contains a new section called Alerts that helps users to remove all alerts from the flow created. Such as missing configurations, channels or mismatches. All of these alerts need to be resolved so that a valid flow can be pushed to Deploy.
19 +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.
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 1.png]]
21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
15 15  
16 -Furthermore, there is now a right hand panel to brings a few configuration more forward for users. In that panel you will find the following 4 tabs as described below. Furthermore, you can collapse the right hand panel to have more space to view/edit your flow.
17 -
18 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 2.png]]
19 -
20 -* **Alerts**
21 -In this section, all alerts are displayed organized by component. Alert text should be clear to understand the issue and the component can be opened from that same location.
23 +{{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}}
22 22  
23 -* **Resources**
24 -In this section, all resources are displayed used by the flow. Resources can be added and deleted from this section, as well as download and viewed. Generated resources such as transformations and definition are also vieweable from here. Use the option Show generated resources to explore these.
25 -
26 -* **Support objects**
27 -The support objects are no longer stored on the canvas, but displayed as a list in this tab. The interaction to add new support objects is also moved to this tab. Support objects can be edited from this tab as well. Please note that the interaction with the main canvas remains - selecting a support object will highlight the components in the canvas to illustrate where that support object is used.
25 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
28 28  
29 -* **Properties**
30 -The properties tab is also visible now and has been improved so that the values in Deploy can also be viewed. All values of all environments can be viewed - container level properties replicated are condensed into a single entry.
31 -
32 -=== **User interaction changes** ===
33 -There are some small changes to consider compared to the old flow designer. Please take a moment to read these:
34 -
35 -* Multiple select. This option is still available, but you have to click the shift button while drawing the rectangle that holds the objects to select
36 -* Live preview. When moving components around, a live preview of the flow is displayed so that alignment becomes easier
27 +//__Tenant technical name__//
28 +The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
37 37  
38 -
39 -== **Feedback items ** ==
30 +//__Tenant transfer__//
31 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
40 40  
41 -We have also solved other feedback items besides the key updates around functionality.
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.
42 42  
43 -//__Set runtime field as first selected field on property level__//
44 -With this change, the runtime is the first field selected when copying a property. This way it is easier to select another runtime and propagate that property to that runtime as well.
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.
45 45  
46 -[[image:Main.Images.Release Blog.WebHome@184 - FlowDesigner releaseblog 3.png]]
41 +[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]]
47 47  
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'.
48 48  
49 49  == **Fancy Forum Answers** ==
50 50  
51 -As always, a gentle reminder to all 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:
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 -* [[Excel Attachment in Mail to File>>https://my.emagiz.com/p/question/172825635703120756||target="blank"]]
54 -* [[Importing datapipeline store component Mendix to AWS Redshift failed>>https://my.emagiz.com/p/question/172825635703120551||target="blank"]]
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"]]
55 55  
56 -== **Key takeaways** ==
56 +== **Key Takeaways** ==
57 57  
58 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
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  
60 60  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  * If you have feedback or ideas for us, talk to the Platypus
62 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
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]
64 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
65 65  * Start thinking about how the license tracker can aid your development
66 66  * Start thinking about major, minor, and patch
67 -* Upgrade to the latest build number
68 68  * Keep making great integrations
69 -* Check out the new documentation portal.
70 70  
71 71  Let's stay in touch and till next time!
72 72  
73 73  {{info}}
74 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
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]]
75 75  
76 -~*~* Indicates a GEN3-only feature.
77 -{{/info}})))((({{toc/}}))){{/container}}
74 +{{/info}}
75 +)))
76 +
77 +(((
78 +{{toc/}}
79 +)))
78 78  {{/container}}
81 +{{/container}}