Changes for page 226 - Alerting Alchemy

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-206 - Situational Deployment
	1	+218 - Sprightly Spring

Content

...	...	@@ -1,79 +1,48 @@
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 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	+**Hi there, eMagiz developers!**
	7	+In this release, we will do a large maintenance update, moving the eMagiz [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] stack from Spring 5 to Spring 6 and from Java 8 to Java 17. Please refer to our new [[runtime image>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]] and Spring 6 [[migration path>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]] for more information. Next to this, we have improved event streaming logging, so that logs are not cluttered with irrelevant info anymore. Lastly, we have removed the deprecated cloud option 'Root' from the portal.
6	6
7		-== **Deployment Plan** ==
	9	+== **Spring 6 Migration** ==
	10	+As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release.
8	8
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.
	12	+Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
	13	+* JDBC BoneCP data source
	14	+* SSL web service message sender
	15	+* Web service outbound gateway
	16	+* SFTP session factory
	17	+* HTTP components message sender
	18	+* Job manager
	19	+* Credentials
	20	+* Simple job launcher
	21	+* Default SFTP session factory
11	11
12		-//__Editing release properties__//
13		-With this release, it will be possible to change the description of a property by editing the property.
	23	+Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
14	14
15		-//__JMS memory setting check__//
16		-A change in memory settings triggers redeployment of the container now.
	25	+In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]].
17	17
18		-//__Properties tab__//
19		-We have removed the deprecated tab Properties in the Deploy phase.
	27	+This large maintenance update, moving the eMagiz runtime stack from Spring 5 to Spring 6 and from Java 8 to Java 17, includes moving to latest (major) versions of open source projects, libraries and technologies. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]] will be released. Although no new functionality is added in this new image version, several Spring libraries have been changed significantly. More information can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].
20	20
21		-//__Cleanup old images__//
22		-When a release is removed, the related unused images in the on-premises machines will be removed as well.
23		-
24		-//__Performance improvements for loading releases__//
25		-Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
26		-
27		-== **Store Improvements** ==
28		-
29		-//__Message definition elements order__//
30		-We fixed an issue that the orders of message definition’s elements were changed after they were imported.
31		-
32		-//__Message definition elements order__//
33		-We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
34		-
35	35	== **Feedback Items** ==
	30	+//__Event streaming logging__//
	31	+Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs.
36	36
37		-//__Alerting manual pause__//
38		-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.
	33	+//__Root Cloud__//
	34	+Options and screens related to the deprecated cloud option 'Root' have been removed from the portal.
39	39
40		-//__Ordering of graphs in Manage__//
41		-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).
42		-
43		-//__UTC times in Grafana panels__//
44		-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.
45		-
46		-//__Update flow designer version__//
47		-The framework used in the flow designer has been updated to the latest version.
48		-
49		-//__Carwash track TLS versions in logging__//
50		-A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
51		-
52		-//__Moving channels in the flow designer__//
53		-Moving already attached channels in the flow designer has been made sligthly easier.
54		-
55		-//__Topic sizes description change__//
56		-In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
57		-
58		-//__Password change notification__//
59		-When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
60		-
61		-//__Password comparison__//
62		-When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
63		-
64		-
65		-== **Bug Fixes** ==
66		-
67		-//__Flow designer styling__//
68		-The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
69		-
70	70	== **Fancy Forum Answers** ==
71	71
72	72	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:
73	73
74		-* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
	40	+* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]]
	41	+* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]]
	42	+* [[Requesting Azure token not working because of form-data structure>>https://my.emagiz.com/p/question/172825635703799013||target="blank"]]
	43	+* [[PGP Signing and Encryption>>https://my.emagiz.com/p/question/172825635703799061||target="blank"]]
75	75
76		-== **Key takeaways** ==
	45	+== **Key Takeaways** ==
77	77
78	78	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:
79	79
...	...	@@ -84,7 +84,6 @@
84	84	* Check out the release notes [here]
85	85	* Start thinking about how the license tracker can aid your development
86	86	* Start thinking about major, minor, and patch
87		-* Upgrade to the latest build number
88	88	* Keep making great integrations
89	89
90	90	Let's stay in touch and till next time!
...	...	@@ -92,6 +92,11 @@
92	92	{{info}}
93	93	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
94	94
95		-~*~* Indicates a next-generation-architecture only feature.
96		-{{/info}})))((({{toc/}}))){{/container}}
	63	+{{/info}}
	64	+)))
	65	+
	66	+(((
	67	+{{toc/}}
	68	+)))
97	97	{{/container}}
	70	+{{/container}}