Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 576.1
edited by dfirdausy
on 2024/07/02 13:16
Change comment: There is no comment for this version
To version 283.1
edited by CarlijnKokkeler
on 2023/12/04 15:19
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,75 +3,56 @@
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!** We have have done much work for the Deploy phase. Moreover, we did several bug fixes, mainly relating to the Deploy phase again, but also several for the Store. Lastly, we have 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’ alert 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 +//__Container version overview__//
19 +In Deploy > Releases, it is now possible to see the container versions in the release details. This can be viewed by clicking the three dots in the Create phase section.
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 +[[image:Main.Images.Release Blog.WebHome@release-blog-210-deployment-delights-container-overview.png]]
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.
23 +//__Unchanged containers__//
24 +When deploying a new release, containers that have no changes between the deployed release and the new release will not be deployed and restarted.
26 26  
27 -[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
26 +//__Rebuilding of images__//
27 +Changing the list of flows that should run on a container will now trigger the rebuilding of images.
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.
29 +== **Bug Fixes** ==
31 31  
32 -//__Adding attributes for a message definition__//
33 -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.
31 +//__Runtime metrics processing__//
32 +The collection and publishing of runtime metrics is no longer synchronized across containers, which improves their processing.
34 34  
35 -//__Helptext for HTTP methods__//
36 -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.
34 +//__Deployment plan__//
35 +We solved a bug where a deployment step in the deployment plan could randomly get stuck.
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.
37 +//__Store message merging__//
38 +The message merging tool has been fixed to allow merging of your message definitions from the Store to existing data model messages.
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.
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.
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
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.
48 48  
49 -{{html}}
50 -<!-- 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. -->
51 -<!-- [[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]] -->
52 -{{/html}}
46 +//__Max fetch size__//
47 +We improved the help text of the advanced option of ‘max fetch size’ for the mail inbound adapter to better describe how that option affects its behavior.
53 53  
54 -//__Test Message from Manage-Explore__//
55 -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.
56 -
57 -[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
58 -
59 -//__Password property__//
60 -In the Flow designer within the Create phase, copying password properties now copies the actual password value instead of the encoded value.
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 +* [[JSONPath in SpEL expressions>>https://my.emagiz.com/p/question/172825635703415034||target="blank"]]
73 73  
74 -== **Key Takeaways** ==
55 +== **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,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"]]
63 +* 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
66 +* 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  
71 +{{info}}
72 +~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 +
74 +~*~* Indicates a next-generation-architecture only feature.
75 +{{/info}}
89 89  )))
90 90  
91 91  (((