Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 94.1
edited by Erik Bakker
on 2023/03/17 08:35
Change comment: There is no comment for this version
To version 551.1
edited by CarlijnKokkeler
on 2024/06/17 12:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -194 - Giant Leap
1 +223 - TBD
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -1,82 +1,59 @@
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 few weeks, we have worked around the clock to release various improvement points within the 3rd generation runtime and elsewhere. We have improved the feedback provided when a flow can't start due to an incorrect transformation, improved when specific logging is triggered, and improved the stability of our internal infrastructure. On top of that, we fixed several bugs surrounding other parts of the platform. So without further ado, let us look at all these improvements.
6 +**Hi there, eMagiz developers!**
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.
6 6  
7 -== **3rd generation improvements** ==
12 +[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
8 8  
9 -//__Better feedback in the 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.
14 +== **Bug Fixes** ==
15 +//__Cron triggers__//
16 +Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
11 11  
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 alerts you receive on this topic when your model runs on the 3rd generation monitoring stack.
18 +[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
14 14  
15 -//__Improved Manage Dashboard__//
16 -This release improves what you can see in the Manage Dashboard after you migrate your model to the 3rd generation runtime architecture.
20 +//__Trigger activation__//
21 +Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
17 17  
18 -//__Improved process surrounding "slot standby" and "slot wakeup" for 3rd generation runtimes__//
19 -When a slot is put into standby mode, we also stop all on-premise runtimes to avoid excessive logging (and alerting) on your models with this functionality. 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.
23 +//__Multiple users deploying__//
24 +Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
20 20  
21 -//__Improved process of deploy preparation__//
22 -With this release, we have improved the process through which your deployment action is prepared by eMagiz. As a result, the chances of unexpected behavior occurring in your model are drastically reduced.
26 +[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
23 23  
24 -//__Improved migration of Streaming container__//
25 -When migrating your streaming container, we now consider whether "custom error handling" is used within one of the event processors. Based on that determination, additional components are added to ensure that the streaming container will work after migrating without manual intervention.
28 +//__Invalid memory configurations__//
29 +We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
26 26  
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.
31 +//__Property value synchronization__//
32 +Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
29 29  
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 help texts to clarify what each chart our table displays to you.
34 +//__JMS number__//
35 +The number on the JMS container correctly displays the amount of queues present in Design.
32 32  
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.
37 +[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
35 35  
36 -{{warning}}Should you be interested in migrating your model to our new 3rd generation architecture, don't hesitate 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}}
37 -
38 -== **Feedback items ** ==
39 -
40 -//__Generation of security logic API Gateway in case of API Key as security method is improved__//
41 -With this release, we have improved the generation of security logic within the Create phase related to API Gateways that use the API Key method as their security mechanism.
42 -
43 -//__User Roles are sorted alphabetically__//
44 -All user roles under User Management are now also sorted alphabetically.
45 -
46 -//__Name of keystore for user management now includes the environment__//
47 -To improve the naming of the downloaded keystore that needs to be distributed to external parties, we have added the name of the environment to the filename. You can distinguish between the various environments by looking at the filename.
48 -
49 -//__Improved Topic calculations in Design Architecture__//
50 -Following our earlier improvements on the best practice configuration of topics we have now additionally updated the calculations on "Topic Storage" level to ensure that the configuration of a user is related to the total Assigned Size on "Topic Storage" level.
51 -
52 -== **Bug fixes ** ==
53 -
54 -//__Consolidated upgrade process cloud template__//
55 -With this release, we have removed some specific update options that could cause mismatches between what was visually displayed and what was happening in the cloud.
56 -
57 -//__Ensure users can deploy release on environments they have edit rights on__//
58 -Currently, users with limited rights in Deploy, for example, only edit rights in Test, can now activate and deploy releases ready for other environments but need to be deployed on the environment for which they have the rights to do so.
59 -
60 60  == **Fancy Forum Answers** ==
61 61  
62 62  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:
63 63  
64 -* [[API Security not updated in all entry flow>>https://my.emagiz.com/p/question/172825635703363718||target="blank"]]
65 -* [[Preventing exceptions triggering on HTTP 400 status code>>https://my.emagiz.com/p/question/172825635703351155||target="blank"]]
66 -* [[Deployment of 3rd gen runtimes to Azure Kubernetes Service (AKS containers)>>https://my.emagiz.com/p/question/172825635703350980||target="blank"]]
43 +* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 +* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
67 67  
68 -== **Key takeaways** ==
46 +== **Key Takeaways** ==
69 69  
70 -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:
48 +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:
71 71  
72 72  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
73 73  * If you have feedback or ideas for us, talk to the Platypus
74 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
52 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
75 75  * Clear your browser cache (Ctrl + Shift + Del)
76 -* Check out the release notes [here]
54 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
77 77  * Start thinking about how the license tracker can aid your development
78 78  * Start thinking about major, minor, and patch
79 -* Upgrade to the latest build number
80 80  * Keep making great integrations
81 81  
82 82  Let's stay in touch and till next time!
... ... @@ -84,6 +84,11 @@
84 84  {{info}}
85 85  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
86 86  
87 -~*~* Indicates a GEN3-only feature.
88 -{{/info}})))((({{toc/}}))){{/container}}
64 +{{/info}}
65 +)))
66 +
67 +(((
68 +{{toc/}}
69 +)))
89 89  {{/container}}
71 +{{/container}}