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 06- Situational Deployment1 +224 - Summer Sonata - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.dfirdausy - Content
-
... ... @@ -1,114 +1,74 @@ 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, wehavedonemuch work fortheDeploy phase.Ontopofthat, we haveworkedon severalstorefunctionalities.Next to this, wehave several smallerfeedbackitemsfromourhackathoneffortsthatarenowreleased toyou.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 -== **Release Date Change** == 8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (4:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]. 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. 9 9 10 -== **Deployment Plan** == 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. 11 11 12 -//__ Improveddeploymentplanto make the processbetter andmorepredictable__//13 - Thealgorithm for generatingadefault deployment plan isimprovedtokeep JMS downtime and alerting to aminimum. When stoppinga machine, the JMS server is stoppedlast,andwhen executingthedeploymentplan, the JMS server is deployedfirst. This way, theJMS server is troubled minimally, and all processesarestopped before beingdeployed again. This providesadditionalcontrol overthedeploymentof your release(s)and reduces the likelihoodof false-positive logging(and potentially alerting)during andshortly afterthe deployment.15 +//__Adding tags in Capture__// 16 +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. 14 14 15 -{{info}}The start/stop/restart machine deployment steps work for cloud and on-premises machines.{{/info}} 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. 16 16 17 -//__Editing release properties__// 18 -With this release, it will be possible to change the description of a property by editing the property. 23 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]] 19 19 20 -//__ Containermemorysettings__//21 - A change inmemorysettingstriggersredeploymentofthecontainernow.25 +//__Improved text in Design architecture__// 26 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture. 22 22 23 -//__ Properties tab__//24 -We have removed thedeprecatedtabProperties in theDeploy phase.28 +//__Adding attributes for a message definition__// 29 +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 -//__ Cleanup oldimages__//27 -W henareleaseisremoved,therelated unusedimagesinthe on-premisesmachineswillbe removed aswell.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. 28 28 29 -//__ Performanceimprovements forloading releases__//30 - Performanceimprovementshavebeenimplemented forloadingreleasesinDeploy.Releasesshouldnowloadfaster thanbefore. All functionalityshouldremainexactlythe same asbefore.34 +//__External links__// 35 +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. 31 31 32 -== **Store Improvements** == 37 +//__Debugging Shortcut__// 38 +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. 33 33 34 -//__Message definition elements order__// 35 -We fixed an issue that the order of message definition elements was changed after being imported. 40 +[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]] 36 36 37 -//__Importing a store item with synchronous message definitions__// 38 -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. 42 +[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] 39 39 40 -//__ Importingstoreitemscontaining static copies__//41 - We fixedanissue thatstoreitemsweremissingstaticcopies.Now, storeitemswithstatic copiesareimportedcorrectly.44 +//__Test Message from Manage-Explore__// 45 +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. 42 42 43 -//__Importing store content__// 44 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store. 47 +<Screenshot here> 45 45 46 -//__ Storedisclaimer__//47 - Users who arenotthemodelowner nolonger seethe eMagiz Storedisclaimerpopup,instead theyseea popupcontaining a messagethat statesthatthemodel owner shouldaccept thedisclaimer.49 +//__Password property__// 50 +In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value. 48 48 49 -== **Feedback Items** == 50 - 51 -//__Alerting manual pause__// 52 -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. 53 - 54 -//__Ordering of graphs in Manage__// 55 -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). 56 - 57 -//__UTC times in Grafana panels__// 58 -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. 59 - 60 -//__Update flow designer version__// 61 -The framework used in the flow designer has been updated, improving performance. 62 - 63 -//__Carwash track TLS versions in logging__// 64 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards. 65 - 66 -//__Moving channels in the flow designer__// 67 -Moving already attached channels in the flow designer has been made sligthly easier. 68 - 69 -//__Topic sizes description change__// 70 -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. 71 - 72 -//__Password change notification__// 73 -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. 74 - 75 -//__Password comparison__// 76 -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. 77 - 78 -//__Inactive user alerting__// 79 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications. 80 - 81 -//__Alphabetical sorting on user level in HTTP statistics__// 82 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. 83 - 84 - 85 85 == **Bug Fixes** == 86 86 87 -//__Flow designer styling__// 88 -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. 54 +//__Event Processor Keystore and Trustore__// 89 89 90 -//__Partial search for messages__// 91 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim". 56 +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. 92 92 93 -//__Disk usage after cloud template update__// 94 -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. 95 95 96 -//__Error handling migration__// 97 -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. 98 98 60 + 99 99 == **Fancy Forum Answers** == 100 100 101 101 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: 102 102 103 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 104 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 105 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 106 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 107 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 65 +* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]] 66 +* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]] 67 +* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]] 68 +* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]] 108 108 70 +== **Key Takeaways** == 109 109 110 -== **Key takeaways** == 111 - 112 112 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: 113 113 114 114 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -115,10 +115,9 @@ 115 115 * If you have feedback or ideas for us, talk to the Platypus 116 116 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 117 117 * Clear your browser cache (Ctrl + Shift + Del) 118 -* Check out the release notes [here] 78 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]] 119 119 * Start thinking about how the license tracker can aid your development 120 120 * Start thinking about major, minor, and patch 121 -* Upgrade to the latest build number 122 122 * Keep making great integrations 123 123 124 124 Let's stay in touch and till next time! ... ... @@ -126,6 +126,11 @@ 126 126 {{info}} 127 127 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 128 128 129 -~*~* Indicates a next-generation-architecture only feature. 130 -{{/info}})))((({{toc/}}))){{/container}} 88 +{{/info}} 89 +))) 90 + 91 +((( 92 +{{toc/}} 93 +))) 131 131 {{/container}} 95 +{{/container}}