Skip to Content

Changes for page 194 - Giant Leap

Last modified by Carlijn Kokkeler on 2024/04/18 13:18
From version 81.1
edited by Erik Bakker
on 2023/02/13 14:00
Change comment: There is no comment for this version
To version 79.1
edited by Erik Bakker
on 2023/02/06 07:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -192 - Small Step
1 +191 - Fifty Fifty
Content
... ... @@ -2,22 +2,14 @@
2 2  {{container layoutStyle="columns"}}(((
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 worked hard on building several major things that will be released later this Q. On top of that we finished an additional features for our 3rd generation runtime that give you chirurgical precision when doing maintenance on a model. Among the additional features we have the dynamic alerting and the debugger functionality.
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 6  
7 -== **Start/Stop Flows** ~*~* ==
7 +== **Dynamic Alerts** ~*~* ==
8 8  
9 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 10  
11 -To enhance the options you have when running into problems or when maintaining your solution in a Production environment, we have added a new feature to our Deploy phase called "Start/Stop Flows". You can access this functionality via the "Deploy Architecture" overview in Deploy. On runtime level you can open the context menu and select the option called "Start/Stop Flows".
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 12  
13 -[[image:Main.Images.Release Blog.WebHome@192-release-blog--start-stop-flows-context-menu.png]]
14 -
15 -
16 -{{info}}Only in "Start Editing" mode you can actually start and stop specific flows{{/info}}
17 -
18 -
19 - 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.
20 -
21 21  We offer alerting on five types.
22 22  
23 23  * Error message
... ... @@ -41,6 +41,7 @@
41 41  {{warning}}Note that this functionality only works when the following criteria are met.
42 42  * Your JMS server is running on the 3rd generation runtime
43 43  * 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 +* A feature flag needs to be enabled on your model
44 44  * A new release is created that includes the flow changes and this release is deployed to the environment(s){{/warning}}
45 45  
46 46  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.