Changes for page 224 - Summer Sonata
Last modified by Danniar Firdausy on 2024/07/04 10:01
From version 445.1
edited by Carlijn Kokkeler
on 2024/04/08 12:53
on 2024/04/08 12:53
Change comment:
There is no comment for this version
To version 332.1
edited by Carlijn Kokkeler
on 2024/01/03 10:01
on 2024/01/03 10:01
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -21 8-SprightlySpring1 +211 - Log Luminary - Content
-
... ... @@ -3,46 +3,71 @@ 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 - == **Spring 6 Migration** ==10 - As announcedin our previousreleaseblogs,wewillreleasea major versionfour [[current runtime>>doc:Main.eMagizAcademy.Fundamentals.fundamental-runtime-generation3||target="blank"]]baseimagefor all ourclientsrunningonthe[[currentruntime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]architecture in our release that willbereleasedonApril 11th, 2024, which is this release.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 11 12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6: 13 -* JDBC BoneCP data source 14 -* SSL web service message sender 15 -* Web service outbound gateway 16 -* SFTP session factory 17 -* HTTP components message sender 18 -* Job manager 19 -* Credentials 20 -* Simple job launcher 21 -* Default SFTP session factory 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. 22 22 23 - Legacyconfigurations that contain SSL web servicemessagesender components are also updated with a non runtime affecting change.18 +== **Overviews** == 24 24 25 -In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration.WebHome||target="blank"]]. 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. 26 26 27 - This largemaintenance update, movingtheeMagiz runtime stack from Spring5 to Spring 6 and from Java 8 to Java 17, includesmoving to latest (major) versions of open source projects, libraries and technologies.For this, a new [[runtime image>>doc:Main.ReleaseInformation.Runtime Images.WebHome||target="blank"]] will bereleased. Although no new functionality is added in this new imageversion, several Spring libraries have been changed significantly. Moreinformation can be found [[here>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V3.0.0/||target="blank"]].23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 28 28 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 + 29 29 == **Feedback Items** == 30 -//__Event streaming logging__// 31 -Event streaming processors will produce significantly less logging, so the logs are not cluttered with irrelevant info logs. 32 32 33 -//__ RootCloud__//34 - Optionsandscreens related to thedeprecatedcloud option 'Root'havebeenremoved fromtheportal.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'. 35 35 40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.png]] 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. 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 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 + 36 36 == **Fancy Forum Answers** == 37 37 38 38 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: 39 39 40 -* [[Model Dashboard - Manage - color explanation>>https://my.emagiz.com/p/question/172825635703786144||target="blank"]] 41 -* [[Error handling within XSLT extension gateway>>https://my.emagiz.com/p/question/172825635700354385||target="blank"]] 67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 42 42 69 +== **Key takeaways** == 43 43 44 -== **Key Takeaways** == 45 - 46 46 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: 47 47 48 48 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]