Changes for page 213 - Joyful Journeys

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-197 - Pay Attention
	1	+207 - Aligned State

Author

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

Content

...	...	@@ -2,67 +2,117 @@
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!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection.
6	6
7		-== **Event streaming alerting** ==
	7	+{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
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	+Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
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.
	11	+== **State Generation~*~*** ==
12	12
13		-The two "dynamic" alerts we have added mimic the alerting on the queue level we already offer to the community.
	13	+//__New components__//
	14	+The following components have been added:
	15	+* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
	16	+* Infinispan metadata outbound channel adapter: used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
	17	+* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
	18	+* Duplicate detector: support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
	19	+* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
14	14
15		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--new-alerting-options.png]]
	21	+//__SpEL functions & JSON__//
	22	+Added SpEL functions for:
	23	+* Encoding & decoding Base64, Hex and hmac.
	24	+* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
	25	+* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
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.
	27	+Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
18	18
19		-[[image:Main.Images.Release Blog.WebHome@197-release-blog--alert-config-example.png]]
	29	+Added support for `#JsonPath` usage in SpEL expressions.
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	+{{info}}The components are all configurable from the Flow Designer in Create and are accompanied by help text explaining the use cases and the various technical configurations. Note that to make the components work in your model, a new release containing the latest image (2.0.0) needs to be deployed.{{/info}}
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"]].
	33	+== **Metrics Storage Duration** ==
	34	+We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 7, 14 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively.
24	24
25		-== **3rd generation improvements** ==
	36	+[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]]
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.
	38	+== **Feedback Items** ==
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.
	40	+//__Import from store__//
	41	+The button 'Import from Store' in Design will directly open the store instead of showing a pop asking whether the store should be opened.
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.
	43	+//__Save and cancel buttons placement__//
	44	+The save and cancel buttons have been placed slightly further apart from each other to avoid misclicking.
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.
	46	+//__User session times__//
	47	+The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour.
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.
	49	+//__Cancel and next buttons order__//
	50	+The order of the cancel and next buttons when creating a new trigger has been changed to increase alignment across the platform. Now, all cancel buttons are placed on the right of a 'next' or 'save' button.
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}}
	52	+//__Data sink page__//
	53	+The data sink page has been moved to the “Explore” tab.
43	43
44		-== **Feedback items ** ==
	55	+//__Unused images removal__//
	56	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
45	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.
	58	+//__Flow Designer performance__//
	59	+Performance improvements for the Flow Designer have been implemented.
48	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.
	61	+//__Properties with special characters__//
	62	+When a user would migrate to gen3 and deploy their release containing properties with special characters, certain flows could not find the correct values to properties anymore or could not find the properties altogether. With this release, special characters such as a backslash do not break properties after deployment.
51	51
	64	+//__Hidden flow fragements__//
	65	+When importing items from the store, flow fragments that are hidden in design will be listed under the versions in create.
	66	+
	67	+//__Resources disappearances__//
	68	+Resources would disappear in the flow designer when pressing Cancel on selecting a new resource. With this release, resources without a name will not trigger error messages when users select components.
	69	+
	70	+//__Error channel for all inbounds__//
	71	+If there is no custom error handling, Gen3 migration would set the error channel to “errorChannel” only for the first inbound in an entry flow.
	72	+We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
	73	+
	74	+//__Highlighting resources__//
	75	+The performance of highlighting resources of selected components is improved in Read only mode.
	76	+
	77	+== **Bug Fixes** ==
	78	+
	79	+//__Topic and event-processor names__//
	80	+The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
	81	+
	82	+//__System alignment__//
	83	+The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. So, systems are aligned regarding positioning across all phases.
	84	+
	85	+//__Error checking__//
	86	+Besides checking error header, the error trigger is now configured to check if an error message contains a term.
	87	+
	88	+//__Alerting__//
	89	+For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%.
	90	+For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of configured size used to 110%.
	91	+The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
	92	+
	93	+//__Unused containers__//
	94	+Containers are set inactive when they are unused and removed in Design.
	95	+
	96	+//__Error popups when promoting a release version__//
	97	+We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment.
	98	+
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"]]
	103	+* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
	104	+* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
	105	+* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
	106	+* [[3rd generation runtime with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
58	58
	108	+
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:
	111	+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.
	115	+* 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.
	128	+~*~* Indicates a next-generation-architecture only feature.
79	79	{{/info}})))((({{toc/}}))){{/container}}
80	80	{{/container}}