Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 186.1
edited by Carlijn Kokkeler
on 2023/10/23 14:44
Change comment: There is no comment for this version
To version 283.1
edited by Carlijn Kokkeler
on 2023/12/04 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +210 - Deployment Delights
Content
... ... @@ -1,94 +1,57 @@
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!** 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.
6 +**Hi there, eMagiz developers!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we have made some changes to the alerts that you may be receiving.
6 6  
7 -== **State Generation** ==
8 +== **Alerts** ==
8 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.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ alert has been temporarily disabled due to a high number of false positives.
16 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 -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`.
23 -Added support for `#JsonPath` usage in SpEL expressions
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
24 24  
25 -
26 -== **Metrics Storage Duration** ==
27 -
28 -
29 -
30 -
31 31  == **Feedback Items** ==
32 32  
33 -//__Alerting manual pause__//
34 -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.
18 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
35 35  
36 -//__Ordering of graphs in Manage__//
37 -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).
21 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
38 38  
39 -//__UTC times in Grafana panels__//
40 -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.
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
41 41  
42 -//__Update flow designer version__//
43 -The framework used in the flow designer has been updated, improving performance.
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
44 44  
45 -//__Carwash track TLS versions in logging__//
46 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
29 +== **Bug Fixes** ==
47 47  
48 -//__Moving channels in the flow designer__//
49 -Moving already attached channels in the flow designer has been made sligthly easier.
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
50 50  
51 -//__Topic sizes description change__//
52 -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.
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
53 53  
54 -//__Password change notification__//
55 -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.
37 +//__Store message merging__//
38 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
56 56  
57 -//__Password comparison__//
58 -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.
40 +//__View all store items__//
41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
59 59  
60 -//__Inactive user alerting__//
61 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
62 62  
63 -//__Alphabetical sorting on user level in HTTP statistics__//
64 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
46 +//__Max fetch size__//
47 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
65 65  
66 -
67 -== **Bug Fixes** ==
68 -
69 -//__Flow designer styling__//
70 -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.
71 -
72 -//__Partial search for messages__//
73 -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".
74 -
75 -//__Disk usage after cloud template update__//
76 -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.
77 -
78 -//__Error handling migration__//
79 -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.
80 -
81 81  == **Fancy Forum Answers** ==
82 82  
83 83  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:
84 84  
85 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
86 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
87 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
88 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
89 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
53 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
90 90  
91 -
92 92  == **Key takeaways** ==
93 93  
94 94  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:
... ... @@ -109,5 +109,11 @@
109 109  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
110 110  
111 111  ~*~* Indicates a next-generation-architecture only feature.
112 -{{/info}})))((({{toc/}}))){{/container}}
75 +{{/info}}
76 +)))
77 +
78 +(((
79 +{{toc/}}
80 +)))
113 113  {{/container}}
82 +{{/container}}