Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.44
edited by dfirdausy
on 2024/07/02 12:10
on 2024/07/02 12:10
Change comment:
There is no comment for this version
To version 92.1
edited by Erik Bakker
on 2023/03/14 08:25
on 2023/03/14 08:25
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - 224 -SummerSonata1 +194 - Big Leap - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,84 +1,79 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}} 3 -((( 2 +{{container layoutStyle="columns"}}((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In th is release, we arebringingasignificantperformance improvementtoflowtesting,with execution timesnowacceleratedby up to3times.Nextto that,overthepast week,we focusedonimprovingtheusabilityof ourplatformandaddressingcommunityfeedback.Specifically,weenhanced userinterface elementson severalpages,includingthedescriptionsofhelptexts, externallinkswithin helptexts,andtheoveralllayout ofhelptext pages. Additionally,wemadeimprovementstoseveralpop-up pages.Wealsomade the userinterface moreuser-friendly for debuggingintegrationflows.Lastly, weresolvedanissueforsomemodelswhencreatinganEventProcessor.5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements. 7 7 8 -== ** FasterFlow Testing** ==7 +== **3rd generation improvements** == 9 9 10 -We are rolling out a major upgrade to flow testing performance, boosting execution speeds by up to three times. This enhancement will greatly accelerate your workflow when developing integrations, enabling you to run tests faster and more efficiently. Consequently, this will further support users for delivering higher-quality integrations. 9 +//__Better feedback in error log when a corrupt stylesheet is encountered__// 10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action. 11 11 12 -== **Feedback Items** == 13 -//__Retention duration and bytes in Capture__// 14 -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 +//__Better internal error handling to avoid unnecessary alerting and notifications__// 13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack. 15 15 16 -//__ Helptextpanelin Capture__//17 - Collapsing thehelptextof thispop-uppageby clickingthe"?" icon onthetoprightcornerofthepop-uppagewillnowcorrectly hidethe helptextpane.15 +//__Improved Manage Dashboard__// 16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture. 18 18 19 -//__ Adding tagsinCapture__//20 - In theCapturephase,clickingto addorremovea tagin thepop-uppagefor specifyingintegrationrequirements nolongerdisplaysa'blocked'icon.18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__// 19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes. 21 21 22 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 23 - 24 -//__Property value page__// 25 -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. 21 +//__Improved process of deploy preparation__// 22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 24 +//__Improved migration of Streaming container__// 25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention. 28 28 29 -//__ Improved text inDesign architecture__//30 - Wefixedsomespellingmistakesinthepop-up pagewhenapplyingto environmentinDesign architecture.27 +//__Add History to Notifications in Manage__// 28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications. 31 31 32 -//__ Adding attributes fora messagedefinition__//33 - Wefixedanissuewhereyour selectedattributes werelostwhennavigatingbetweenpaginationswhile addingmoreattributestotheentityinthe pop-up shownwhenyoupressthe'Add Attribute' buttonontherightpanel ofyourSystemMessage,CDM, API DataModel, orEventStreamingDataModel.30 +//__Improved Manage phase for Event Streaming__// 31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you. 34 34 35 -//__ Helptext forHTTP methods__//36 -W eimprovedthehelptextfor theHTTPmethod fieldintheHTTP outbound gateway and HTTP outbound channeladapter flow componentstoprovideclearer descriptionsfor different HTTP methods.Additionally, we implementedavalidationfor these componentstopreventselectingtheHTTPmethod 'PATCH'if anApache HttpComponentsREST template isnotprovided.33 +//__Improved help text for network volumes__// 34 +With this release we have improved the help text that explains network volumes and how to use them within our solution. 37 37 38 -//__External links__// 39 -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. 40 - 41 -//__Enumeration values__// 42 -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. 36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}} 43 43 44 -//__Debugging Shortcut__// 45 -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. 38 +== **Feedback items ** == 46 46 47 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 40 +//__Generation of security logic API Gateway in case of API Key as security method is improved__// 41 +With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism. 48 48 49 -[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] 43 +//__User Roles are sorted alphabetically__// 44 +All user roles under User Management are now also sorted alphabetically. 50 50 51 -//__ TestMessage fromManage-Explore__//52 - Additionally,we haveimprovedthe names anddescriptionsoftestmessagesthatyousavedwhendebuggingand wiretappingyourintegrationin theManage-Exploresection.46 +//__Name of keystore for user management now includes the environment__// 47 +To improve the naming of downloaded keystore that need to be distributed to external parties we have added the name of the environment to the filename. This way you can make a distinction between the various environments by looking at the filename. 53 53 54 - [[image:Main.Images.ReleaseBlog.WebHome@release-224-test-message-debug-title-description.png]]49 +== **Bug fixes ** == 55 55 56 -//__ Password property__//57 - IntheFlow designerwithintheCreatephase,copyingpasswordpropertiesnowcopies the actualpasswordvalueinsteadoftheencodedvalue.51 +//__Consolidated upgrade process cloud template__// 52 +With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was actually happening in the cloud. 58 58 59 -== **Bug Fixes** == 54 +//__Ensure users can deploy release on environments they have edit rights on__// 55 +As of now users with only limited rights in Deploy, for example, only edit rights in Test can now activate and deploy releases that are ready for other environments but need to be deployed on the environment for which they have the rights to do so. 60 60 61 -//__Event Processor Keystore and Trustore__// 62 - 63 -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. 64 - 65 65 == **Fancy Forum Answers** == 66 66 67 67 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: 68 68 69 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]] 61 +* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]] 62 +* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]] 63 +* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]] 70 70 71 -== **Key Takeaways** ==65 +== **Key takeaways** == 72 72 73 -Thanks to all whohelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:67 +Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you: 74 74 75 75 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 76 76 * If you have feedback or ideas for us, talk to the Platypus 77 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 71 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 78 78 * Clear your browser cache (Ctrl + Shift + Del) 79 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]73 +* Check out the release notes [here] 80 80 * Start thinking about how the license tracker can aid your development 81 81 * Start thinking about major, minor, and patch 76 +* Upgrade to the latest build number 82 82 * Keep making great integrations 83 83 84 84 Let's stay in touch and till next time! ... ... @@ -86,11 +86,6 @@ 86 86 {{info}} 87 87 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 88 88 89 -{{/info}} 90 -))) 91 - 92 -((( 93 -{{toc/}} 94 -))) 84 +~*~* Indicates a GEN3-only feature. 85 +{{/info}})))((({{toc/}}))){{/container}} 95 95 {{/container}} 96 -{{/container}}