Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 574.32
edited by dfirdausy
on 2024/07/01 17:16
on 2024/07/01 17:16
Change comment:
There is no comment for this version
To version 119.1
edited by Erik Bakker
on 2023/06/05 14:27
on 2023/06/05 14:27
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 +199 - Home Improvements - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.ebakker - Content
-
... ... @@ -1,76 +1,58 @@ 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, wefocused on improvingtheusabilityof ourplatformand addressingcommunity feedback.Specifically,weenhanceduserinterfaceelementsonseveralpages,includingthedescriptionsofhelptexts,external links within helptexts,andtheoveralllayout ofhelptext pages. Additionally,wemade improvementstoseveralpop-up pages.We alsomadetheuser interface moreuser-friendlyfor debuggingintegrationflows. Lastly, weresolved anissueforsomemodelswhencreating an EventProcessor.5 +**Hi there, eMagiz developers!** In the last few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern. 7 7 8 -== **Feedback Items** == 9 -//__Retention duration and bytes in Capture__// 10 -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. 7 +== **Next generation improvements and bug fixes** == 11 11 12 -//__ HelptextpanelinCapture__//13 - Collapsing thehelp text of thispop-uppagebyclickingthe"?"icononthetoprightcornerofthepop-uppagewillnowcorrectly hide thehelptextpane.9 +//__Enhanced overview of the HTTP Statistics__// 10 +As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort. 14 14 15 -//__ Addingtags inCapture__//16 -In th eCapturephase,clickingtoadd or removeatagin the pop-uppageforspecifyingintegrationrequirementsnolongerdisplaysa'blocked'icon.12 +//__Reason why runtime cannot start is now in the vast majority of cases reported back__// 13 +In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup. 17 17 18 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 19 - 20 -//__Property value page__// 21 -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. 15 +{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 17 +//__Forced congestion control__// 18 +To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform. 24 24 25 -//__Improved text in Design architecture__// 26 -We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 27 27 28 -//__ Addingattributesfora messagedefinition__//29 - We fixed an issuewhereyour selectedattributeswerelost when navigating between paginationswhileaddingmoreattributes to theentity in the pop-upshown whenyoupressthe 'Add Attribute' button on therightpanelofyourSystem Message,CDM, API DataModel,or EventStreamingDataModel.21 +//__Improved validation errors on the invalid configuration of HTTP outbound components__// 22 +This release fixes and re-introduces the option to execute your actions on the eMagiz per zone or all at once when running in a double-lane Docker setup. 30 30 31 -//__Helptext for HTTP methods__// 32 -We improved the help text for the HTTP method field in the HTTP outbound gateway and HTTP outbound channel adapter flow components to provide clearer descriptions for different HTTP methods. Additionally, we implemented a validation for these components to prevent selecting the HTTP method 'PATCH' if an Apache HttpComponents REST template is not provided. 24 +//__Improved migration behavior__// 25 +This release introduces several improvements concerning the migration behavior via "Transfer settings from Design." Among these are: 26 +A smoother migration of your JMS (and backup JMS) process. 27 +Shortening of names that otherwise would be too long, additional feedback given to the user. 28 +Feedback when the migration process is finished. 33 33 34 -//__ External links__//35 - Clickinglinkstoexternaldocumentation in the eMagizportal is now configuredto always openthelinksina newtab,ratherthanreplacingyourcurrent tab.30 +//__Additional checks when deploying__// 31 +This release introduces additional checks when deploying. Among others, we have added a check to prevent you from deploying two flows that use the same resource with differing versions. Not stopping this can cause issues with deployments and even worse with the functional behavior of the flows, as it leads to the situation in which a validation error might trigger on one offramp but not on the other. 36 36 37 -//__Test Message from Manage-Explore__// 38 -We improved the names and descriptions of test messages that you saved when debugging and wiretapping your integration in the Manage - Explore section. 33 +== **Store Improvements** == 39 39 40 - <Screenshothere>35 +== **Event Streaming - Certificate Management** == 41 41 42 -//__Password property__// 43 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 44 - 45 -== **Bug Fixes** == 46 - 47 -//__Event Processor Keystore and Trustore__// 48 - 49 -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. 50 - 51 - 52 - 53 - 54 54 == **Fancy Forum Answers** == 55 55 56 56 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: 57 57 58 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 59 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 60 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 61 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 41 +* [[How to determine the system definition for this sample message in JSON?>>https://my.emagiz.com/p/question/172825635703440852||target="blank"]] 42 +* [[Instability in JMS connection>>https://my.emagiz.com/p/question/172825635703440717||target="blank"]] 62 62 63 -== **Key Takeaways** ==44 +== **Key takeaways** == 64 64 65 -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:46 +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: 66 66 67 67 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 68 68 * If you have feedback or ideas for us, talk to the Platypus 69 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 50 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 70 70 * Clear your browser cache (Ctrl + Shift + Del) 71 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]52 +* Check out the release notes [here] 72 72 * Start thinking about how the license tracker can aid your development 73 73 * Start thinking about major, minor, and patch 55 +* Upgrade to the latest build number 74 74 * Keep making great integrations 75 75 76 76 Let's stay in touch and till next time! ... ... @@ -78,11 +78,6 @@ 78 78 {{info}} 79 79 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 80 80 81 -{{/info}} 82 -))) 83 - 84 -((( 85 -{{toc/}} 86 -))) 63 +~*~* Indicates a GEN3-only feature. 64 +{{/info}})))((({{toc/}}))){{/container}} 87 87 {{/container}} 88 -{{/container}}