Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.39
edited by dfirdausy
on 2024/07/02 11:50
on 2024/07/02 11:50
Change comment:
There is no comment for this version
To version 89.1
edited by Erik Bakker
on 2023/03/14 06:50
on 2023/03/14 06:50
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,85 +1,92 @@ 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!** Overthepast week, wefocusedon improvingtheusabilityofourplatformand addressingcommunityfeedback. Specifically,we enhanceduserinterfaceelementson several pages,including thedescriptionsofhelp texts,externallinkswithinhelptexts,andthe overalllayoutof helptextpages. Additionally,wemade improvementsto severalpop-up pages.We alsomade theuser interfacemoreuser-friendlyfordebuggingintegrationflows. Lastly, we resolvedanissueforsomemodelswhencreatinganEventProcessor.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 -== ** RapidFlow Testing** ==7 +== **3rd generation improvements** == 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. 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. 13 13 14 -//__ Helptextpanel inCapture__//15 - Collapsingthehelptextofthis pop-up page by clickingthe"?"icononthe toprightcornerofthepop-uppage willnow correctlyhidethehelptextpane.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. 16 16 17 -//__ Addingtagsin Capture__//18 - In theCapturephase,clicking to add or remove atagin thepop-up pageforspecifyingintegration requirementsnolongerdisplaysa'blocked'icon.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. 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. 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. 24 24 25 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 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 -//__Improved t extinDesignarchitecture__//28 -We fixedsomespellingmistakesin thepop-uppage whenapplyingtoenvironmentinDesign architecture.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. 29 29 30 -//__Add ingattributesforamessage definition__//31 - Wefixedan issue whereyourselectedattributeswerelost when navigatingbetweenpaginationswhileaddingmoreattributestotheentityin thepop-upshownwhenyou pressthe'Add Attribute' buttonon therightpanel of your SystemMessage,CDM,API Data Model,orEventStreamingDataModel.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. 32 32 33 -//__ HelptextforHTTP methods__//34 - Weimprovedthehelp textforthe HTTP methodfieldintheHTTP outboundgatewayand HTTP outbound channeladapterflowcomponentsto provideclearer descriptionsfor differentHTTP methods. Additionally, we implementedavalidation forthesecomponents topreventselectingtheHTTPmethod'PATCH'if anApacheHttpComponentsRESTtemplate isnotprovided.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. 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 +//__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. 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. 44 44 45 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 46 46 47 - [[image:Main.Images.ReleaseBlog.WebHome@release-224-open-debug-queue-button.png]]38 +{{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.WebHome||target="blank"]] on the subject.{{/warning}} 48 48 49 -//__Test Message from Manage-Explore__// 50 -Additionally, we have improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section. 40 +== **WS-Security on the 3rd generation runtime** ~*~* == 51 51 52 - [[image:Main.Images.ReleaseBlog.WebHome@release-224-test-message-debug-title-description.png]]42 +To further improve our offering on the 3rd generation runtime we now also have added the necessary functionality to allow you to call SOAP endpoints while utilizing WS-Security as well as securing your hosted SOAP endpoint through WS-Security protocols. Please make sure to create a new release that will trigger the image creation process which will included this feature when necessary. 53 53 54 -//__Password property__// 55 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 44 +== **State Generation ~*~* == 56 56 57 - ==**BugFixes**==46 +With this release we introduce our first "State Generation" functionality to our user community. After rigorous internal testing and use we have now made a stride to also make it available to the user community on specific use case. In the following months we will gather feedback on this to further improve and release it in a simpler and more user friendly way to the user community. 58 58 59 - //__EventProcessorKeystore andTrustore__//48 +{{info}}Should you be interested in this functionality or want to learn more please contact us at productmanagement@emagiz.com{{/info}} 60 60 61 - Wefixed an issuewhere the keystore location andthe truststore location were generated incorrectlywhen creating a new eventprocessor formodelsthatwere migrated from the legacy runtime architecture to the current generation architecture.50 +== **Feedback items ** == 62 62 52 +//__Removed OData as option for an API Gateway operation__// 53 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform. 54 + 55 +//__Changes in API Gateway operation paths is automatically updated in Create__// 56 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry. 57 + 58 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}} 59 + 60 +== **Bug fixes ** == 61 + 62 +//__Prevent endless loop in Deploy -> User Management__// 63 +With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion. 64 + 65 +{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}} 66 + 67 +//__Update error handling during migration to the 3rd generation runtime__// 68 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration. 69 + 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"]] 74 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]] 75 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]] 76 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]] 71 71 72 -== **Key Takeaways** ==78 +== **Key takeaways** == 73 73 74 -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:80 +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: 75 75 76 76 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 77 77 * If you have feedback or ideas for us, talk to the Platypus 78 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 84 +* 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"]]86 +* 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 89 +* 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,11 +87,6 @@ 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 90 -{{/info}} 91 -))) 92 - 93 -((( 94 -{{toc/}} 95 -))) 97 +~*~* Indicates a GEN3-only feature. 98 +{{/info}})))((({{toc/}}))){{/container}} 96 96 {{/container}} 97 -{{/container}}