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 319.1
edited by Carlijn Kokkeler
on 2023/12/21 14:50
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +211 - Log Luminary
Content
... ... @@ -1,92 +1,75 @@
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!**
6 6  
7 -== **State Generation** ==
8 +== **Logging** ==
9 +//__Missing log entries__//
10 +We improved crash handling so that log messages clearly show when and why a container failed to start.
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.
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
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
15 +== **Overviews** ==
16 +//__Runtime overview__//
17 +We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines in an overview.
24 24  
19 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
25 25  
26 -== **Metrics Storage Duration** ==
27 -
28 -
29 -
21 +//__Missing properties overview__//
22 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
30 30  
31 -== **Feedback Items** ==
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
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.
26 +//__Runtime restart or redeploy overview__//
27 +Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
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).
29 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
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.
41 41  
42 -//__Update flow designer version__//
43 -The framework used in the flow designer has been updated, improving performance.
32 +== **Feedback Items** ==
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.
47 47  
48 -//__Moving channels in the flow designer__//
49 -Moving already attached channels in the flow designer has been made sligthly easier.
35 +//__Breaking changes pop-up__//
36 +Pending changes that have a high risk level are now shown in red bold in the pop up that appears after clicking 'Apply to environment'.
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.
38 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
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.
40 +//__External recipients emailaddress__//
41 +The overview of external recipients has been updated. External recipients are created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
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.
43 +//__Broker queue metrics dashboards__//
44 +It is now possible to select the MQTT broker in the queue metrics dashboards.
59 59  
60 -//__Inactive user alerting__//
61 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
46 +//__Runtime image version__//
47 +The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
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.
65 65  
66 -
67 67  == **Bug Fixes** ==
68 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.
52 +//__Message throughput__//
53 +The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
71 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".
55 +//__Cloud template upgrade unjust rollback__//
56 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks.
74 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.
58 +//__Next generation block__//
59 +Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
77 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.
61 +//__Deployment execution error message__//
62 +In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
80 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"]]
68 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
69 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
70 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
71 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
72 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
90 90  
91 91  
92 92  == **Key takeaways** ==
... ... @@ -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}}
95 +{{/info}}
96 +)))
97 +
98 +(((
99 +{{toc/}}
100 +)))
113 113  {{/container}}
102 +{{/container}}