Skip to Content

Changes for page 207 - Aligned State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 188.1
edited by Carlijn Kokkeler
on 2023/10/23 14:45
Change comment: There is no comment for this version
To version 150.1
edited by Erik Bakker
on 2023/08/29 10:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +204 - Found It
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,95 +2,36 @@
2 2  {{container layoutStyle="columns"}}(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
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. State generation functionality is only accessible for models with an add-on state generation license. 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.
5 +**Hi there, eMagiz developers!** We have processed additional feedback on the release properties in the last few weeks. On top of that, we have improved the error handling and manageability of our new generation monitoring stack.
6 6  
7 -== **State Generation** ==
8 -
9 -//__New components__//
10 -The following components have been added:
11 -* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
12 -* Infinispan metadata outbound channel adapter: Used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
13 -* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
14 -* 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.
15 -* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
16 -
17 -//__SpEL functions & JSON__//
18 -Added SpEL functions for:
19 -* Encoding & decoding Base64, Hex and hmac.
20 -* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
21 -* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
22 -
23 -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`.
24 -
25 -Added support for `#JsonPath` usage in SpEL expressions.
26 -
27 -
28 -== **Metrics Storage Duration** ==
29 -
30 -
31 -
32 -
33 33  == **Feedback Items** ==
34 34  
35 -//__Alerting manual pause__//
36 -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.
9 +//__Improved check on nested property placeholders__//
10 +To avoid problems when using nested property placeholders in your configuration, we have added additional checks to identify these nested properties as missing if they are indeed missing.
37 37  
38 -//__Ordering of graphs in Manage__//
39 -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).
12 +//__Removed outdated properties when deploying on the new generation architecture stack__//
13 +We have removed two specific outdated properties from the configuration when deploying on the new generation architecture stack. The properties in question were necessary before in order to connect to a Kafka cluster but have become obsolete once you migrate.
40 40  
41 -//__UTC times in Grafana panels__//
42 -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.
15 +{{warning}}Should you still use the properties called "emagiz.runtime.name" and "emagiz.runtime.environment" **after** successfully migrating the flow in question to the next generation, please get in touch with us before deploying.{{/warning}}
43 43  
44 -//__Update flow designer version__//
45 -The framework used in the flow designer has been updated, improving performance.
17 +//__Improved performance Manage Dashboards__//
18 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
46 46  
47 -//__Carwash track TLS versions in logging__//
48 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
49 -
50 -//__Moving channels in the flow designer__//
51 -Moving already attached channels in the flow designer has been made sligthly easier.
52 -
53 -//__Topic sizes description change__//
54 -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.
55 -
56 -//__Password change notification__//
57 -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.
58 -
59 -//__Password comparison__//
60 -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.
61 -
62 -//__Inactive user alerting__//
63 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
64 -
65 -//__Alphabetical sorting on user level in HTTP statistics__//
66 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
67 -
68 -
69 69  == **Bug Fixes** ==
70 70  
71 -//__Flow designer styling__//
72 -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.
22 +//__Errors with long stack traces or long message histories will now also show in eMagiz__//
23 +We have fixed a bug that could cause an error message to be lost between the flow and the Manage phase of eMagiz. This happened in situations where either the stack trace or the message history was very long. To ensure this new functionality is applied to your flows, create a new release and deploy it to your environment(s).
73 73  
74 -//__Partial search for messages__//
75 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
25 +//__Moving runtimes from on-premise to the cloud will not result in a broken container anymore__//
26 +We have fixed a bug that caused specific runtimes to deploy on-premises but later migrated to the cloud, not to start up. By fixing this bug, you have more flexibility in moving containers around when running in a hybrid configuration.
76 76  
77 -//__Disk usage after cloud template update__//
78 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
79 -
80 -//__Error handling migration__//
81 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
82 -
83 83  == **Fancy Forum Answers** ==
84 84  
85 85  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:
86 86  
87 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
88 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
89 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
90 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
91 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
32 +* [[XSLT Extension Gateway with JSON message>>https://my.emagiz.com/p/question/172825635703543227||target="blank"]]
33 +* [[eMagiz property migration>>https://my.emagiz.com/p/question/172825635703543395||target="blank"]]
92 92  
93 -
94 94  == **Key takeaways** ==
95 95  
96 96  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:
... ... @@ -97,7 +97,7 @@
97 97  
98 98  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
99 99  * If you have feedback or ideas for us, talk to the Platypus
100 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
101 101  * Clear your browser cache (Ctrl + Shift + Del)
102 102  * Check out the release notes [here]
103 103  * Start thinking about how the license tracker can aid your development