Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 579.1
edited by dfirdausy
on 2024/07/02 13:29
Change comment: There is no comment for this version
To version 290.1
edited by CarlijnKokkeler
on 2023/12/06 14:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -224 - Summer Sonata
1 +210 - Deployment Delights
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.dfirdausy
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,76 +3,62 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we are bringing a significant performance improvement to flow testing, with execution times now accelerated by up to 3 times. Next to that, 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 +**Hi there, eMagiz developers!** In this release, we have invested our effort to improve the performance and experience of our platform in the Deploy phase. Next to that, we did several bug fixes, not only for the Deploy phase, but also for the Store. Lastly, we made some changes to the alerts that you may be receiving.
7 7  
8 -== **Faster Flow Testing** ==
8 +== **Alerts** ==
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.
10 +//__Topic approaching max size alert__//
11 +The alert ‘topic approaching maximum size’ has been temporarily disabled due to a high number of false positives.
11 11  
13 +//__Missing metrics alert__//
14 +We solved an issue where the ‘missing metrics’ alert did not always contain the full container name.
15 +
12 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.
15 15  
16 -//__Help text panel in Capture__//
17 -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.
18 +//__Improved release build process__//
19 +When a new release will be activated, no longer all containers will be rebuild but only affected containers will be rebuild. This should decrease the time for a release to be ready to be deployed.
18 18  
19 -//__Adding tags in Capture__//
20 -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.
21 +//__Container version overview__//
22 +Due to the improved build process for containers, the release versions and container versions will not longer be the same anymore. Therefore we introduce a way where you can look up to see which container versions are linked to a specific release. This can help you to identify if your containers that are running have the right version according to the release.
21 21  
22 -[[image:Main.Images.Release Blog.WebHome@release-224-selectable-cursor-for-tags.png]]
24 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
23 23  
24 -//__Adding attributes for a message definition__//
25 -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.
26 +//_Improved deployment process_//
27 +The improved release build process, as mentioned above, brings another major improvement to the platform. Because container versions will not be updated regularly we can identify during a deployment which container should get a new container version. Only the ones that should get a new version will be deployed and restarted, all other containers will not go down and keep running. This decreases the deployment time and improves the performance.
26 26  
27 -//__Improved text in Design architecture__//
28 -We fixed some spelling mistakes in the steps to be executed within the pop-up page when applying to environment in Design architecture.
29 -
30 -//__Property value page__//
31 -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.
29 +//__Rebuilding of images__//
30 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
32 32  
33 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
32 +== **Bug Fixes** ==
34 34  
35 -//__Password property__//
36 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value.
34 +//__Runtime metrics processing__//
35 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
37 37  
38 -//__Enumeration values__//
39 -When editing a message definition (i.e., a System Message, CDM, API Data Model, or Event Streaming Data Model) in the Flow designer within 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.
37 +//__Deployment plan__//
38 +We solved a bug where a deployment step in the execution of the deployment plan could randomly get stuck.
40 40  
41 -//__Helptext for HTTP methods__//
42 -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.
40 +//__View all store items__//
41 +An issue has been fixed where it was not possible to load more store items in the left panel in the Create phase Flow Designer.
43 43  
44 -//__External links__//
45 -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.
46 -
47 -//__Debugging Shortcut__//
48 -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.
43 +//__Out of memory behavior__//
44 +We improved the out of memory behavior of runtimes. Runtimes will now always restart when an out of memory error occurs.
49 49  
50 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
46 +//__Max fetch size__//
47 +In the Flow Designer, we improved the help text of the advanced option of ‘max fetch size’ for the Mail Inbound Adapter component to better describe how that option affects the component's behavior.
51 51  
52 -{{html}}
53 -<!-- 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. -->
54 -<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] -->
55 -{{/html}}
56 -
57 -//__Test Message from Manage-Explore__//
58 -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.
59 -
60 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
61 -
62 -== **Bug Fixes** ==
63 -
64 -//__Event Processor Keystore and Trustore__//
65 -
66 -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.
67 -
68 68  == **Fancy Forum Answers** ==
69 69  
70 70  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:
71 71  
72 -* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]]
53 +* [[Deleting object failed for security reasons>>https://my.emagiz.com/p/question/172825635703671061||target="blank"]]
54 +* [[How do I delete a user?>>https://my.emagiz.com/p/question/172825635703670973||target="blank"]]
55 +* [[Import RCV-Shipment & RCV-Receipt XSD from Boltrics>>https://my.emagiz.com/p/question/172825635703671171||target="blank"]]
56 +* [[Add day in XPath header enricher>>https://my.emagiz.com/p/question/172825635703671325||target="blank"]]
57 +* [[Missing Body Java type resulting in problems>>https://my.emagiz.com/p/question/172825635703683790||target="blank"]]
73 73  
74 -== **Key Takeaways** ==
75 75  
60 +== **Key takeaways** ==
61 +
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  
78 78  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -79,13 +79,19 @@
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"]]
68 +* 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
71 +* 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!
88 88  
76 +{{info}}
77 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
78 +
79 +~*~* Indicates a next-generation-architecture only feature.
80 +{{/info}}
89 89  )))
90 90  
91 91  (((