Skip to Content

Changes for page 226 - Alerting Alchemy

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

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -225 - TBD
1 +211 - Log Luminary
Content
... ... @@ -3,67 +3,70 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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.
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 8  
9 -== **Feedback Items** ==
10 -//__Alerting notification settings__//
11 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature.
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by a container.
12 12  
13 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]]
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 14  
15 -//__Process containers__//
16 -If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern.
18 +== **Overviews** ==
17 17  
18 -//__Design settings__//
19 -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.
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.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
22 22  
23 -//__Untested images__//
24 - 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.
25 -
26 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
25 +//__Missing properties overview__//
26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
27 27  
28 -//__Infinispan Cache Manager__//
29 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
30 -
31 -//__Infinispan Cache Manager error message__//
32 -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.
28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
33 33  
34 -//__Flow bump__//
35 -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.
36 -
37 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
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.
38 38  
39 -//__Unused support objects__//
40 -Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
41 41  
42 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
43 -
44 -//__Deleting routes__//
45 -For clarity purposes, a confirmation pop-up will be shown when deleting routes.
35 +== **Feedback Items** ==
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
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.
48 48  
49 -//__Debug queue__//
50 -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.
51 -
52 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
53 -
54 -== **Bug Fixes** ==
40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]]
55 55  
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.
56 56  
45 +//__Broker queue metrics dashboards__//
46 +It is now possible to select the MQTT broker in the queue metrics dashboards.
57 57  
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.
58 58  
59 59  
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 +
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]]
65 65  
66 -== **Key Takeaways** ==
69 +== **Key takeaways** ==
67 67  
68 68  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:
69 69  
... ... @@ -71,7 +71,7 @@
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 72  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
77 +* Check out the release notes [here]
75 75  * Start thinking about how the license tracker can aid your development
76 76  * Start thinking about major, minor, and patch
77 77  * Keep making great integrations