Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40

From version 573.1
edited by CarlijnKokkeler
on 2024/06/19 09:01
Change comment: There is no comment for this version
To version 91.1
edited by Erik Bakker
on 2023/03/14 06:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - Idyllic Image
1 +194 - Big Leap
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,65 +1,80 @@
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 the past week, we have worked hard to release a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]]. This image contains several bug fixes, and increases the debugger duration. Next to this, improvements have been done to the SwaggerUI settings, we have resolved more deprecated warnings to prepare for Mendix version 10, and it is now possible to filter on the use of message types in Capture. Moreover, we have done bug fixes related to viewing an XSLT and SpEL expressions used for contructing a multipart/form-data HTTP request.
5 +**Hi there, eMagiz developers!** In the last couple of weeks, we have worked around the clock to release various improvements points within the 3rd generation runtime and elsewhere. Among others we have improved the feedback provided when a flow can't start due to an incorrect transformation. Improved when certain logging is triggerd and improved the stability of our internal infrastructure. On top of that we fixed several bug fixes surrounding other parts of the platform. So without further ado let us take a look at all these improvements.
7 7  
8 -== **Feedback Items** ==
9 -//__SwaggerUI default__//
10 -Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
7 +== **3rd generation improvements** ==
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
9 +//__Better feedback in error log when a corrupt stylesheet is encountered__//
10 +We have improved the logging within a 3rd generation runtime that identifies the broken resource by name within a container and informs you to navigate to Create -> Resources to see in which flows the resource is used so you can take the appropriate action.
13 13  
14 -//__Used message types__//
15 -It is now possible to filter the message types in Capture on whether they are used.
12 +//__Better internal error handling to avoid unnecessary alerting and notifications__//
13 +We have improved the internal error handling when sending metrics from the runtime to our monitoring stack. This will gravely reduce the number of alerts you will receive on this topic when your model runs on the 3rd generation monitoring stack.
16 16  
17 -[[image:Main.Images.Release Blog.WebHome@release-223-capture-settings-used.png]]
18 -
19 -//__Debugger duration__//
20 -Wiretaps and debugging sessions will now collect messages for ten minutes, this used to be five. Note that the JMS server needs to be updated in order to also store the messages for ten minutes instead of five. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
15 +//__Improved Manage Dashboard__//
16 +This release improves what you can see in the Manage Dashboard after you migrated your model to the 3rd generation runtime architecture.
21 21  
22 -== **Bug Fixes** ==
23 -//__SFTP sessions__//
24 -Support has been added to provide SFTP session factories with a known_hosts in string format rather than file format, so that it is easier to setup SFTP. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available. Moreover, helptexts have been added for clarification.
18 +//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 +When a slot is put into standby mode we now also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models that have this functionality activated. The opposite happens when the slot wakeup is triggered. As a result not only the cloud runtimes are started but also all on-premise runtimes.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts.png]]
21 +//__Improved process of deploy preparation__//
22 +With this release we have improved the process through which your deploy action is preparated by eMagiz. As a result the chances of unexpected behavior occuring in your model are drastically reduced.
27 27  
24 +//__Improved migration of Streaming container__//
25 +When migrating your streaming container we now take into account whether "custom error handling" is used within one of the event processors. Based on that determination specific additional components are added to ensure that the streaming container will work after migrating without any manual intervention.
28 28  
29 -[[image:Main.Images.Release Blog.WebHome@release-223-known-hosts-generation.png]]
27 +//__Add History to Notifications in Manage__//
28 +To improve the auditability of our platform we have introduced an audit trail to the Notification section in Manage for models running on our 3rd generation monitoring stack. This way it is always visible when the notifications were paused and who paused or unpaused the notifications.
30 30  
31 -//__SMB outbound gateway__//
32 -The SMB outbound gateway with the GET command did not work, this has been resolved. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
30 +//__Improved Manage phase for Event Streaming__//
31 +Based on the feedback on our first iteration of the Manage phase for Event Streaming we have improved the graphs and the calculations that fill the graphs with values. On top of that we have added helptexts to clarify what each graph our table displays to you.
33 33  
34 -//__TaskScheduler__//
35 -In rare occurences, when a TaskScheduler was used, a deadlock situation could occur due to thread starvation. The number of threads available to the TaskScheduler has been increased to resolve this issue. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V310.WebHome||target="blank"]] is available.
33 +//__Improved help text for network volumes__//
34 +With this release we have improved the help text that explains network volumes and how to use them within our solution.
36 36  
37 -//__View XSLT__//
38 -We fixed an issue with the transformation tooling, where it was not possible to view an XSLT in certain cases.
36 +{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesistate to contact us at [[productmanagement@emagiz.com>>mailto:productmanagement@emagiz.com]] or read our [[documentation>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] on the subject.{{/warning}}
39 39  
40 -//__Multipart/form-data HTTP request__//
41 -The recommended SpEL expression used for contructing a multipart/form-data HTTP request was no longer valid. The [[documentation>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Data Handling.expert-data-handling-multipart-form-data.WebHome||target="blank"]] has been updated with the new standard and the updated expression is now part of our default test suite. The [[legacy documentation>>doc:Main.eMagiz Academy.Microlearnings.Legacy Functionality.expert-data-handling-multipart-form-data.WebHome||target="blank"]] is also still available.
38 +== **Feedback items ** ==
42 42  
40 +//__Removed OData as option for an API Gateway operation__//
41 +With this release, we have removed the OData operation option as it was not used and was not fully supported anymore by the platform.
42 +
43 +//__Changes in API Gateway operation paths is automatically updated in Create__//
44 +When you change your path on a hosted API Gateway we will now automatically update the accompanying component in your Create (all-)entry.
45 +
46 +{{warning}}Make sure to check the changes and create a new version afterward to deploy the changes.{{/warning}}
47 +
48 +== **Bug fixes ** ==
49 +
50 +//__Prevent endless loop in Deploy -> User Management__//
51 +With this release, we have changed the way we update properties when user management is updated for an API gateway using the API Key security mechanisms. This will prevent the endless loop that could now happen on occasion.
52 +
53 +{{warning}}Any operation that is incorrectly deleted from Deploy while still end up in the logic and could cause issue so pay attention when removing API Gateway operations.{{/warning}}
54 +
55 +//__Update error handling during migration to the 3rd generation runtime__//
56 +As of now the error handling of all flows is correctly updated whilst migrating to the 3rd generation runtime configuration.
57 +
43 43  == **Fancy Forum Answers** ==
44 44  
45 45  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:
46 46  
47 -* [[.NET REST API authentication>>https://my.emagiz.com/p/question/172825635703862917||target="blank"]]
48 -* [[SMB Session Factory can't connect to AIX (or Linux) Samba share>>https://my.emagiz.com/p/question/172825635703875733||target="blank"]]
49 -* [[Check header value http_statusCode in standard filter>>https://my.emagiz.com/p/question/172825635703875955||target="blank"]]
50 -* [[How set up alerting for one message per hour>>https://my.emagiz.com/p/question/172825635703876056||target="blank"]]
62 +* [[Access Spring ApplicationContext within Groovy Script>>https://my.emagiz.com/p/question/172825635703325469||target="blank"]]
63 +* [[Configuration problem: Failed to locate '$autoCreateChannelCandidates'>>https://my.emagiz.com/p/question/172825635703312551||target="blank"]]
64 +* [[503 on SOAP Webservice hosted in eMagiz>>https://my.emagiz.com/p/question/172825635703325386||target="blank"]]
51 51  
52 -== **Key Takeaways** ==
66 +== **Key takeaways** ==
53 53  
54 -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:
68 +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:
55 55  
56 56  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
57 57  * If you have feedback or ideas for us, talk to the Platypus
58 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
72 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
59 59  * Clear your browser cache (Ctrl + Shift + Del)
60 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
74 +* Check out the release notes [here]
61 61  * Start thinking about how the license tracker can aid your development
62 62  * Start thinking about major, minor, and patch
77 +* Upgrade to the latest build number
63 63  * Keep making great integrations
64 64  
65 65  Let's stay in touch and till next time!
... ... @@ -67,11 +67,6 @@
67 67  {{info}}
68 68  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
69 69  
70 -{{/info}}
71 -)))
72 -
73 -(((
74 -{{toc/}}
75 -)))
85 +~*~* Indicates a GEN3-only feature.
86 +{{/info}})))((({{toc/}}))){{/container}}
76 76  {{/container}}
77 -{{/container}}