Skip to Content

Changes for page 212 - Failover Fiesta

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 282.1
edited by Carlijn Kokkeler
on 2023/12/04 15:08
Change comment: There is no comment for this version
To version 302.1
edited by Carlijn Kokkeler
on 2023/12/21 13:36
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -210 - Deployment Delights
1 +211 - Log Luminary
Content
... ... @@ -3,57 +3,55 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** We have...
6 +**Hi there, eMagiz developers!**
7 7  
8 -== **Alerts** ==
8 +== **TBD** ==
9 9  
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.
12 12  
13 -//__Missing metrics alert__//
14 -We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 15  
16 16  == **Feedback Items** ==
17 17  
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.
14 +//__Runtime overview__//
15 +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.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
17 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
22 22  
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.
19 +//__Missing properties overview__//
20 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
25 25  
26 -//__Rebuilding of images__//
27 -Changing the list of flows that should run on a container will now trigger the rebuilding of images.
22 +//__Breaking changes pop-up__//
23 +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'.
28 28  
25 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
29 29  
27 +//__Broker queue metrics dashboards__//
28 +It is now possible to select the MQTT broker in the queue metrics dashboards.
29 +
30 30  == **Bug Fixes** ==
31 31  
32 -//__Runtime metrics processing__//
33 -The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
32 +//__Deployment execution error message__//
33 +In some cases when a machine type step in your deployment execution has an error and the portal tries to display this error message, it may give an error in the portal. This case has been fixed by now showing a generic error in the deployment plan and logging the full error to the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new popup.
34 34  
35 -//__Deployment plan__//
36 -We solved a bug where a deployment step in the deployment plan could randomly get stuck.
35 +//__Cloud template upgrade unjust rollback__//
36 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly due to failed runtime checks on gen3.
37 37  
38 -//__Store message merging__//
39 -The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
38 +//__Missing log entries__//
39 +We improved crash handling so that log messages clearly show when and why a container failed to start.
40 40  
41 -//__View all store items__//
42 -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.
41 +//__Runtime logging__//
42 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
43 43  
44 -//__Out of memory behavior__//
45 -We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
46 -
47 -//__Max fetch size__//
48 -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.
49 -
50 -
51 51  == **Fancy Forum Answers** ==
52 52  
53 53  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:
54 54  
55 -* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
48 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
49 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
50 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
51 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
52 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
56 56  
54 +
57 57  == **Key takeaways** ==
58 58  
59 59  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: