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 +206 - Situational Deployment - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. dfirdausy1 +XWiki.CarlijnKokkeler - Content
-
... ... @@ -1,77 +1,99 @@ 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 are bringing a significantperformanceimprovement to flowtesting,withexecution timesnowacceleratedby up to 3 times. Next to that,overthepastweek,wefocused on improvingtheusabilityof ourplatform and addressingcommunityfeedback.Specifically, weenhanceduserinterfaceelementson severalpages, includingthedescriptions of help texts, externallinks within helptexts,andtheoveralllayoutofhelp text pages. Additionally, wemade improvementstoseveralpop-up pages. We alsomadetheuserinterfacemore user-friendlyfordebugging integration flows.Lastly,we resolvedan issuefor some modelswhen creatingan Event Processor.5 +**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you. 7 7 8 -== ** Faster Flow Testing** ==7 +== **Deployment Plan** == 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 +//__Improved deployment plan to make the process better and more predictable__// 10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 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 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 15 15 16 -//__ HelptextpanelinCapture__//17 - Collapsingthehelptextofthispop-up pageby clicking the "?" icon on the topright cornerof thepop-up pagewillnowcorrectlyhidethehelptext pane.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 18 18 19 -//__ Addingtagsin Capture__//20 - In theCapture phase,clicking to add orremoveatag in thepop-up pagefor specifying integrationrequirements nolongerdisplaysa'blocked' icon.18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 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 +//__Cleanup old images__// 22 +When a release is removed, the related unused images in the on-premises machines will be removed as well. 26 26 27 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 24 +//__Performance improvements for loading releases__// 25 +Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before. 28 28 29 -//__Improved text in Design architecture__// 30 -We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 27 +== **Store Improvements** == 31 31 32 -//__ Adding attributesfor a message definition__//33 -We fixed an issue where your selectedattributeswerelostwhen navigating betweenpaginationswhileaddingmoreattributes to the entity in the pop-upshownwhen you pressthe 'Add Attribute' button on the right panel of your System Message,CDM, API Data Model, orEvent StreamingData Model.29 +//__Message definition elements order__// 30 +We fixed an issue that the order of message definition elements was changed after being imported. 34 34 35 -//__ HelptextforHTTP methods__//36 -We i mprovedthehelptextfortheHTTPmethodfieldintheHTTP outbound gatewayand HTTP outboundchannel adapterflow componentsto provideclearerdescriptionsfor differentHTTP methods.Additionally,we implemented avalidationforthesecomponentstopreventselectingtheHTTP method 'PATCH' if an ApacheHttpComponents REST template isnotprovided.32 +//__Improting a store item with synchronous message definitions__// 33 +We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions. 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. 35 +//__Importing store items containing static copies__// 36 +We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly. 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 +//__Alerting manual pause__// 41 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment. 48 48 49 -[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] 43 +//__Ordering of graphs in Manage__// 44 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first). 50 50 51 -//__T estMessagefromManage-Explore__//52 -A dditionally,wehaveimprovedthe namesanddescriptions oftestmessagesthatyou savedwhen debuggingandwiretappingyourintegrationintheManage- Exploresection.46 +//__UTC times in Grafana panels__// 47 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts. 53 53 54 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]] 49 +//__Update flow designer version__// 50 +The framework used in the flow designer has been updated to the latest version. 55 55 56 -//__ Passwordproperty__//57 - IntheFlow designer withintheCreatephase,copyingpasswordpropertiesnowcopiestheactualpasswordvalueinsteadofthe encoded value.52 +//__Carwash track TLS versions in logging__// 53 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 58 58 55 +//__Moving channels in the flow designer__// 56 +Moving already attached channels in the flow designer has been made sligthly easier. 57 + 58 +//__Topic sizes description change__// 59 +In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved. 60 + 61 +//__Password change notification__// 62 +When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action. 63 + 64 +//__Password comparison__// 65 +When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database. 66 + 67 +//__Inactive user alerting__// 68 +Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 69 + 70 +//__Alphabetical sorting on user level in HTTP statistics__// 71 +Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 72 + 73 +//__SOAP Web services path__// 74 +Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings. 75 + 59 59 == **Bug Fixes** == 60 60 61 -//__Event Processor Keystore and Trustore__// 78 +//__Flow designer styling__// 79 +The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities. 62 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. 81 +//__Partial search for messages__// 82 +It is now possible to search on messages partially in Manage Monitoring. For example, search for Uptime can be done by searching for "up" "time" "ptim". 64 64 84 +//__Disk usage after cloud template update__// 85 +In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates. 86 + 87 +//__Error handling migration__// 88 +If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false. 89 + 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 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 70 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 71 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 72 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 94 +* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 73 73 74 -== **Key Takeaways** ==96 +== **Key takeaways** == 75 75 76 76 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: 77 77 ... ... @@ -79,9 +79,10 @@ 79 79 * If you have feedback or ideas for us, talk to the Platypus 80 80 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 81 81 * Clear your browser cache (Ctrl + Shift + Del) 82 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]104 +* Check out the release notes [here] 83 83 * Start thinking about how the license tracker can aid your development 84 84 * Start thinking about major, minor, and patch 107 +* Upgrade to the latest build number 85 85 * Keep making great integrations 86 86 87 87 Let's stay in touch and till next time! ... ... @@ -89,11 +89,6 @@ 89 89 {{info}} 90 90 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 91 91 92 -{{/info}} 93 -))) 94 - 95 -((( 96 -{{toc/}} 97 -))) 115 +~*~* Indicates a next-generation-architecture only feature. 116 +{{/info}})))((({{toc/}}))){{/container}} 98 98 {{/container}} 99 -{{/container}}