Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 75.1
edited by Erik Bakker
on 2023/01/31 13:02
Change comment: There is no comment for this version
To version 574.41
edited by dfirdausy
on 2024/07/02 12:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -191 - Fifty Fifty
1 +224 - Summer Sonata
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -1,116 +1,87 @@
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!** In the last couple of weeks we had our quarterly "hackathon" in which we fixed a series of annoying bugs and introduced many small improvements. On top of that we also finished several additional features for our 3rd generation runtime that will make your life while running on the 3rd generation runtime easier and better manageable. Among the additional features we have the dynamic alerting and the debugger functionality.
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 6  
7 -== **Dynamic Alerts** ~*~* ==
8 +== **Rapid Flow Testing** ==
8 8  
9 -{{warning}}Note that depending on the alert this functionality will only work when your JMS server is running on the 3rd generation runtime{{/warning}}
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 10  
11 -To enhance the observability of your integration landscape while running in the 3rd generation runtime architecture, we have added a new feature to our Manage phase called "Dynamic Alerts." You can access this functionality via the "Alerting" menu in Manage. Then, with the help of the "Trigger" overview, you can view all triggers on your environment. On the top of the list you will see all "static" alerts as defined by eMagiz. Below that you will see all "dynamic" alerts that you and your fellow teammembers (with sufficient rights) can view, edit and delete.
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 12  
13 -We offer alerting on five types.
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.
14 14  
15 -* Error message
16 -* Log message
17 -* Queue consumers
18 -* Messages in queue
19 -* Queue throughput
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.
20 20  
21 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-options.png]]
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.
22 22  
23 -These five options give you the option to configure more or less the same as you are currently used to when configuring triggers. Once you make a choice for a type you can press the "Next" button to fill in the details of the trigger. One example of how this can look is shown below.
27 +[[image:Main.Images.Release Blog.WebHome@release-224-pop-ups-wrapped-property-values.png]]
24 24  
25 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-input.png]]
29 +//__Improved text in Design architecture__//
30 +We fixed some spelling mistakes in the pop-up page when applying to environment in Design architecture.
26 26  
27 -Once the trigger tab is filled in you can navigate to the "Output" tab to select the recipients for the trigger you are configuring. On top of that you can reduce the number of message at which congestion control is enabled if ten is too high for you.
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.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--dynamic-alert-trigger-output.png]]
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.
30 30  
31 -== **Debugger ** ~*~* ~* ==
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.
32 32  
33 -{{warning}}Note that this functionality only works when the following criteria are met.
34 -* Your JMS server is running on the 3rd generation runtime
35 -* The store item called "3rd generation debugger" is imported in the infra flow of each runtime for which you want the ability to debug
36 -* The beta image is activated
37 -* A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
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 38  
39 -As with our current offering, we now offer a functionality with which you can debug channels and see them via the eMagiz portal. As stated above to get to this point you need to execute several steps to get your model ready to be "debugged". Once you have done this you can activate the "debug" mode, via Deploy -> Containers for **one** specific flow **per** runtime that is of particular interest to you. Once you have done this you will see a pop-up telling you whether the "debug" mode was indeed activated or not.
47 +[[image:Main.Images.Release Blog.WebHome@release-224-queue-explorer-button.png]]
40 40  
41 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-success.png]]
49 +[[image:Main.Images.Release Blog.WebHome@release-224-open-debug-queue-button.png]]
42 42  
43 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-action-failure.png]]
51 +//__Test Message from Manage-Explore__//
52 +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.
44 44  
45 -Assuming it was activated correctly you can navigate to Manage -> Explore -> Queue browser and select the emagiz.debug queue to see the messages coming through.
54 +[[image:Main.Images.Release Blog.WebHome@release-224-test-message-debug-title-description.png]]
46 46  
47 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--debugger-output-queue-browser.png]]
56 +//__Password property__//
57 +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 -{{info}}Note the following limitations when working with the debugger.
50 - * Your entire model needs to be migrated to the 3rd generation runtime
51 - * Only **one** flow **per** runtime can be debugged **per** environment
52 - * There is only **one** overview in which **all** debugged messages are shown
53 - * Message payload in excess of 100KB are not shown in the queue browser as they constitute a "large message"
54 - * The debug functionality works for a period of five minutes in which you can use the refresh button to see new messages coming in.
55 - ** After five minutes the debug functionality will be shutdown automatically under water.
56 - ** To see new messages after the five minutes you will have to access the debug functionality again from scratch.{{/info}}
59 +== **Bug Fixes** ==
57 57  
58 -== **Volume mapping - Network Share** ==
61 +//__Event Processor Keystore and Trustore__//
59 59  
60 -This release will introduce an additional functionality within our [[volume mapping>>doc:Main.eMagiz Academy.Microlearnings.Novice.File based connectivity.novice-file-based-connectivity-volume-mapping-on-premise||target="blank"]] offering. With this additional configuration option you can configure a network share and configure it to create a mapping between a network share and a docker volume.
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.
61 61  
62 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-overview.png]]
63 -
64 -[[image:Main.Images.Release Blog.WebHome@191-release-blog--volume-mapping-network-share-detail.png]]
65 -
66 -== **Feedback items ** ==
67 -
68 -We have also solved other feedback items besides the flow designer's critical updates.
69 -
70 -//__Improved validation feedback on non-supported WSS4J interceptor __//
71 -We have improved the validation feedback when someone tries to implement a specific WSS4J interceptor implementation.
72 -
73 -//__Improve help text in flow testing on Java classes__//
74 -We have improved the helptext when you are adding headers to your test message. In this helptext we explain the top five Java classes and how to note them down to make it work in the flow testing functionality and in eMagiz in general.
75 -
76 -//__Improved readibility of notification when trying to delete a runtime__//
77 -When you have forgotten one or more steps when deleting a runtime you will be notified by the system on this. With this release we have improved the readibility of the notification.
78 -
79 -== **Bug fixes ** ==
80 -
81 -//__Keep selection when copying properties__//
82 -We have fixed the bug that prevented you from easily copying properties from one runtime to another based on the runtime list.
83 -
84 -//__Check on security header improved for API Gateway__//
85 -We improved the check in the API Gateway through which we validate whether an API caller is authenticated when using the API Key method to secure the API Gateway.
86 -
87 -//__Copy and paste default support objects__//
88 -With this release, you can now copy and paste components without worrying that additional support objects already existing in your target flow are copied over and over into the same flow.
89 -
90 -//__Fix editability of properties when importing store items__//
91 -With this release, you can once again change property names upon importing a store item.
92 -
93 93  == **Fancy Forum Answers** ==
94 94  
95 95  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:
96 96  
97 -* [[Can I change my 2FA secret, eg. move to another authenticator?>>https://my.emagiz.com/p/question/172825635703274697||target="blank"]]
98 -* [[Webrequest header 'SOAPAction'>>https://my.emagiz.com/p/question/172825635703274615||target="blank"]]
99 -* [[XPathException on XPATH router>>https://my.emagiz.com/p/question/172825635703274295||target="blank"]]
100 -* [[Change property with new release in generation 3 runtimes>>https://my.emagiz.com/p/question/172825635703274441||target="blank"]]
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"]]
101 101  
102 -== **Key takeaways** ==
74 +== **Key Takeaways** ==
103 103  
104 -Thanks to all that helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
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:
105 105  
106 106  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
107 107  * If you have feedback or ideas for us, talk to the Platypus
108 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
80 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
109 109  * Clear your browser cache (Ctrl + Shift + Del)
110 -* Check out the release notes [here]
82 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.223 - Idyllic Image.WebHome||target="blank"]]
111 111  * Start thinking about how the license tracker can aid your development
112 112  * Start thinking about major, minor, and patch
113 -* Upgrade to the latest build number
114 114  * Keep making great integrations
115 115  
116 116  Let's stay in touch and till next time!
... ... @@ -118,6 +118,11 @@
118 118  {{info}}
119 119  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
120 120  
121 -~*~* Indicates a GEN3-only feature.
122 -{{/info}})))((({{toc/}}))){{/container}}
92 +{{/info}}
93 +)))
94 +
95 +(((
96 +{{toc/}}
97 +)))
123 123  {{/container}}
99 +{{/container}}