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,77 +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 work hard on improving our next generation architecture and introduced alerting functionality on top of our event streaming pattern based on user feedback. Furthermore there are several smaller feedback items and bugs that 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		-With this release we expand our alerting functionality into the event streaming pattern. As of now one new "static" alert is introduced for all clients (using event streaming) and two "dynamic" alerts are introduced that you can configure yourself if there is 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 whether messages on it are deleted due to a size or time constraint. In cases where data is deleted becomes the topic was too full way before the messages should have been removed as a result of the retention hours constraint this alert can be seen as an indication 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 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 total 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 message 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@196-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 is more than X number of messages behind on one or more topics. The configuration of this is comparable as 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.WebHome||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		-//__Event Streaming statistics completion__//
28		-In this release, we have updated the retrieval of data to ensure that for all models, all environments and all topics this data can be shown to the user so they can properly monitor the environment.
	38	+== **Feedback Items** ==
29	29
30		-//__Deployments on next generation architecture__//
31		-This release fixes several smaller bugs and adds several improvements to the deployment process of the next generation architecture.
	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		-//__Clean queues option__//
34		-This release introduces an option for **admins** to clean queues that remained after a migration towards the next generation runtime architecture. This will make the overview of which queues are "problematic" a much more realistic overview.
	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		-== **Feedback items ** ==
	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.
37	37
38		-//__On-premise containers are started upon slot wakeup__//
39		-With this release, we have added additional functionality to models running in the next generation runtime architecture. With this improvement all on-premise containers are stopped when the cloud slot goes to sleep and are woken up once the slot is woken up in the morning.
	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.
40	40
41		-//__Resource path is shown to the user__//
42		-You can now, without downloading, see the resource path of a resource by viewing the metadata of the resource. You can do so by pressing the "eye" icon to view this information.
	52	+//__Data sink page__//
	53	+The data sink page has been moved to the “Explore” tab.
43	43
44		-//__Flow designer improvements__//
45		-With this release various improvements have been made to the flow designer. Among others we have improved the overview of what an "unused resource" is. You now have the option to define certain resources that are used but cannot be auto-detected by eMagiz to be an "used" resource to avoid confusion.
	55	+//__Unused images removal__//
	56	+When a release is removed, the related unused images in the on-premises machines will be removed as well.
46	46
47		-//__Improved capabilities of a company contact__//
48		-With this release we have improved the capabilities of a company contact. As of now you can also add users to models belonging to subcompanies below your the company to which you are the company contact.
	58	+//__Flow Designer performance__//
	59	+Performance improvements for the Flow Designer have been implemented.
49	49
50		-== **Bug fixes ** ==
	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
52		-//__Optional API parameters are handled correctly__//
53		-Currently, eMagiz would create the wrong expression for handling optional API parameters. With this release we have improved the expression in such a way that all optional parameters are handled correctly out of the box.
	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.
54	54
55		-//__Without CDM rights nothing related to any data model can be edited anymore__//
56		-With this release, we have made sure that nothing related to any data model can be edited without having the proper rights.
	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.
57	57
58		-//__Improved sorting of Design and Deploy archticture__//
59		-With this release, we now ensure that both Design and Deploy architecture are sorted in the same manner to avoid confusion when quickly switching between both views.
	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.
60	60
	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	+
61	61	== **Fancy Forum Answers** ==
62	62
63	63	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:
64	64
65		-* [[jsonPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
66		-* [[Connecting to Azure SQL>>https://my.emagiz.com/p/question/172825635703415110||target="blank"]]
67		-* [[Changes to JSON api keep breaking my model validation, although they are irrelevant to me>>https://my.emagiz.com/p/question/172825635703415225||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"]]
68	68
	108	+
69	69	== **Key takeaways** ==
70	70
71		-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:
72	72
73	73	* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
74	74	* If you have feedback or ideas for us, talk to the Platypus
75		-* 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.
76	76	* Clear your browser cache (Ctrl + Shift + Del)
77	77	* Check out the release notes [here]
78	78	* Start thinking about how the license tracker can aid your development
...	...	@@ -85,6 +85,6 @@
85	85	{{info}}
86	86	~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
87	87
88		-~*~* Indicates a GEN3-only feature.
	128	+~*~* Indicates a next-generation-architecture only feature.
89	89	{{/info}})))((({{toc/}}))){{/container}}
90	90	{{/container}}