Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 647.1
edited by CarlijnKokkeler
on 2024/07/30 16:24
Change comment: There is no comment for this version
To version 130.1
edited by Erik Bakker
on 2023/07/17 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -226 - Alerting Alchemy
1 +201 - Be Informed
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,70 +1,73 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
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!
5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the previous Q. More on that later. On top of that, we have several smaller items as a result of our hackathon efforts to present to you.
7 7  
7 +== **Announcement - Release Properties** ==
8 +As of the next release (202), we will introduce a new way of handling properties for all our clients. In the upcoming weeks, we will publish additional information on the process, what changes, and how you best manage your properties as of then within the documentation portal. Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
9 +
10 +== ** Deploy Architecture - Apply To Environment improvements ** ==
11 +As of this release, we will show you a list of all changes about to be changed once you press "Apply to the environment" in Deploy Architecture. This will make it clearer for users, especially those working in teams, what will change when pressing this button.
12 +
13 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--apply-to-environment-example.png]]
14 +
15 +== ** Breadcrumb navigation in eMagiz ** ==
16 +This release introduces the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed and impact the Create phase when you check out your transformation or system message on the flow level. Apart from there, the navigation is implemented consistently across the portal for a unified look and feel.
17 +
18 +[[image:Main.Images.Release Blog.WebHome@201-release-blog--breadcrumb-navigation-example.png]]
19 +
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 18  
19 -[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]]
22 +//__Improved layout of catalog page in Design__//
23 +We have improved the layout of the API Catalog overview in Design for our API Gateway users. Among others, we have introduced a scrollbar to get a better overview of several operations.
20 20  
25 +//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26 +Currently, the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
21 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}}
28 +//__Additional help texts on Design Architecture__//
29 +We have improved the help texts in Design Architecture concerning the Event Streaming topic storage overview.
23 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.
31 +//__Improved Audit Trail on several places__//
32 +In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
25 25  
26 -{{warning}}Please note that the new queue alerting will not yet be available for models with message redelivery. {{/warning}}
34 +//__Removed the erroneous alert on message mapping when having a passthrough API__//
35 +This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
27 27  
28 -//__Tenant technical name__//
29 -The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
37 +== **Bug Fixes** ==
30 30  
31 -//__Tenant transfer__//
32 -A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
39 +//__Avoid clicking on other components while deleting another__//
40 +To avoid unexpected behavior, we now ensure that nothing can be selected once you see the "deletion" pop-up when you want to remove something in the flow designer.
33 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.
42 +//__Improved validation feedback in migrating to the next-generation architecture__//
43 +We have improved the validation feedback when migrating to the next-generation architecture.
36 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.
45 +//__Make sure that user credentials can be viewed with view rights__//
46 +This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
41 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'.
48 +//__Refresh behavior within the deployment plan is fixed__//
49 +This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
49 49  
50 50  == **Fancy Forum Answers** ==
51 51  
52 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 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"]]
55 +* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
56 +* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
57 +* [[Split gateway configuration for local GEN3 gateway>>https://my.emagiz.com/p/question/172825635703517580||target="blank"]]
56 56  
57 -== **Key Takeaways** ==
59 +== **Key takeaways** ==
58 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:
61 +Thanks to all that 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 60  
61 61  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
62 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.
65 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
64 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"]]
67 +* Check out the release notes [here]
66 66  * Start thinking about how the license tracker can aid your development
67 67  * Start thinking about major, minor, and patch
70 +* Upgrade to the latest build number
68 68  * Keep making great integrations
69 69  
70 70  Let's stay in touch and till next time!
... ... @@ -72,11 +72,6 @@
72 72  {{info}}
73 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 74  
75 -{{/info}}
76 -)))
77 -
78 -(((
79 -{{toc/}}
80 -)))
78 +~*~* Indicates a GEN3-only feature.
79 +{{/info}})))((({{toc/}}))){{/container}}
81 81  {{/container}}
82 -{{/container}}