Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 435.1
edited by CarlijnKokkeler
on 2024/04/08 11:19
Change comment: There is no comment for this version
To version 123.1
edited by Erik Bakker
on 2023/06/08 08:11
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +199 - Home Improvements
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,79 +1,57 @@
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!**
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.
7 7  
7 +== **Next generation improvements and bug fixes** ==
8 8  
9 -== **Spring 6 Migration** ==
10 -As announced in our previous release blogs, we will release a major version of our [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] base image for all our clients running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture in our release that will be released on April 11th, 2024, which is this release.
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.
11 11  
12 -Configurations that contain any one of the listed components below are automatically migrated to Spring 6:
13 -* JDBC BoneCP data source
14 -* SSL web service message sender
15 -* Web service outbound gateway
16 -* SFTP session factory
17 -* HTTP components message sender
18 -* Job manager
19 -* Credentials
20 -* Simple job launcher
21 -* Default SFTP session factory
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.
22 22  
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
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}}
24 24  
25 -In our continued efforts to make the transition to Spring 6 as smooth as possible we have written down the advised process for identifying and updating the relevant flows as a consequence of the Spring 6 migration, which you can find [[here runtime>>doc:Main.Support.Migration Paths.migration-path-spring-6-migration||target="blank"]].
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.
26 26  
27 -== **Feedback Items** ==
28 -//__Dynamic trigger__//
29 -The generic alert trigger "More than 100 messages on queue over 10 minutes" has been migrated to a dynamic trigger for each model and environment, allowing users to edit this trigger.
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.
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
23 +== **Store Improvements** ==
32 32  
33 -//__Copy to clipboard buttons__//
34 -Copy to clipboard buttons have been added to various pages:
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.
35 35  
36 - * Deploy agent pop-up
37 - * Create - Flow designer: Properties
38 - * Deploy - Property releases: Property details
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.
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
31 +== **Event Streaming - Certificate Management** ==
41 41  
42 -//__Reset H2 database__//
43 -For our **[[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]** architecture, it is now possible to remove the eMagiz infra H2 database for connector machines.
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]].
44 44  
45 -{{info}}Please note the following:
46 -
47 -* Only H2 databases that are registered under the standard eMagiz data folder will be removed.
48 -* It is possible to reset the H2 database on every cloud runtime, but it will only have effect if an H2 database exists for that runtime.
49 -* For on-premise runtimes, only a reset of the runtime is needed.
50 -
51 -For more information please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-runtime-management-reset-h2.WebHome||target="blank"]]{{/info}}
52 -
53 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-remove-h2.png]]
54 -
55 -== **Bug Fixes** ==
56 -//__Runtime overview improvements__//
57 -The runtime overview has been improved regarding checks on the runtime version.
58 -
59 59  == **Fancy Forum Answers** ==
60 60  
61 61  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:
62 62  
63 -* [[XSD is only partially imported into eMagiz (xmlStat.xsd)>>https://my.emagiz.com/p/question/172825635703773349||target="blank"]]
64 -* [[TLSv1.3>>https://my.emagiz.com/p/question/172825635703773474||target="blank"]]
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"]]
65 65  
66 -== **Key Takeaways** ==
43 +== **Key takeaways** ==
67 67  
68 -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:
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:
69 69  
70 70  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
71 71  * If you have feedback or ideas for us, talk to the Platypus
72 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
49 +* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
73 73  * Clear your browser cache (Ctrl + Shift + Del)
74 74  * Check out the release notes [here]
75 75  * Start thinking about how the license tracker can aid your development
76 76  * Start thinking about major, minor, and patch
54 +* Upgrade to the latest build number
77 77  * Keep making great integrations
78 78  
79 79  Let's stay in touch and till next time!
... ... @@ -81,11 +81,6 @@
81 81  {{info}}
82 82  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
83 83  
84 -{{/info}}
85 -)))
86 -
87 -(((
88 -{{toc/}}
89 -)))
62 +~*~* Indicates a GEN3-only feature.
63 +{{/info}})))((({{toc/}}))){{/container}}
90 90  {{/container}}
91 -{{/container}}