Changes for page 226 - Alerting Alchemy

Summary

• Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-201 - Be Informed
	1	+226 - Alerting Alchemy

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ebakker
	1	+XWiki.CarlijnKokkeler

Content

...	...	@@ -1,73 +1,55 @@
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!** In the last few weeks, we have worked hard on planning the upcoming Q and finishing up features of the last 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.
	6	+**Hi there, eMagiz developers!** In this release,
6	6
7		-== **Announcement - Release Properties** ==
8		-As of the next release (202) we will introduce a completely 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 contact 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 change that are about to be changed once you press "Apply to environment" in Deploy Architecture. This will ensure that it becomes clearer for users, especially those working together 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		-With this release we introduce the "breadcrumb" navigation in certain parts of eMagiz. This will mostly be noticed, and have impact, in the Create phase when you are checking out your transformation or system message on 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		-
20	20	== **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	+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.
21	21
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 when having several operations.
	21	+{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
24	24
25		-//__Improved layout of "Edit integration" pop-up for API Gateway integrations__//
26		-As of now the full path of your backend system will be shown when opening the "Edit integration" pop-up on your API Gateway integration.
	23	+//__Tenant technical name__//
	24	+ The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
27	27
28		-//__Additional help texts on Design Architecture__//
29		-We have improved the help texts in Design Archicture in relation to the Event Streaming topic storage overview.
	26	+//__Tenant transfer__//
	27	+A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
30	30
31		-//__Improved Audit Trail on several places__//
32		-In several places in the portal we have improved the audit trail to better specify who changed what at which point in time.
	29	+//__Property placeholder__//
	30	+A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
33	33
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.
36		-
37	37	== **Bug Fixes** ==
38	38
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.
41		-
42		-//__Improved validation feedback in migrating to the next-generation architecture__//
43		-We have improved several things with regards to the validation feedback when migrating to the next-generation architecture.
44		-
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 viewed with view rights and not only when having edit rights.
47		-
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.
50		-
51	51	== **Fancy Forum Answers** ==
52	52
53	53	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:
54	54
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"]]
	38	+* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
	39	+* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
	40	+* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
58	58
59		-== **Key takeaways** ==
	42	+== **Key Takeaways** ==
60	60
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:
	44	+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:
62	62
63	63	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
64	64	* If you have feedback or ideas for us, talk to the Platypus
65		-* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
	48	+* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
66	66	* Clear your browser cache (Ctrl + Shift + Del)
67		-* Check out the release notes [here]
	50	+* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]]
68	68	* Start thinking about how the license tracker can aid your development
69	69	* Start thinking about major, minor, and patch
70		-* Upgrade to the latest build number
71	71	* Keep making great integrations
72	72
73	73	Let's stay in touch and till next time!
...	...	@@ -75,6 +75,11 @@
75	75	{{info}}
76	76	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
77	77
78		-~*~* Indicates a GEN3-only feature.
79		-{{/info}})))((({{toc/}}))){{/container}}
	60	+{{/info}}
	61	+)))
	62	+
	63	+(((
	64	+{{toc/}}
	65	+)))
80	80	{{/container}}
	67	+{{/container}}