Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 437.1
edited by CarlijnKokkeler
on 2024/04/08 11:20
Change comment: There is no comment for this version
To version 156.1
edited by CarlijnKokkeler
on 2023/10/10 13:56
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -218 - Sprightly Spring
1 +206 - Situational Deployment
Content
... ... @@ -1,69 +1,54 @@
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 done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
7 7  
7 +== **Deployment Plan** ==
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 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
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 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
22 22  
23 -Legacy configurations that contain SSL web service message sender components are also updated with a non runtime affecting change.
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
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>>doc:Main.eMagiz Support.Migration Paths.migration-path-spring-6-migration||target="blank"]].
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
20 +
21 +//__Cleanup old images__//
22 +
23 +== **Store Improvements** ==
24 +
26 26  
27 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.
30 30  
31 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-custom-trigger.png]]
28 +//__Alerting manual pause__//
29 +A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
32 32  
33 -//__Copy to clipboard buttons__//
34 -Copy to clipboard buttons have been added to various pages:
31 +//__Ordering of graphs in Manage__//
32 +The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
35 35  
36 - * Deploy agent pop-up
37 - * Create - Flow designer: Properties
38 - * Deploy - Property releases: Property details
34 +//__UTC times in Grafana panels__//
35 +All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
39 39  
40 -[[image:Main.Images.Release Blog.WebHome@release-217-template-tango-copy-to-clipboard.png]]
37 +//__Update flow designer version__//
38 +The framework used in the flow designer has been updated to the latest version.
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.
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 -
41 +
55 55  == **Bug Fixes** ==
56 -//__Runtime overview improvements__//
57 -The runtime overview has been improved regarding checks on the runtime version.
58 58  
44 +
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"]]
49 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
65 65  
66 -== **Key Takeaways** ==
51 +== **Key takeaways** ==
67 67  
68 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:
69 69  
... ... @@ -74,6 +74,7 @@
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
62 +* 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 -)))
70 +~*~* Indicates a next-generation-architecture only feature.
71 +{{/info}})))((({{toc/}}))){{/container}}
90 90  {{/container}}
91 -{{/container}}