Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-202 - New Equilibrium
	1	+226 - Alerting Alchemy

Author

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

Content

...	...	@@ -1,84 +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 crossed our t's and dotted our i's on the release properties functionality that will impact the day to day life of every user working within the platform. The focus of the release blog will consequently also be on this subject. On top of that we have several additional smaller feedback item coming from our hackathon efforts that are now released to you.
	6	+**Hi there, eMagiz developers!** In this release,
6	6
7		-== **Release Properties** ==
8		-As of this release, we will introduce a new way of handling properties for all our clients. This change intends to solidify the relationship between a release and a property value. Before, in the current generation architecture, timing of changing properties was crucial to avoid costly mistakes on Production. On top of that it was not always clear whether a property value was indeed updated as it was not linked to something that was deployed. These considerations let us to change the property management behavior not only on our next-generation architecture but also on our current generation architecture. Having said that, there are several key changes compared to the current way of managing your properties. Most notably among these are:
9		-
10		-* The current properties tab in Deploy will disappear. The new overview of the properties (and their values) can be found under the "Create phase release" in Deploy -> Releases
11		-* Property placeholders (i.e. the names of properties as given in Create) are now automatically created for you. This to avoid mistakes when filling them in.
12		-* When adding or editing a property you can *now* select multiple runtimes for which the property applies. This is mainly beneficial for those running in a double lane setup or having a distributed landscape of containers.
13		-* A, for most, new concept of a "property release" is introduced. With the help of this functionality you can easily change a property on Production without having to create a completely new release in Test and promote it to the Production environment.
14		-
15		-{{info}}For more information please check out the following microlearnings:
16		-
17		-* [[Property Management>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]]
18		-* [[Actualize properties - current generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-new.WebHome||target="blank"]]
19		-* [[Actualize properties - next generation architecture>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-actualize-properties-gen3-new.WebHome||target="blank"]]
20		-
21		-Should you have any questions in advance, please get in touch with us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
22		-{{/info}}
23		-
24		-== ** Manage - Next generation graphs improvements ** ==
25		-As of this release, we will create a condensed view of your metrics when zooming out in the Manage phase graphs. This will significantly improve the performance of the manage graphs as we retrieve and show less fine-grained information when zooming out.
26		-
27		-[[image:Main.Images.Release Blog.WebHome@202-release-blog--manage-graphs-zoomed-out.png]]
28		-
29	29	== **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.
30	30
31		-//__Improved editability when testing in eMagiz wihout Edit rights in Create__//
32		-Without having edit rights in the Create phase you could already do a lot on the level of flow tests in eMagiz. However, there were some oversights we missed during the implementation. These have been fixed allowing those without edit rights to now also change the name and description of the test case.
	21	+{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}}
33	33
34		-//__Improved auditability on Deploy Architecture__//
35		-To improve the audtiability on Deploy Architecture we now also log when someone with Admin rights changes specific functions on this level (i.e. Fixed IP).
	23	+//__Tenant technical name__//
	24	+ The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
36	36
37		-//__Test your own exported work__//
38		-We have now made it possible to test your own exported work to the Store before it gets approved. This will increase the quality of store items we have, and our partners, have on offer within the store.
	26	+//__Tenant transfer__//
	27	+A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
39	39
40		-{{info}}In case the concept of the store is new for you please check out this [[Fundamental>>doc:Main.eMagiz Academy.Fundamentals.fundamental-emagiz-store.WebHome||target="blank"]]{{/info}}
	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.
41	41
42		-//__Improved Audit Trail on several places__//
43		-In several places in the portal, we have improved the audit trail to specify better who changed what at which point in time.
44		-
45		-//__Removed the erroneous alert on message mapping when having a passthrough API__//
46		-This release removes the erroneous alert people reported on "errors in message mapping" for a passthrough API.
47		-
48	48	== **Bug Fixes** ==
49	49
50		-//__Avoid clicking on other components while deleting another__//
51		-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.
52		-
53		-//__Improved validation feedback in migrating to the next-generation architecture__//
54		-We have improved the validation feedback when migrating to the next-generation architecture.
55		-
56		-//__Make sure that user credentials can be viewed with view rights__//
57		-This release makes sure that the user credentials in Deploy can be considered with view rights and not only when having edit rights.
58		-
59		-//__Refresh behavior within the deployment plan is fixed__//
60		-This release changes the refresh behavior within the deployment plan to show, once more, the "to be installed" flows before the user presses Execute.
61		-
62	62	== **Fancy Forum Answers** ==
63	63
64	64	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:
65	65
66		-* [[Replacing Legacy eMagiz-Mendix Connector: Migration Plan>>https://my.emagiz.com/p/question/172825635703517317||target="blank"]]
67		-* [[Unknown character(s) does not create error message.>>https://my.emagiz.com/p/question/172825635703517488||target="blank"]]
68		-* [[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"]]
69	69
70		-== **Key takeaways** ==
	42	+== **Key Takeaways** ==
71	71
72		-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:
73	73
74	74	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
75	75	* If you have feedback or ideas for us, talk to the Platypus
76		-* 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.
77	77	* Clear your browser cache (Ctrl + Shift + Del)
78		-* 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"]]
79	79	* Start thinking about how the license tracker can aid your development
80	80	* Start thinking about major, minor, and patch
81		-* Upgrade to the latest build number
82	82	* Keep making great integrations
83	83
84	84	Let's stay in touch and till next time!
...	...	@@ -86,6 +86,11 @@
86	86	{{info}}
87	87	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
88	88
89		-~*~* Indicates a GEN3-only feature.
90		-{{/info}})))((({{toc/}}))){{/container}}
	60	+{{/info}}
	61	+)))
	62	+
	63	+(((
	64	+{{toc/}}
	65	+)))
91	91	{{/container}}
	67	+{{/container}}