Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 24-Summer Sonata1 +211 - Log Luminary - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -3,73 +3,70 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** Overthe pastweek, wefocusedon improving theusabilityof ourplatform and addressingcommunity feedback. Specifically, we enhanceduserinterface elementsonseveralpages, includingthe descriptions of helptexts,external links within help texts, and the overalllayoutofhelp textpages.Additionally, wemadeimprovementstoseveralpop-uppages.Wealso madetheuserinterfacemore user-friendlyfordebuggingintegrationflows. Lastly, weresolvedanissue for some modelswhen creatingan EventProcessor.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 -== **Rapid Flow Testing** == 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. 9 9 10 -== **Feedback Items** == 11 -//__Retention duration and bytes in Capture__// 12 -The pop-up page for specifying integration requirements in the Capture phase now correctly asks for the required retention duration and bytes for the integration/topic, instead of the previously incorrect terms retention size and bytes. 12 +//__Runtime logging__// 13 +We fixed a bug where no new log messages were showing up, even though they were produced by a container. 13 13 14 -//__ HelptextpanelinCapture__//15 - Collapsingthehelptext ofthispop-uppagebyclicking the"?"icon on thetoprightcornerofthe pop-uppagewillnowcorrectlyhidethe helptextpane.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. 16 16 17 -//__Adding tags in Capture__// 18 -In the Capture phase, clicking to add or remove a tag in the pop-up page for specifying integration requirements no longer displays a 'blocked' icon. 18 +== **Overviews** == 19 19 20 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 21 - 22 -//__Property value page__// 23 -Pop-up pages with non-editable input fields containing long text are now displaying the entire content without any text being cut off at the edge of the page. 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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release- 224-pop-ups-wrapped-property-values.png]]23 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-runtime-overview.png]] 26 26 27 -//__ Improvedtextin Designarchitecture__//28 - Wefixedsomespellingmistakes inthepop-uppage when applyingtoenvironmentinDesignarchitecture.25 +//__Missing properties overview__// 26 +The missing properties overview has been updated to show the runtimes and flow versions of missing property values. 29 29 30 -//__Adding attributes for a message definition__// 31 -We fixed an issue where your selected attributes were lost when navigating between paginations while adding more attributes to the entity in the pop-up shown when you press the 'Add Attribute' button on the right panel of your System Message, CDM, API Data Model, or Event Streaming Data Model. 28 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-missing-properties-overview.png]] 32 32 33 -//__ HelptextforHTTP methods__//34 - Weimproved the help textfortheHTTP method field in theHTTP outboundgateway andHTTP outboundchannel adapter flowcomponentsto provide clearerdescriptionsfor differentHTTP methods. Additionally,weimplementedavalidationforthesecomponents to prevent selecting theHTTP method'PATCH' if anApache HttpComponentsREST template is not provided.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. 35 35 36 -//__External links__// 37 -Clicking links to external documentation in the eMagiz portal is now configured to always open the links in a new tab, rather than replacing your current tab. 38 - 39 -//__Enumeration values__// 40 -When editing a message definition (i.e., a System Message, CDM, API Data Model, or Event Streaming Data Model) in the Create phase, users can add enumeration values for attributes with an Enumeration data type. In this release, we’ve added a "Save and Add New" button to streamline the process of adding multiple enumeration values. 33 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-restarted-redeployed-runtimes.jpg]] 41 41 42 -//__Debugging Shortcut__// 43 -Debugging a flow typically requires users to activate debug on a specific flow in Deploy → Containers, then navigate to Manage → Explore → Queue Browser and manually type in emagiz.debug. In this release, we have added a shortcut button that opens the Queue Browser page directly in the pop-up page right after activating debugging. Next to that, the Queue Browser page now includes a button to directly open the debugging queue, eliminating the need to manually type in emagiz.debug in the search box. 35 +== **Feedback Items** == 44 44 45 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 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'. 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-2 24-open-debug-queue-button.png]]40 +[[image:Main.Images.Release Blog.WebHome@release-blog-211-breaking-changes.jpg]] 48 48 49 -//__ TestMessage from Manage-Explore__//50 - Additionally,we haveimproved thenames and descriptions of test messages that yousaved whendebuggingandwiretappingyour integrationintheManage - Exploresection.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. 51 51 52 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 45 +//__Broker queue metrics dashboards__// 46 +It is now possible to select the MQTT broker in the queue metrics dashboards. 53 53 54 -//__ Passwordproperty__//55 - In theFlow designerwithintheCreatephase,copying passwordpropertiesnowcopiesthe actualpasswordvalueinsteadof the encodedvalue.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. 56 56 51 + 57 57 == **Bug Fixes** == 58 58 59 -//__Event Processor Keystore and Trustore__// 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. 60 60 61 -We fixed an issue where the keystore location and the truststore location were generated incorrectly when creating a new event processor for models that were migrated from the legacy runtime architecture to the current generation architecture. 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. 62 62 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 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 68 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 69 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 70 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 67 +* [[Save header as class 'long'>>https://my.emagiz.com/p/question/172825635703683851||target="blank"]] 71 71 72 -== **Key Takeaways** ==69 +== **Key takeaways** == 73 73 74 74 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: 75 75 ... ... @@ -77,9 +77,10 @@ 77 77 * If you have feedback or ideas for us, talk to the Platypus 78 78 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 79 79 * Clear your browser cache (Ctrl + Shift + Del) 80 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]77 +* Check out the release notes [here] 81 81 * Start thinking about how the license tracker can aid your development 82 82 * Start thinking about major, minor, and patch 80 +* Upgrade to the latest build number 83 83 * Keep making great integrations 84 84 85 85 Let's stay in touch and till next time! ... ... @@ -87,6 +87,7 @@ 87 87 {{info}} 88 88 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 89 89 88 +~*~* Indicates a next-generation-architecture only feature. 90 90 {{/info}} 91 91 ))) 92 92