Skip to Content

Changes for page 213 - Joyful Journeys

Last modified by Carlijn Kokkeler on 2024/04/18 13:07
From version 17.1
edited by eMagiz
on 2022/10/13 09:28
Change comment: There is no comment for this version
To version 323.1
edited by Carlijn Kokkeler
on 2023/12/21 15:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -185 - Get ready
1 +211 - Log Luminary
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.eMagiz
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,51 +1,83 @@
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 been hard at work bolstering our offering concerning the upcoming rollout of our new architecture stack. Next to that, we have made several small updates as this release contained a complete revamp of the Manage phase. Please take a moment to read the below carefully and work with the new flow designer as soon as possible to familiarize yourself with this one.
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 6  
7 -==**Audit trail User Management**==
8 -Since the introduction of the API Gateway and Event Streaming patterns in eMagiz, the notion of users and roles have been added to the platform. In the User Management section in Deploy you will find the overview of the users and roles configured in your model. With this release we have also added the history tab to this page in which the platform registers the changes made in Users & Roles. At the moment when the user presses the Apply to environment button, the changes between the previous history entry and this action are registered in this section. The popup that is displayed when pressing Apply to environment has been expanded with the list of entries that will be added to this History section.
9 -
10 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 1.png]]
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.
11 11  
12 -==**Next Generation Monitoring & Alerting engine**==
13 -In the recent sprints, we have completed our alerting & monitoring engine for our new runtime architecture. Effectively that means that we are now using State Generation components inside this architecture, and all error messages, runtime metrics and logging are now passing through this engine. All of our regular Manage phase screens have been updated to point to the new storage locations.
14 -
15 -* In the Manage phase we have introduced proper means to toggle between data of the current and the new monitoring stack (transition to the new runtime can be a runtime by runtime approach).
16 -* We have also released and described the new Manage phase graphs in [[Release blog 183>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Release%20Blogs/Rainbow%20World||target="blank"]].
17 -* In the new architecture all error messages are automatically send to the eMagiz monitoring & alerting stack, which means that these flow components are no longer required. During migration these will be removed. In case custom error handling is required, these components are made available in the Create Store and will point to the current error flow (which serves a new purpose from then onwards)
18 -* Hosted SOAP Webservices can be migrated to the new architecture which removes the need to use the Jetty component, and introduces the request layer as root element in the System Message. This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well.
19 -* The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms
20 -
21 -
22 -=== **Improvements** ===
23 -
24 -* Performance Deployment plan
25 -When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU. This has been improved with this release.
26 -
27 -* Flow Designer updates
28 -We have added an icon to identify a Queued channel which are mostly found in entry flows that use the h2 bridge. Furthermore, the display of wiretaps and annotations can be copied now. Next to that some small UI improvements where made.
29 -
30 -[[image:Main.Images.Release Blog.WebHome@185 - Release blog 2.png]]
31 -
32 -* Store
33 -We have fixed several smaller Store import issues to improve the user experience.
34 -
12 +//__Runtime logging__//
13 +We fixed a bug where no new log messages were showing up, even though they were produced by the container.
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.
17 +
18 +== **Overviews** ==
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 in an overview.
22 +
23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]]
24 +
25 +//__Missing properties overview__//
26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
27 +
28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]]
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.
32 +
33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]]
34 +
35 +== **Feedback Items** ==
36 +
37 +//__Breaking changes pop-up__//
38 +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'.
39 +
40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]]
41 +
42 +//__External recipients emailaddress__//
43 +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.
44 +
45 +//__Broker queue metrics dashboards__//
46 +It is now possible to select the MQTT broker in the queue metrics dashboards.
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.
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 unjust rollback__//
58 +An issue has been fixed where a cloud template upgrade would be rolled back unjustly 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 +
35 35  == **Fancy Forum Answers** ==
36 36  
37 -As always, a gentle reminder to all 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:
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:
38 38  
39 -* [[Start runtime via a delayed start in a Linux environment?>>https://my.emagiz.com/p/question/172825635703146181||target="blank"]]
40 -* [[Failed to create sFTP session: Het systeem kan het opgegeven pad niet vinden>>https://my.emagiz.com/p/question/172825635703146327||target="blank"]]
67 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
68 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
69 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
70 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
71 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
41 41  
73 +
42 42  == **Key takeaways** ==
43 43  
44 -Thanks to all that help build, those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
76 +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:
45 45  
46 46  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
47 47  * If you have feedback or ideas for us, talk to the Platypus
48 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 49  * Clear your browser cache (Ctrl + Shift + Del)
50 50  * Check out the release notes [here]
51 51  * Start thinking about how the license tracker can aid your development
... ... @@ -52,13 +52,18 @@
52 52  * Start thinking about major, minor, and patch
53 53  * Upgrade to the latest build number
54 54  * Keep making great integrations
55 -* Check out the new documentation portal.
56 56  
57 57  Let's stay in touch and till next time!
58 58  
59 59  {{info}}
60 -~* Indicates a Beta feature. If you would like to get access to this beta feature please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
91 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
62 -~*~* Indicates a GEN3-only feature.
63 -{{/info}})))((({{toc/}}))){{/container}}
93 +~*~* Indicates a next-generation-architecture only feature.
94 +{{/info}}
95 +)))
96 +
97 +(((
98 +{{toc/}}
99 +)))
64 64  {{/container}}
101 +{{/container}}