Changes for page 207 - Aligned State

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+206 - Situational Deployment

Author

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

Content

...	...	@@ -2,67 +2,67 @@
2	2	{{container layoutStyle="columns"}}(((
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 improving our next-generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore, several smaller feedback items and bugs have been resolved with this release. So without further ado, let us dive into all we have to offer.
	5	+**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6	6
7		-== **Event streaming alerting** ==
	7	+== **Deployment Plan** ==
8	8
9		-This release expands our alerting functionality into the event streaming pattern. As of now, one new "static" alert has been introduced for all clients (using event streaming), and two "dynamic" alerts have been introduced that you can configure yourself if there is a need for it.
	9	+//__Improved deployment plan to make the process better and more predictable__//
	10	+The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
10	10
11		-The "static" alert we have added raises an alert (and a subsequent email) when the actual topic size crosses the threshold of 80% of the configured maximum retention size on a topic. This alert provides insights into whether messages on it are deleted due to a size or time constraint. In cases where data is deleted, the topic was too full way before the messages should have been removed due to the retention hours constraint. This alert can indicate that messages might be deleted before consumer groups had the option to consume the messages.
	12	+//__Editing release properties__//
	13	+With this release, it will be possible to change the description of a property by editing the property.
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
	15	+//__JMS memory setting check__//
	16	+A change in memory settings triggers redeployment of the container now.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	18	+//__Properties tab__//
	19	+We have removed the deprecated tab Properties in the Deploy phase.
	20	+
	21	+//__Cleanup old images__//
	22	+
	23	+== **Store Improvements** ==
	24	+
16	16
17		-The first new "dynamic" alert allows you to raise an alert once the number of messages on one (or more topics) is less than a certain number per defined time unit. So, for example, you can configure an alert once the number of messages placed on a topic called "Exception" is less than 15 messages within 5 minutes.
	26	+== **Feedback Items** ==
18	18
19		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
	28	+//__Alerting manual pause__//
	29	+A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
20	20
21		-The second new "dynamic" alert allows you to raise an alert once one (or more) consumer groups are more than X messages behind on one or more topics. The configuration of this is comparable to what we saw before.
	31	+//__Ordering of graphs in Manage__//
	32	+The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
22	22
23		-For more information on the generic way of working surrounding alerting, please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] and this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Novice.Alerting.novice-alerting-dynamic-alerting.WebHome||target="blank"]].
	34	+//__UTC times in Grafana panels__//
	35	+All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
24	24
25		-== **3rd generation improvements** ==
	37	+//__Update flow designer version__//
	38	+The framework used in the flow designer has been updated to the latest version.
26	26
27		-//__Increased grace period for shutdown__//
28		-In this release, we have increased a container's grace period to shut down before it is forcefully shut down. This should reduce the chance of unwanted failover behavior within your model.
29	29
30		-//__Update at once or not__//
31		-This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup.
	41	+
	42	+== **Bug Fixes** ==
32	32
33		-//__Improved user feedback while executing a deployment plan__//
34		-This release introduces additional feedback to the user when the deployment plan is executed. This is noticeable when a step cannot be executed properly. The relevant information about why this cannot be executed is shown to the user. This way, they can take this information and act upon it instead of assuming everything went well.
	44	+//__Gain the ability again to configure certificates in Deploy Architecture again__//
	45	+In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
35	35
36		-//__Improved auto-healing when running in a hybrid situation__//
37		-In situations where you run in a hybrid situation (i.e., partly next-gen and partly the current generation), we have improved the auto-healing functionality in case an "out of memory" appears on a runtime running in the current generation but on a next-generation architecture.
	47	+//__Ensure that differing container configurations deploy the correct configuration__//
	48	+When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
38	38
39		-//__Improved rollup and storage of metrics when running your solution in the next generation archticture__//
40		-To improve the stability of the Manage phase and, in particular, the metrics when zooming out on the provided information, we have made some structural changes that support this user functionality better.
	50	+//__Remove queurying options in Manage__//
	51	+To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
41	41
42		-{{warning}} Due to this change, the platform will remove data collected before the release date in the upcoming weeks. This process will be finished at the beginning of June. From then on, all data before the 12th of May will no longer be visible. As users generally do not look back this far back in time, we consider this an acceptable trade-off. {{/warning}}
43		-
44		-== **Feedback items ** ==
45		-
46		-//__Make sure the message format can be viewed without "Start editing"__//
47		-With this release, we have ensured that when you navigate to Design -> System message, you can see the message format (i.e., XML, JSON, or EDI) without entering the "Start Editing" mode.
48		-
49		-//__Various styling improvements in the flow testing functionality__//
50		-Various minor styling improvements have been added to the flow testing functionality to improve the overall user experience. Please check out the release notes for a complete list and more details.
51		-
52	52	== **Fancy Forum Answers** ==
53	53
54	54	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:
55	55
56		-* [[Update Core01 without downtime?>>https://my.emagiz.com/p/question/172825635703427783||target="blank"]]
57		-* [["EDI" mapping?>>https://my.emagiz.com/p/question/172825635703440524||target="blank"]]
	57	+* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
58	58
59	59	== **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:
	61	+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.
	65	+* 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	67	* Check out the release notes [here]
68	68	* Start thinking about how the license tracker can aid your development
...	...	@@ -75,6 +75,6 @@
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.
	78	+~*~* Indicates a next-generation-architecture only feature.
79	79	{{/info}})))((({{toc/}}))){{/container}}
80	80	{{/container}}