Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 121.1
edited by Erik Bakker
on 2023/06/05 15:02
on 2023/06/05 15:02
Change comment:
There is no comment for this version
To version 574.22
edited by dfirdausy
on 2024/07/01 15:45
on 2024/07/01 15:45
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 - 199-Home Improvements1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ebakker1 +XWiki.dfirdausy - Content
-
... ... @@ -1,59 +1,62 @@ 1 1 {{container}} 2 -{{container layoutStyle="columns"}}((( 2 +{{container layoutStyle="columns"}} 3 +((( 3 3 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 4 4 5 -**Hi there, eMagiz developers!** Inthelastfewweeks, wehave workedhardon improvingvariousaspectsof ourhome.Among otherswe haveimprovedthe logging,alerting,andsecurityofournext-generationarchitecture.On topofthat wehave improvedtheinnerworkings ofthe storeandthecertificatemanagementforthose of ususing theEventStreamingpattern.6 +**Hi there, eMagiz developers!** Over the past week, we focused on improving the usability of our platform and addressing community feedback. Specifically, we enhanced user interface elements on several pages, including the descriptions of help texts, external links within help texts, and the overall layout of help text pages. Additionally, we made improvements to several pop-up pages. We also made the user interface more user-friendly for debugging integration flows. Lastly, we resolved an issue for some models when creating an Event Processor. 6 6 7 -== **Next generation improvements and bug fixes** == 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. 8 8 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. 12 +//__Help text panel in Capture__// 13 +Collapsing the help text of this pop-up page by clicking the "?" icon on the top right corner of the pop-up page will now correctly hide the help text pane. 14 + 15 +//__Property value page__// 16 +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. 11 11 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. 18 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 14 14 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}} 20 +== **Bug Fixes** == 21 +//__Adding tags in Capture__// 22 +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. 16 16 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 +[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]] 19 19 20 -//__ Unused imagesare cleaned up__//21 - Thisreleaseimprovesthewayin which images are kept. Toavoid a lot of old andunusedimageson oursystemsandoursystemswenow(ondefault) cleanup oldimages that are notused anymore. Shouldyouwishtokeep the imagesandmanuallyremovethemon yourown server you can deactivate this behaviorper"Deploy machine"step inyourdeploymentplan.26 +//__External links__// 27 +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. 22 22 23 -//__ Improvedrollup andstorageof metricswhenrunninganeventstreaming solution__//24 - Toimprovethe stabilityoftheManage phase and,inparticular,themetricswhenzoomingoutontheprovidedinformation,wehavemadesomestructuralchangesthatsupportthisuserfunctionalitybetter.29 +//__Adding attributes for a message definition__// 30 +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. 25 25 26 - {{warning}} Due to this change,the platformwill remove data collected beforethereleasedateinthe upcomingweeks.This processwill be finished atthe beginningof July.Fromthenon,alldatabeforethe 9th of June willnolonger bevisible. As users generally do notlook backthis farbackin time,weconsiderthisan acceptable trade-off.{{/warning}}32 +When you are editing a message definition (i.e., system message, CDM, API Data Model, and Event Streaming Data Model) and adding attributes to your entities 27 27 28 -== **Store Improvements** == 34 +//__View XSLT__// 35 +We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases. 29 29 30 -//__ Improved importing behaviorforspecificusecases__//31 - Before, itcouldhappenthatacertainplaceholderthatcontainedan asterisk were importedincorrectly.This hasnowbeenfixed toensure thatthecorrectimportbehavioris experiencedbyourusers.37 +//__Multipart/form-data HTTP request__// 38 +The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available. 32 32 33 -== **Event Streaming - Certificate Management** == 34 - 35 -//__Expired certification notification__// 36 -As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 37 - 38 38 == **Fancy Forum Answers** == 39 39 40 40 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: 41 41 42 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]] 43 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]] 44 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 45 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 46 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 47 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 44 44 45 -== **Key takeaways** ==49 +== **Key Takeaways** == 46 46 47 -Thanks to all thathelped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:51 +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: 48 48 49 49 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 50 50 * If you have feedback or ideas for us, talk to the Platypus 51 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 55 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 52 52 * Clear your browser cache (Ctrl + Shift + Del) 53 -* Check out the release notes [here] 57 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 54 54 * Start thinking about how the license tracker can aid your development 55 55 * Start thinking about major, minor, and patch 56 -* Upgrade to the latest build number 57 57 * Keep making great integrations 58 58 59 59 Let's stay in touch and till next time! ... ... @@ -61,6 +61,11 @@ 61 61 {{info}} 62 62 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 63 63 64 -~*~* Indicates a GEN3-only feature. 65 -{{/info}})))((({{toc/}}))){{/container}} 67 +{{/info}} 68 +))) 69 + 70 +((( 71 +{{toc/}} 72 +))) 66 66 {{/container}} 74 +{{/container}}