Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 333.1
edited by CarlijnKokkeler
on 2024/01/03 10:03
Change comment: There is no comment for this version
To version 604.1
edited by Erik Bakker
on 2024/07/16 14:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -211 - Log Luminary
1 +225 - Pop-up Party
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -3,70 +3,84 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
6 +**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
7 7  
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 +== **Feedback Items** ==
9 +//__Alerting notification settings__//
11 11  
12 -//__Runtime logging__//
13 -We fixed a bug where no new log messages were showing up, even though they were produced by a container.
11 +//__Process containers__//
12 +If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
14 14  
15 -//__Deployment execution error message__//
16 -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.
14 +//__Design settings__//
15 +When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
17 17  
18 -== **Overviews** ==
17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
19 19  
20 -//__Runtime overview__//
21 -We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
19 +//__Untested images__//
20 + A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before.
21 +
22 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
23 +
24 +{{warn}}
25 +The following restrictions apply to this functionality:
26 +
27 +- The warning is
28 +{{/warn}}
22 22  
23 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
30 +//__Infinispan Cache Manager__//
31 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
32 +
33 +//__Infinispan Cache Manager error message__//
34 +We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
24 24  
25 -//__Missing properties overview__//
26 -The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
36 +//__Flow bump__//
37 +When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
38 +
39 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
27 27  
28 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
41 +//__Unused support objects__//
42 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
29 29  
30 -//__Runtime restart or redeploy overview__//
31 -Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
44 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
45 +
46 +//__Deleting routes__//
47 +For clarity purposes, a confirmation pop-up will be shown when deleting routes.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
49 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
34 34  
35 -== **Feedback Items** ==
51 +//__Debug queue__//
52 +The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
53 +
54 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
55 +
56 +== **Bug Fixes** ==
57 +//__Internal server error__//
58 +The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
36 36  
37 -//__Breaking changes pop-up__//
38 -The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
60 +//__Namespace update__//
61 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
63 +//__Error pop-up__//
64 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
41 41  
42 -//__External recipients emailaddress__//
43 -The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
66 +//__SMB inbound channel adapter__//
67 +The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available.
44 44  
45 -//__Broker queue metrics dashboards__//
46 -It is now possible to select the MQTT broker in the queue metrics dashboards.
69 +//__Heap memory__//
70 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
47 47  
48 -//__Runtime image version__//
49 -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.
72 +//__Classpath conflicts__//
73 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
50 50  
51 -
52 -== **Bug Fixes** ==
53 -
54 -//__Message throughput__//
55 -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.
56 -
57 -//__Cloud template upgrade incorrect rollback__//
58 -An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
59 -
60 -//__Next generation block__//
61 -Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
62 -
63 63  == **Fancy Forum Answers** ==
64 64  
65 65  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:
66 66  
67 -* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
79 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
80 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
81 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
68 68  
69 -== **Key takeaways** ==
83 +== **Key Takeaways** ==
70 70  
71 71  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  
... ... @@ -74,7 +74,7 @@
74 74  * If you have feedback or ideas for us, talk to the Platypus
75 75  * 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 -* Check out the release notes [here]
91 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
78 78  * Start thinking about how the license tracker can aid your development
79 79  * Start thinking about major, minor, and patch
80 80  * Keep making great integrations