Skip to Content

Changes for page 208 - Controlled State

Last modified by Carlijn Kokkeler on 2024/04/18 13:10
From version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
Change comment: There is no comment for this version
To version 249.2
edited by Danniar Firdausy
on 2023/11/06 16:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -199 - Home Improvements
1 +208 - Controlled State
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.dfirdausy
Content
... ... @@ -2,51 +2,54 @@
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 few weeks, we have worked hard on improving various aspects of our home. Among others we have improved the logging, alerting, and security of our next-generation architecture. On top of that we have improved the inner workings of the store and the certificate management for those of us using the Event Streaming pattern.
5 +**Hi there, eMagiz developers!** We have done much work to improve the functionality of our state generation solution so that you can have a better overview of its implementation in your environment. This overview covers a visibility towards the statistics for Retrieve Latency, Cache Size, Successful and Failed Retrieves. Next to the monitoring for the state generation implementation in your model, several feedback items revolving around user interfacing components in our platform that can improve the user experience are also released. Lastly, some performance improvements and bug fixes have also been implemented.
6 6  
7 -== **Next generation improvements and bug fixes** ==
7 +{{warning}}State generation functionality is only accessible for models with an add-on state generation license.{{/warning}}
8 8  
9 -//__Enhanced overview of the HTTP Statistics__//
10 -As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe. On top of that it makes comparing data on various operations easier. In here you can also filter on one (by pressing the + icon) or more by clicking on the filter icon. In case you want to sort the table in a different manner you can click on the name of the column on which you want to sort.
9 +== **State Generation~*~*** ==
11 11  
12 -//__Reason why runtime cannot start is now in the vast majority of cases reported back__//
13 -In this release, we have improved the way we report failures during startup of runtimes. This will ensure that it becomes much easier to pinpoint what went wrong upon startup.
11 +//__New Page__//
12 +The following page has been added:
13 +* State generation statistics: Contains the statistics for state generation implementation in your model. This page can be found under Manage->Monitoring, right under the Topic statistics navigation menu. This page provides you with graphs that explains the Retrieve Latency, Cache Size, Successful and Failed Retrieves, which are coming from flows using state generation components. **Note** that this menu will only show for models that has the add-on license for state generation.
14 14  
15 -{{info}}Note that this fix is part of a new runtime image for the next-generation runtimes. The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}}
15 +{{info}}The graphs are configured with the same behaviour as graphs in the other statistics pages, meaning that you can also change the time range, zoom in zoom out to the time frame, etc.{{/info}}
16 16  
17 -//__Forced congestion control__//
18 -To reduce the number of repeating mails within a 10 minute window we have now forced congestion control on all alerts generated via the platform.
17 +== **Metrics Storage Duration** ==
18 +We will ... .
19 19  
20 -//__Unused images are cleaned up__//
21 -This release improves the way in which images are kept. To avoid a lot of old and unused images on our systems and our systems we now (on default) cleanup old images that are not used anymore. Should you wish to keep the images and manually remove them on your own server you can deactivate this behavior per "Deploy machine" step in your deployment plan.
20 +== **Feedback Items** ==
22 22  
23 -== **Store Improvements** ==
22 +//__Import from store__//
23 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
24 24  
25 -//__Improved importing behavior for specific use cases__//
26 -Before, it could happen that a certain placeholder that contained an asterisk were imported incorrectly. This has now been fixed to ensure that the correct import behavior is experienced by our users.
25 +//__Import from store__//
26 +The button 'Import from Store' in Design will directly open the store instead of showing a pop up asking whether the store should be opened.
27 +
28 +== **Bug Fixes** ==
27 27  
28 -//__Fixed bug in creating a message mapping on top of an imported system message__//
29 -It is now possbile to create a message mapping to an imported system message from the store.
30 +//__Topic and event-processor names__//
31 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
30 30  
31 -== **Event Streaming - Certificate Management** ==
33 +//__Topic and event-processor names__//
34 +The styling of the event streaming canvas in the Create and Deploy phases has been altered slightly to make topic and event-processor names more readable.
32 32  
33 -//__Expired certification notification__//
34 -As of now we have functionality in place that will inform you (and us) when a client certificate of an Event Streaming user is going to expire within the upcoming three months. This way you can take action early on and report back that the update was succesfull so we can revoke the expiring client certificate accordingly. If you want specific information on this please reach out to us at [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
35 -
36 36  == **Fancy Forum Answers** ==
37 37  
38 38  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:
39 39  
40 -* [[OpenAPI import for API Gateway system response throws error>>https://my.emagiz.com/p/question/172825635703466150||target="blank"]]
41 -* [[Api GW won't boot after adding integration>>https://my.emagiz.com/p/question/172825635703479151||target="blank"]]
40 +* [[Message Redelivery blank error message>>https://my.emagiz.com/p/question/172825635703619933||target="blank"]]
41 +* [[Timeout error kafka batch creation>>https://my.emagiz.com/p/question/172825635703620012||target="blank"]]
42 +* [[SFTP Connectivity: Transfering a whole folder structure>>https://my.emagiz.com/p/question/172825635703632587||target="blank"]]
43 +* [[Next generation architecture with dynamic file pickup / filedrop>>https://my.emagiz.com/p/question/172825635703632732||target="blank"]]
42 42  
45 +
43 43  == **Key takeaways** ==
44 44  
45 -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:
46 46  
47 47  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
48 48  * If you have feedback or ideas for us, talk to the Platypus
49 -* 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.
50 50  * Clear your browser cache (Ctrl + Shift + Del)
51 51  * Check out the release notes [here]
52 52  * Start thinking about how the license tracker can aid your development
... ... @@ -59,6 +59,6 @@
59 59  {{info}}
60 60  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
61 61  
62 -~*~* Indicates a GEN3-only feature.
65 +~*~* Indicates a next-generation-architecture only feature.
63 63  {{/info}})))((({{toc/}}))){{/container}}
64 64  {{/container}}