Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 25-TBD1 +206 - Situational Deployment - Content
-
... ... @@ -1,83 +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,a newruntimeimage(LINK)will be available,includingchangesto ourinfinispan cachemanager, SMB inboundchanneladapter, andheapmemory configuration. Moreover, we havemade progressonouralertingimprovementplansandhaveimprovedandaddedseveralpop-upscreens.Findout allwe releasedbelow!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 -== **Feedback Items** == 9 -//__Alerting notification settings__// 10 -The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature. 7 +== **Deployment Plan** == 11 11 12 -[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]] 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. 13 13 14 -//__ Processcontainers__//15 - If a model does nothavelicenseforapattern, themodelcontact nowhastheoptiontodeletetheprocesscontainerofthat givenpattern.12 +//__Editing release properties__// 13 +With this release, it will be possible to change the description of a property by editing the property. 16 16 17 -//__ Designsettings__//18 - WhenpressingApply settingsin Design Settings,a confirmation screen will now beshowntopresentthe changesthat will be takenintoeffect foreach environment.15 +//__JMS memory setting check__// 16 +A change in memory settings triggers redeployment of the container now. 19 19 20 -[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]] 18 +//__Properties tab__// 19 +We have removed the deprecated tab Properties in the Deploy phase. 21 21 22 -//__Untested images__// 23 - A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before. 24 - 25 -[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]] 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 -//__Infinispan Cache Manager__// 28 -We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available. 29 - 30 -//__Infinispan Cache Manager error message__// 31 -We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available. 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. 32 32 33 -//__Flow bump__// 34 -When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description. 35 - 36 -[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]] 27 +== **Store Improvements** == 37 37 38 -//__ Unusedsupportobjects__//39 - Supportobjects arenowshownintwo sections,namely 'Support objects'and'Unusedsupportobjects'.29 +//__Message definition elements order__// 30 +We fixed an issue that the orders of message definition’s elements were changed after they were imported. 40 40 41 -[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]] 42 - 43 -//__Deleting routes__// 44 -For clarity purposes, a confirmation pop-up will be shown when deleting routes. 32 +//__Message definition elements order__// 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. 45 45 46 - [[image:Main.Images.ReleaseBlog.WebHome@release-225-routes.png]]35 +== **Feedback Items** == 47 47 48 -//__Debug queue__// 49 -The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it. 50 - 51 -[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]] 52 - 53 -== **Bug Fixes** == 54 -//__Internal server error__// 55 -The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it. 37 +//__Alerting manual pause__// 38 +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. 56 56 57 -//__ Namespaceupdate__//58 - Editing a namespaceusedin a message definitionautomaticallyupdatesthemessagedefinition&transformations.40 +//__Ordering of graphs in Manage__// 41 +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). 59 59 60 -//__ Errorpop-up__//61 - Wefixedanissue wherea pop-up was shownwith an incorrecterrorwhileediting the messagemappingofasynchronousflows.43 +//__UTC times in Grafana panels__// 44 +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. 62 62 63 -//__ SMB inboundchanneladapter__//64 -The SMB inbound channel adapterfailed toretrievefileswhen the remotedirectorypointedto a path withmultipledirectoriesinit, unless they wereseperated with'}}' instead of '{{/'. Thishasbeenresolved, meaningthat remotedirectoriesthat containmultiplefolders in its path can (andshould) contain'/' again. For this, a newruntime image LINK isavailable.46 +//__Update flow designer version__// 47 +The framework used in the flow designer has been updated to the latest version. 65 65 66 -//__ Heapmemory__//67 - Theinitialcommittedheap memoryof runtimeshasbeenlowered to bettermatchactual usage. For this,anewruntimeimageLINKisavailable.49 +//__Carwash track TLS versions in logging__// 50 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 68 68 69 -//__ Classpathconflicts__//70 - Weupdatedtransitive runtimedependenciesto preventpotentialconflictsontheclasspathforextendedimages.52 +//__Moving channels in the flow designer__// 53 +Moving already attached channels in the flow designer has been made sligthly easier. 71 71 55 +//__Topic sizes description change__// 56 +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. 57 + 58 +//__Password change notification__// 59 +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. 60 + 61 +//__Password comparison__// 62 +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. 63 + 64 + 65 +== **Bug Fixes** == 66 + 67 +//__Flow designer styling__// 68 +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. 69 + 72 72 == **Fancy Forum Answers** == 73 73 74 74 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: 75 75 76 -* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 77 -* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 78 -* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 74 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]] 79 79 80 -== **Key Takeaways** ==76 +== **Key takeaways** == 81 81 82 82 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: 83 83 ... ... @@ -85,9 +85,10 @@ 85 85 * If you have feedback or ideas for us, talk to the Platypus 86 86 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 87 87 * Clear your browser cache (Ctrl + Shift + Del) 88 -* Check out the release notes [ [here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]84 +* Check out the release notes [here] 89 89 * Start thinking about how the license tracker can aid your development 90 90 * Start thinking about major, minor, and patch 87 +* Upgrade to the latest build number 91 91 * Keep making great integrations 92 92 93 93 Let's stay in touch and till next time! ... ... @@ -95,11 +95,6 @@ 95 95 {{info}} 96 96 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 97 97 98 -{{/info}} 99 -))) 100 - 101 -((( 102 -{{toc/}} 103 -))) 95 +~*~* Indicates a next-generation-architecture only feature. 96 +{{/info}})))((({{toc/}}))){{/container}} 104 104 {{/container}} 105 -{{/container}}